Open source. Self-host on your own infra.
Genfeed is open source under AGPL-3.0. Install it with one command or a checksummed release bundle, run it with Docker Compose, and add your own model provider keys. Or skip the ops and start free on managed cloud.
Why self-host
Full control over your infrastructure and data, with no platform fees and no lock-in.
Own Your Infrastructure
Run Genfeed on your own servers with Docker Compose: one container plus PostgreSQL. Your storage, your network, no vendor lock-in.
Own Your Data
Your content, brands, and database live on your infrastructure. Generation requests go to the model providers whose keys you add.
Bring Your Own Keys
Self-hosting has no Genfeed credits. Add your own provider keys and pay those providers directly, with no Genfeed credit meter.
Install
Two ways to run the same Community release: one command, or the release bundle with no repository clone.
One command
Downloads the release bundle, verifies its checksum, and starts it.
npx @genfeedai/create my-genfeed
Release bundle
A checksummed tarball of the latest stable release that runs as one container alongside PostgreSQL. No git clone, no build. On macOS, use shasum -a 256 -c genfeed-selfhosted.tar.gz.sha256 for the checksum step.
curl -fLO https://github.com/genfeedai/genfeed.ai/releases/latest/download/genfeed-selfhosted.tar.gz curl -fLO https://github.com/genfeedai/genfeed.ai/releases/latest/download/genfeed-selfhosted.tar.gz.sha256 sha256sum -c genfeed-selfhosted.tar.gz.sha256 tar -xzf genfeed-selfhosted.tar.gz && cd genfeed-selfhosted-v* cp .env.example .env && docker compose --env-file .env -f compose.yml up -d
Then open http://localhost:3000.
Requirements
- Docker Compose v2 (Docker Engine with the Compose plugin, or Docker Desktop)
- Node.js 24 (>=24 <25), only for the npx command. The release bundle does not need Node.
- About 10 GB of free disk (15 GB recommended)
- Free ports 3000 (web), 3010 (API), and 3014 (MCP)
Model provider keys
Self-hosting does not include Genfeed credits. To generate content, add your own keys (OpenRouter, OpenAI, Anthropic, Replicate, fal, ElevenLabs) to .env and pay those providers directly. An OpenRouter key is required for text generation; the other keys are optional. The Community image does not start GPU or local-model services.
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 your data and deployment
- No Genfeed credits: bring your own provider keys
- 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. Run it on your own infrastructure at no platform cost. You cover your own hosting and pay your model providers directly.
What is the license?
The repository is licensed AGPL-3.0. Self-hosting 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 and updates yourself, and you bring your own model provider keys. 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.