Capabilities
Genfeed’s source tree spans several clients. A workspace in the monorepo is evidence that source exists, not necessarily that a public installer or store listing exists.
What the self-hosted image contains
The published 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 BYOK execution; and
- brand and content-library surfaces used by the product UI.
It is single-tenant, with local sign-up on by default and an optional no-login mode. See Architecture for the services and ports.
Generation providers
The provider registry includes adapters for text, image, video, and voice/audio generation. Models vary by the keys you add, account access, and region; see Models and Providers.
Genfeed does not meter self-hosted execution and has no credits. Provider quotas, provider charges, and your infrastructure limits still apply.
Application records remain on your 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.
Client source
| Client | Repository evidence |
|---|---|
| Web | Next.js application served by the self-hosted image. |
| Desktop | macOS-first Electron application with signed macOS release automation. |
| Mobile | Expo/React Native source. Its EAS config is disabled/not actively developed, with no store publication workflow. |
| Browser | Chrome extension source with build and optional store-submission automation. |
| IDE | VS Code extension source with manual VSIX packaging CI. |
See Installation Options to run the web stack and the Security Policy for vulnerability reporting.