Skip to main content

Use Builder Cloud for backend features

Builder Cloud is the managed backend layer for hosted OXVO Builder apps.

Use it when an app needs more than frontend code and preview.

When Builder Cloud is required​

Turn on Builder Cloud before asking Builder to add:

  • email/password auth
  • user accounts
  • database tables and records
  • file uploads or managed storage
  • secrets
  • API routes or server-side business logic
  • scheduled jobs or webhooks

For frontend-only work, you can stay in the default Builder flow.

What happens when you enable Cloud​

When you enable Cloud for an app:

  1. You choose a region.
  2. Builder provisions a managed regional backend for that app.
  3. Builder writes the managed connection into the app runtime.
  4. The current product UI and routes stay intact during setup.
  5. Builder opens the Cloud workspace panel for that app.

In hosted Builder, region choice is permanent for that app after Cloud is enabled.

What the Cloud panel includes​

The Cloud panel is organized into app-level backend operations:

TabWhat it is for
OverviewCurrent cloud status, region, usage summary, and workspace-level context
DatabaseBrowse tables, inspect rows, and understand schema state
UsersReview app users and basic signup/user activity context
AuthConfigure sign-in methods and auth-related options
StorageReview database size and workspace storage usage
SQL EditorRun SQL for managed database work when needed
UsageCheck Cloud consumption and project-level cost signals
LogsInspect recent backend and app activity
SettingsReview Cloud status, billing safety, and removal controls

Auth in Builder Cloud​

Builder Cloud is the default backend path for hosted auth work.

That means if you ask Builder for:

  • sign in
  • sign up
  • protected routes
  • account-backed features

Builder should use the managed backend path instead of a frontend-only mock.

The Auth area can also extend the standard auth setup with social providers or plugins when your app needs them.

Users, database, and storage​

After Cloud is enabled, Builder gives you app-level operational visibility:

  • inspect tables and row counts
  • browse app users
  • review storage usage and largest tables
  • use SQL tools for targeted database work

This makes it much easier to verify that backend features are behaving like real product features, not demo placeholders.

Usage, limits, and billing safety​

Builder Cloud usage is workspace-scoped.

Important expectations:

  • workspaces include a monthly Cloud allowance before overage billing applies
  • Cloud usage is separate from Builder AI credits
  • Builder can warn or restrict Cloud access if billing issues are not resolved

Open the current workspace in OXVO when you need plan or billing changes.

Remove Cloud carefully​

Builder can remove Cloud from an app, but this is a destructive action.

Removing Cloud also removes the managed backend relationship for that app, including hosted auth and data access tied to the managed Cloud setup.

Use removal only when you are certain the app should no longer rely on Builder Cloud.

  1. Finish the core frontend flow first.
  2. Enable Cloud only when backend features are real requirements.
  3. Add auth or schema changes one feature at a time.
  4. Verify the flow in preview before moving on to deployment.