Skip to Content
Genfeed Core (OSS)Self-Hosted vs. Cloud

Self-Hosted vs. Cloud

Genfeed is available as an open-source core (self-hosted) and a fully managed cloud platform. This page compares product capabilities. For the runtime and account-sync contract, see Execution Boundaries.

Comparison

Self-Hosted (Core)Genfeed Cloud
SetupYou manage infrastructureInstant — sign up and start
CostYour compute + API costsSubscription (free tier available)
Managed inference creditsOptional, through explicit Cloud API keyYes
Image generationYesYes
Video generationYesYes
Text generationYesYes
Audio / voice generationYesYes
Brand kitsYesYes
Model selectionFull control (any model)Curated best models
Multi-tenancyNoYes — manage multiple brands
PublisherNoYes — auto-post to X, LinkedIn, Instagram, YouTube
AnalyticsNoYes — engagement, revenue per post
Team collaborationNoYes — roles, approvals, workspaces
Manager (templates, ingredients)NoYes
Studio (full editor)NoYes
MarketplaceNoYes — workflows, prompts, presets, brand kits
APIYes (REST)Yes (REST + SDK)
WebhooksYesYes
NSFW contentYes (your models)SFW only
SupportCommunity (GitHub)Priority support + SLA
UpdatesManual (git pull)Automatic
LicenseAGPL-3.0 (enterprise features under commercial license in ee/)Commercial

Marketplacemarketplace.genfeed.ai  is a separate cloud product where creators buy and sell workflows, prompts, presets, and brand kits. It is not available in the self-hosted edition.

When to Self-Host

Self-hosting is right for you if:

  • You need NSFW content support (bring your own models)
  • You want full control over models, data, and infrastructure
  • You’re a developer who prefers to run their own stack
  • You have existing infrastructure (Kubernetes, Docker, etc.)
  • You need to keep data on-premises for compliance

When to Use Cloud

Genfeed Cloud is right for you if:

  • You want to start generating content immediately
  • You need multi-brand management (agencies, teams)
  • You want auto-publishing to social platforms
  • You need analytics and performance tracking
  • You want a collaborative workspace for your team
  • You prefer managed infrastructure with zero DevOps

Cost Comparison

Self-Hosted

  • Infrastructure: $20-100/month (VPS or cloud server)
  • AI API costs: Variable (Replicate ~$0.003-0.05/image, fal.ai similar)
  • Your time: Setup, maintenance, updates, monitoring

Cloud

  • Subscription: Free tier available, paid plans from $29/month
  • Per-use pricing: Images and video billed per asset
  • Your time: Zero infrastructure management

The math: If you generate fewer than 500 images/month, Cloud is more cost-effective when you factor in infrastructure and maintenance time. Above 500/month, self-hosting saves money, but Publisher, Analytics, and multi-tenancy are not available in the self-hosted edition.

Migration Path

Start with either option — migration is straightforward:

Core to Cloud: Export your workflows, brand kits, templates, and assets, then import them into a Cloud workspace. Until a dedicated sync feature exists, this is an explicit migration step rather than automatic replication.

Cloud to Core: Export your configuration. Self-host with the same brand kits and generation settings.

Cloud signup handoff from Core may preserve onboarding intent, such as brand name and domain, but it does not sync local records into Cloud automatically.

Get Started

For detailed deployment options, see Deployment Options.