Deployment Options
Genfeed models deployment and client separately:
- SaaS is the hosted Cloud deployment with the web client.
- Community is the single-tenant self-hosted deployment with the web client.
- Desktop is an Electron client that connects to Genfeed Cloud or a self-hosted server, with an optional local workspace.
See Deployment Modes and the public deployment-mode summary for the boundary rules.
Cloud
Cloud is operated by Genfeed and is available at app.genfeed.ai . It can provide managed inference, hosted publishing and analytics, multi-tenant organizations, and team governance. Availability, limits, prices, and support terms are account- and plan-specific; this repository does not define them.
Community
Community is the public Docker distribution for self-hosters. It includes the web UI, REST API, MCP server, PostgreSQL, and embedded Redis in a single-tenant configuration. Organization billing code ships in the same image but stays inactive at runtime for a stock Community install.
You operate backups, updates, networking, TLS, provider accounts, and data handling. Application records stay on your infrastructure; requests sent to configured external providers follow those providers’ data practices.
Start with the Community quick start.
Desktop
The desktop workspace is a macOS-first Electron client that runs the same web
app. It starts in cloud mode after sign-in; an optional local workspace adds
PGlite-backed local state and local/BYOK generation. The repository has signed
macOS artifact automation for desktop-v* tags. It does not claim Windows or
Linux installers, and no installer URL is published in these docs unless a
tagged release exists.
In cloud mode, Desktop also offers:
- Agent on your own Claude Code or Codex subscription. Install and sign in
to the
claudeorcodexCLI on the same computer, sign in to Genfeed, and pick Claude Code or Codex in the agent’s runtime picker. Each turn runs on your CLI subscription and reaches Genfeed only through Genfeed MCP tools, starting withget_brand_context. Threads are saved in Genfeed, and the model turn costs no Genfeed credits. Tools that generate media or publish still use credits. Attachments are not sent to CLI runtimes yet. - Terminal. The agent panel terminal (shell, Genfeed CLI, Claude CLI, Codex CLI) runs on your computer. The first session after each launch asks for confirmation.
- Genfeed server switcher. In Settings → Organization → Integrations, the Genfeed server card switches between Genfeed Cloud and a Self-hosted server by API URL. Test connection checks the server first; switching restarts Desktop. Each server keeps its own sign-in, so switching never signs you out of the other one.
Setup details, CLI flags, and security boundaries are in the desktop README .
Mobile and extensions
Mobile, browser-extension, and IDE-extension workspaces are client source surfaces, not additional backend deployment modes. Their current distribution status is listed on Capabilities.
Help and security
Use the public issue tracker for reproducible Community bugs. This does not imply a response-time commitment. Report suspected vulnerabilities through the Security Policy .