Skip to content

Dedicated Cloud overview

Dedicated Cloud is your project’s own backend. Where a regular site just shows things, a site with a Dedicated Cloud can do things: store data, sign users in, update live in real time, accept file uploads, and run server-side code.

It’s fully managed — you pick a plan, Genesis provisions everything, and both you and the AI work with it from there.

You don’t need a Dedicated Cloud for a normal marketing site, landing page, or blog. You do need it the moment your site has to remember or react to anything:

  • Member areas and user accounts (sign up / log in)
  • Feeds, comments, likes — anything visitors create
  • Custom forms whose data you want to own and query
  • Live features: chat, counters, dashboards that update without refresh
  • File uploads from visitors
  • Server logic: notifications, scheduled work, payments glue

Six tiers, from a starter for small sites to enterprise-grade compute. Every tier is a dedicated instance with daily backups:

PlanComputeGood for
Starter2-core · 1 GB RAMSmall sites, up to a few hundred users
Standard2-core · 2 GB RAMGrowing apps
Plus2-core · 4 GB RAMBusy production apps
Pro2-core · 8 GB RAMHigh-traffic products
Scale4-core · 16 GB RAMData-intensive workloads at scale
Max8-core · 32 GB RAMEnterprise workloads

Current monthly prices are shown in the plan picker. Billing is monthly to your card; upgrade or cancel anytime.

Click the plan pill (or Upgrade) in the Cloud workspace header, pick a bigger tier, and confirm. The difference is charged immediately (prorated), compute resizes in minutes, and your database stays online — no downtime.

  1. Open Project Settings → Dedicated Cloud (or the full-width Cloud page from your project).
  2. Pick a plan and click Activate Dedicated Cloud.
  3. Pay with a saved card or a new one.
  4. Watch the “Setting up your cloud…” status — provisioning usually takes a few minutes.
  5. When the status flips to Active, your workspace opens with six tabs.
TabWhat you manage there
DatabaseTables, rows, access policies, realtime, SQL editor
AuthYour site’s user accounts and sign-in providers (Google, GitHub…)
EmailThe emails your site sends for sign-up, password reset, magic links
StorageFile buckets and uploads
FunctionsServer-side code (edge functions) with logs
SecretsEncrypted API keys for your functions

You rarely have to build any of this by hand — the AI creates tables, policies, and functions for you when you ask for features. The workspace is where you see and manage what exists.

Start with Building backend features with AI →