Practical overview
When it fits
Use Geoflow when content production, review, publishing and operational feedback need to remain in one self-hosted workflow, especially across organizational websites or multiple channels.
Who it is for
- Enterprise website teams
- Brand, growth and content teams
- Organizations operating multiple brands or sites
- Teams building internal content-operations workflows
Documented uses
- Organize source knowledge and content-production materials.
- Create AI-assisted drafts from managed knowledge and assets.
- Apply evidence, citation, advertising and context-based quality checks before publication.
- Route content through human review and retain audit information.
- Distribute approved content to hosted sites, GEOFlow Agent, WordPress or HTTP API channels.
Requirements & limits
The repository identifies Geoflow as open source under AGPL-3.0. It documents self-hosted operation and a Docker Compose path, with PHP 8.3+, PostgreSQL, Redis and Node.js listed in the runtime requirements.
- Whether the team can operate the documented PHP, PostgreSQL, Redis and Node.js environment.
- Whether human review, quality gates and audit records are required before publication.
- Whether distribution must cover hosted sites, GEOFlow Agent, WordPress REST or a general HTTP API.
- Whether browser-assisted publishing and operator confirmation fit the team’s process.
- Whether the AGPL-3.0 license and self-hosted operating model fit the project.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start a local Docker development environment
Prepare a local Geoflow environment using the repository’s documented Docker setup.
Before you start
- Git
- Docker and Docker Compose
- A checkout of the Geoflow repository
Steps
Clone the Geoflow repository.
Enter the repository directory.
Copy .env.example to .env.
Build the Docker Compose services.
Start the services with Docker Compose in detached mode and remove orphaned containers.
Expected outcome
The documented Docker development or evaluation services are started locally.
Guide limitations
- This is a setup recipe, not a production deployment procedure.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 1 October 2026
- Original website title
- yaojingang/GEOFlow · Official homepage title · retained in its source language

