Capabilities

Genfeed’s source tree spans several clients and deployment modes. A workspace in the monorepo is evidence that source exists, not necessarily that a public installer or store listing exists.

Community distribution

The published Community image contains:

• the Next.js product UI;
• the NestJS REST API;
• workers, files, notifications, and MCP runtimes;
• PostgreSQL persistence through Prisma;
• embedded Redis and BullMQ background work;
• visual workflow authoring and local/BYOK execution; and
• brand and content-library surfaces used by the product UI.

Community is single-tenant. It excludes ee/ source and can start without a login wall or Cloud account.

Generation providers

The provider registry includes adapters for text, image, video, and voice/audio generation. Models vary by provider availability, account access, configuration, and region; see Available Models for the current registry.

Local/BYOK execution has no Genfeed-managed usage quota. Provider quotas, provider charges, and the self-hoster’s infrastructure limits still apply.

Application records remain on self-hosted infrastructure, but prompts and media sent to a configured external provider are processed under that provider’s terms. Fully local processing requires a local provider path.

Cloud and commercial boundaries

Cloud adds hosted operations and can provide managed inference, multi-tenant organization controls, team governance, managed publishing connectors, and managed analytics. Exact availability depends on the active deployment and commercial entitlement; this page does not promise a plan, quota, SLA, or certification.

The repository’s current ee/ tree contains billing and harness packages. It does not contain the private managed inference servers or customer Fleet/LoRA operations.

Client source

See Deployment Options for the distribution status of each surface and Security Policy  for vulnerability reporting.