Frequently Asked Questions
What is Genfeed?
Genfeed is an open-source, AGPL-3.0 content workflow platform you run on your own infrastructure. The self-hosted distribution is a single-tenant Docker stack with the web app, REST API, workers, and MCP server. The repository also contains source for desktop, mobile, browser, and VS Code clients.
How do I install it?
Run npx @genfeedai/create my-genfeed (Node 24 or newer) or download the checksummed
release bundle and start it with Docker Compose v2. See
Installation Options and
System Requirements.
Which content types and models are supported?
The provider registry includes text, image, video, and voice/audio adapters. Specific models vary with the provider keys you configure, account access, and region. See Models and Providers and Provider API Keys.
Do I need model provider keys?
Yes, to generate content. Self-hosted Genfeed has no Genfeed credits: you add
your own keys for providers such as OpenAI, Anthropic, Replicate, fal, and
ElevenLabs, and you pay those providers directly. The keys in
.env.example are optional and blank by default. See
Provider API Keys.
Can I run open-source models locally?
Not with the standard image. It does not start GPU or local-model services. You can register a separately operated ComfyUI workflow through the provider registry; see Provider Registry.
Can I collaborate with a team?
A self-hosted deployment is single-tenant: one organization per deployment. Local sign-up and sign-in (Better Auth) are on by default, so people sign in with their own accounts; see Configuration.
Is it free to run?
Genfeed is licensed AGPL-3.0 and does not meter your usage. You pay for your own infrastructure and any external model or publishing providers you configure. Review the repository license before redistributing a modified version.
Does self-hosting keep all data local?
Application records and local assets remain on infrastructure you operate. Prompts and media sent to an external model or publishing provider leave your deployment under that provider’s terms. Fully local processing requires a local provider path that you operate yourself.
Where do I report a problem?
Use the GitHub issue forms for reproducible public bugs and feature requests. No response time is guaranteed. Check Troubleshooting first. Do not report suspected vulnerabilities publicly; follow the Security Policy .