Cloud Plan Limits

Plan-by-plan limits for Gencow Cloud: app slots, production deploys, custom domains, realtime, storage, image transforms, and credits

Gencow Cloud plan limits are enforced by the platform backend. Dashboard and CLI messages are only guidance; the server remains the source of truth for app ownership, plan capabilities, and security boundaries.

Public pricing currently shows Hobby, Pro, and Scale. Enterprise agreements are configured separately and can have custom limits. Internal platform plan IDs can differ from display names during rollout; the backend enforces capabilities such as customDomain and productionDeploy.

Summary

App limits include the stated development and production app allowance for each tier. Hobby has no production apps; Pro includes five production apps and Scale includes ten.

The platform reads the current app-slot limit from the live plan policy for every app creation and ownership transfer. Public pricing reflects the same policy. Audited platform-administrator exceptions are reserved for operations; they do not grant a customer account additional plan entitlement.

Monthly platform credits and monthly service credits are separate pools. The live plan policy sets platform credits. Service credits are granted on the monthly KST anchor, and each account and billing period is processed idempotently.

Backups

Hobby includes one manual database backup with 7-day retention. Pro and Scale include up to 20 manual backups with the retention shown at creation time, plus automatic database backups.

A versioned retention policy is planned for new Pro and Scale backups. After its effective date is announced and the policy is activated, recent restore points will be kept every 6 hours for 72 hours. After that, one successful automatic backup per KST day will be kept so the restore range reaches 30 days. New pre-deploy and pre-restore safety backups will be kept for 7 days.

Until that activation, the expiration time shown for each backup is the applicable retention contract. The effective date will be announced before the new policy starts.

Existing backups are not reclassified or shortened by the new policy. Each backup is deleted only when its own displayed expiration time is reached or when you delete it manually.

Production Deploys

Production apps are available on Pro and Scale plans. Hobby users can still deploy to the dev environment:

gencow deploy          # dev app, available on all plans
gencow static dist/    # dev static hosting, available on all plans

Use --prod for production targets:

gencow deploy --prod
gencow static --prod dist/
gencow env set KEY=VALUE --prod

If your plan cannot use production deploys, the CLI and Dashboard show an upgrade message and the platform rejects the production write.

Custom Domains

Custom domains are available on Pro and Scale plans. Hobby users cannot connect a new custom domain or rebind an existing domain to a different app.

For the end-to-end Dashboard, CLI, DNS, and automatic TLS workflow, see Hosting & Custom Domains.

gencow domain set myapp.com --prod
gencow domain status --prod
gencow domain remove --prod

Unflagged gencow domain status and gencow domain remove are available only to inspect or remove a legacy DEV binding. domain set never accepts a DEV target.

Custom domains can be connected or rebound only on production apps. The server validates the same-owner parent_app_id relationship; an app name ending in -prod is not sufficient. Legacy DEV bindings remain available only for status inspection and removal. They are disabled for serving and TLS.

www hostnames are first-class custom domains. Use a www.example.com CNAME to the selected app target when your DNS provider cannot flatten apex records. Gencow serves a directly connected www domain as canonical and does not redirect it to example.com. Apex domains should use ALIAS/ANAME/CNAME flattening when the DNS provider supports it, or the stable edge IP fallback shown by the CLI.

Existing active custom domains are not removed automatically when a plan changes. Status checks and removal remain available so users can inspect or disconnect their own domains. New domain connections and rebinds still require a plan with the custom-domain capability.

Official Gencow domains such as gencow.app, gencow.dev, and gencow.com are not self-service custom domains. They require platform-admin handling.

Realtime

Realtime limits count concurrent WebSocket connections, not HTTP visitors or static page views. One browser tab with active realtime queries usually consumes one connection.

The account limit is shared across all apps owned by the account. The per-app safety limit prevents one app from consuming the entire allowance. Both are checked when the WebSocket connection opens.

Storage And Images

Storage quota limits the total file storage available to the app. Public website assets and private attachments both count toward storage.

Single-file limits are tiered separately from total quota. Hobby allows 50 MB per file. Pro allows 500 MB per file through browser-direct storage uploads; same-origin API-routed uploads, including CLI/admin multipart paths, are still capped at 50 MB.

Image optimization is always available for safe automatic WebP/downscale paths. Explicit image transforms such as resize, format conversion, and quality control are Pro/Scale features.

See Storage for public/private visibility, read grants, image transform parameters, cache behavior, and tier-specific transform errors.

Credits

Gencow uses two credit pools:

Credit usage depends on the actual workload. AI and document processing costs vary by model, provider, tokens, file size, and output size.

Hosted app traffic analytics are collected through Gencow-owned same-origin routes and shown in the Dashboard. Analytics storage and retention can vary by plan or Enterprise agreement, but the privacy boundary is the same for every plan: raw IP, secrets, session tokens, and private storage grant URLs are not stored. See Hosted App Analytics.

Enforcement Model

Plan limits are enforced in backend routes and runtime gateways, not only in UI:

• App and production-app writes check authenticated ownership.
• App creation and ownership transfer enforce the current plan's app-slot limit.
• Production deploy writes require the production-deploy capability.
• Custom domain set/rebind requires the custom-domain capability.
• Realtime connection limits are enforced at the WebSocket gateway.
• Image transform limits are enforced by storage serving routes.
• Official Gencow domains stay admin-only even when a user has a paid plan.

When a capability is unavailable, the platform returns a plan-limit error and an upgrade path. These errors should not expose other users' app names, tokens, database URLs, provider secrets, or internal infrastructure details.

Related Guides

• Deployment - dev vs production deploys, static hosting, custom domains, CI/CD
• Hosting & Custom Domains - publish an app, configure DNS, and verify TLS
• Realtime - realtime connection behavior and limits
• Storage - file visibility, grants, image optimization, and quotas
• CLI Reference - command flags and --prod behavior