Open source. Self-host on your own infra.
The full Genfeed content OS is open source. Clone it, run it with Docker, and own your stack end to end — or skip the ops and start free on managed cloud.
Why self-host
Full control over your infrastructure, data, and models — with no platform fees and no lock-in.
Own Your Infrastructure
Deploy the full content OS on your own servers with Docker. Your models, your storage, your network — no vendor lock-in.
Own Your Data
Everything runs inside your environment. Nothing leaves your infrastructure unless you decide it does.
Run Your Own Models
Bring your own keys or run open-source models locally. Route generation however you want, with no per-credit meter.
Up and running in four steps
A standard Docker deployment. Full instructions live in the docs.
Clone the AGPL-licensed monorepo from GitHub.
Copy the example env, add your keys, and pick your models and storage.
Bring it up with Docker Compose — API, workers, and app.
Connect your channels and start publishing.
Self-host or managed cloud
Same product. Self-host for control; move to cloud when you would rather not run the infrastructure.
Self-host
- Run it on your own infrastructure
- Full control of data and models
- No platform fees, no credit meter
- You handle hosting, updates, and support
- Community support on GitHub
Managed cloud
- We run the infrastructure and updates
- Managed credits — pay only for output
- No ops, no scaling to manage
- Direct support and SLAs on paid plans
- Start free on Pay As You Go
Common Questions
Open source for control, managed cloud for convenience.
Is self-hosting really free?
Yes. The core is open source under AGPL-3.0. Clone it, run it on your own infrastructure, and use it for free — you cover your own hosting and model costs.
What is the license?
The repository is licensed AGPL-3.0. Enterprise features under ee/ carry a separate commercial license. Self-hosting the core for your own use is fully covered by the open-source license.
Self-host or managed cloud?
Self-host gives you full control and zero platform fees, but you run the infrastructure, updates, and models yourself. Managed cloud handles all of that, adds managed credits and support, and starts free — most teams self-host to evaluate, then move to cloud to skip the ops.
Do I get support?
Community support lives on GitHub — issues, discussions, and the docs. Managed cloud plans add direct support and SLAs.
Can I move to cloud later?
Anytime. Start self-hosted, then move to managed cloud whenever the operational overhead outweighs the control — your workflows and content model carry over.
Ship it your way.
Start free on managed cloud, or deploy the open-source core on your own infrastructure.