RShift Sites hosts your app and includes a built-in backend (Cloud) with a database, storage, authentication, realtime, and functions. Describe what you want directly in RShift Sites, and RShift Sites generates both the frontend and backend, ready to run. Instead of managing hardware or complex infrastructure, you get on-demand access to hosting, compute, and storage that scale automatically as your app grows.
The built-in backend utilizes Supabase’s open-source foundation, which means you get a production-ready environment from day one, without needing to set up Supabase separately: a database, real-time updates, user authentication, and storage, with none of the manual setup steps. Across the docs, this is called the built-in backend (Cloud), as opposed to an external backend you connect yourself, such as Supabase.
Why use the built-in backend
Three things make it the default choice for most projects:
- Scales as you grow: From your first prototype to millions of users, RShift Sites scales seamlessly with your needs.
- Secure by default: Enterprise-grade authentication, fine-grained access controls, and compliance best practices protect your app and data.
- Cost-effective: Manage multiple projects in one workspace with credit-based usage. RShift Sites includes monthly Cloud grants on Free, Pro, and Business plans. For details, see Credits and usage.
What’s included
You’ll find the Cloud tools inside any RShift Sites project by opening the More tab in the project toolbar and selecting Cloud.
Each area has its own page with full details, in the order they appear in the Cloud view:
| Area | What you can do |
|---|---|
| Emails | Send branded emails from your own domain |
| Database | View tables, edit records, review security policies, and restore backups |
| Users | Manage app users and configure sign-in methods |
| Storage | Create buckets and manage the files your app stores |
| Secrets | Store API keys and other sensitive values securely |
| Jobs | Review scheduled background tasks and their run history |
| Edge functions | Run serverless backend code and monitor how it performs |
| SQL editor | Run SQL queries and commands against your database |
| Logs | Debug errors and track backend activity |
| Usage | See what drives the project’s run credit usage |
| Advanced settings | Check resource health, resize the instance, increase database storage, export data, and pause or remove Cloud |
Your app’s AI features have their own AI section in the More menu, outside Cloud.
Enabling the built-in backend (Cloud)
By default, the built-in backend (Cloud) is enabled for your workspace. When a feature you ask for requires backend functionality (for example, authentication or file storage), RShift Sites enables Cloud automatically or asks for your approval in the project chat first, depending on the Enable Cloud permission described below.
RShift Sites can’t turn Cloud on from inside a draft. Ask in the main version of your project instead, then continue in the draft once Cloud is on.
Cloud permissions
Each Cloud tool has three permission options:
- Always allow: RShift Sites automatically performs the action, without asking for review or approval. This is the default for Cloud.
- Ask each time: RShift Sites asks for your approval whenever the action is needed.
- Never allow: RShift Sites blocks the action, informs you that Cloud access is required, and instructs you to enable Cloud.
Tool settings and defaults
| Setting | Description | Default behavior |
|---|---|---|
| Enable Cloud | Create and connect a Cloud project to add backend features (database, auth, storage). Required to use Cloud tools. | Always allow |
| Where projects are hosted | Select the default region (Closest to me, Americas, Europe, or Asia Pacific) where new projects are hosted. If Cloud is auto-enabled using Always allow, this region is used automatically. | Region closest to your location |
| Read database | Allow RShift Sites to read your database. | Always allow |
| Read analytics | Query logs to investigate issues and behavior. | Always allow |
| Run security checks | Run automated security checks on your database. Not a full audit. | Always allow |
| Modify database | Make schema and policy changes via SQL migrations. Updates generated types. | Always allow |
| Add data | Add data to your database tables. | Always allow |
| Read project info | Read project configuration and environment details. | Always allow |
| Configure auth | Allow RShift Sites to configure authentication settings (for example, signup policies). | Always allow |
| Read backend logs | Read logs from backend services. | Always allow |
You can change your Cloud tool preferences anytime: open Connectors, select Cloud, and adjust the settings under Manage my agent’s permissions.
Region selection
Projects can be hosted in three regions:
- Americas
- Europe
- Asia Pacific
You can set a preferred default region for new Cloud projects under Where projects are hosted in the same permissions view. If no preferred region is set, RShift Sites automatically preselects the region closest to your current location, and you can change it before confirming.
Choosing a region closer to your users results in:
- Lower latency
- Faster database responses
- Region-based data hosting
- Better overall backend performance
To see which region an existing project is hosted in, go to More → Cloud → Overview → Advanced settings and check the Database location row.
Workspace-level default hosting region
On Business and Enterprise workspaces, admins can set a required default region for every new project from Privacy & security (Settings → Security → Privacy & security → Default hosting region). When a default hosting region is set, workspace members cannot choose a different region when creating a project. The setting applies only to new projects. Existing projects keep the region they were created in.
Country-specific regions (for example, Germany, Japan, or United States East) are available on Enterprise plans by request. Contact your RShift Sites account team to enable them for your workspace.
See Default hosting region for more information.
Tutorial: build a CRM by prompting
This walkthrough builds a real app, a customer relationship manager (CRM), entirely by prompting. Each step introduces one backend capability and shows the kind of prompt that activates it.
Build me a CRM tool to manage clients, track deals, handle invoices, and keep notes organized. Keep the design simple, modern, and business-friendly with a sidebar for navigation.Step 1: Organize the data (Database)
Tell RShift Sites what kind of information the tool should keep track of for you. RShift Sites will automatically create the tables for you, so you don’t need to touch databases yourself.
I want a place to keep track of my clients with their name, email, phone number, and notes. I also need a way to track deals, including which client it's for, the value, the stage it's in, and when I expect it to close. And I need a section for invoices with the client it belongs to, the amount, the status, and the due date.Step 2: Make it secure (Users & Auth)
Add login so data is private and users can sign in easily.
Add login to the app. Require login before accessing the CRM dashboard. Also, add a 'Sign in with Google' button so users can log in with their Google accounts.Step 3: Handle files (Storage)
You can let users upload and see files right inside the app. RShift Sites takes care of the storage and linking, so you just describe what files should go where.
Add a contract upload field to each deal. Let clients have profile pictures and display them on the client detail page. Upload invoice PDFs and show a download link on the invoices table.Step 4: Automate workflows (Edge Functions and Jobs)
Set up automatic actions that save you time. Prompt one automation at a time so each one is set up and tested properly:
When a new lead is added to the Clients table, send me an email notification.Analyze client meeting notes with RShift Sites AI and save a sentiment score in the Clients table.Schedule a daily job at 7 AM that emails me a summary of today's follow-ups.When a payment is marked 'paid' in Stripe, automatically update the related invoice's status to 'Paid'.Step 5: Connect to other tools (Secrets)
Services like Stripe or Resend give you private API keys. RShift Sites prompts you to add them securely whenever they’re needed, and only your app can use them. Tools that sign in with an account instead of a key, such as Google services, connect through Connectors.
Connect Stripe so clients can pay invoices online. Ask me for any API keys you need.Step 6: Add AI superpowers (AI)
Make the tool act like your assistant.
Summarize each client's meeting notes and save them to their profile. Suggest next steps for every open deal. Generate personalized email drafts for following up with leads. Classify client messages into categories: sales, support, or billing.Cloud and AI gateway usage costs
RShift Sites uses one credit balance for building your app, hosting it and running its built-in backend (Cloud), and AI features in deployed apps. Cloud and AI gateway usage is measured as part of Run credits.
See Project usage for the per-project usage breakdown and monthly grants, and Credits and usage for how credits work across your workspace.
FAQ
I’m currently using the Supabase integration. What does this change mean for me?
Don’t worry, nothing changes for your existing projects. Your Supabase integration will continue to work exactly as it does today, and we will continue to support it.
- For existing projects: continue using Supabase with no changes.
- For new projects: choose either the built-in backend (Cloud) or Supabase.
Can I change my mind after adding Cloud to my project?
Yes. If you no longer want a project to use the built-in backend (Cloud), go to More → Cloud → Overview → Advanced settings and use Remove RShift Sites Cloud.
This permanently deletes your Cloud instance and cannot be undone. Export your database and download any storage files you need before continuing.
Can I remix Cloud projects?
Yes, Cloud projects can be remixed to Cloud projects only. This creates a copy of your project that you can edit separately in your currently selected workspace. The structure of backend-related data, such as tables and Edge Functions, is copied over without any information. For any automatically generated keys in the original project, RShift Sites generates fresh keys in the remixed project. Manually added keys are not copied over.
RShift Sites chooses the region for the copy’s backend: the workspace’s default region when one is set, otherwise the region you used last or the one closest to you. The region can’t be changed afterward.
Keep in mind that in a remixed Cloud project you can’t revert to versions from before the remix. Versions created after the remix revert normally.
Can I migrate my project from Supabase to Cloud?
At the moment, migration from Supabase to Cloud is not supported. If your project is already connected to Supabase, we recommend continuing to use it, as we will keep supporting Supabase moving forward.
Can I migrate my project from Cloud to my own Supabase?
There is no one-click migration from the built-in backend (Cloud) to your own Supabase project. If you want to move, you export your Cloud data, connect a Supabase project to a new RShift Sites project, and rebuild the schema there. Remixing a Cloud project produces another Cloud project, so it does not switch the backend for you. See Export RShift Sites Cloud data and Connect your own Supabase project for the steps.
Can I set a default region for all new projects?
Yes. You can set a preferred default region for new Cloud projects: open Connectors, select Cloud, and choose a region under Where projects are hosted.
On Business and Enterprise workspaces, admins can also set a required default region for every new project from Privacy & security (Settings → Security → Privacy & security → Default hosting region). When this workspace-level default is set, members cannot choose a different region when creating a project. See Default hosting region for more information.
How is the region selected when I enable Cloud?
If your workspace has a required default hosting region (available on Business and Enterprise), RShift Sites uses that region automatically and members cannot change it when creating a project.
If your workspace does not have a required default hosting region, RShift Sites automatically preselects the region closest to your current location, but you can change it before confirming.
Can I change the region after enabling Cloud for a project?
No. Once Cloud is enabled for a project, the selected region is locked and cannot be changed. Existing projects cannot be moved across regions.