# Backend tasks

> Data-backed features in plain language — once your project has a Dedicated Cloud, describe what you want and Genesis builds the backend and the UI.

Source: https://support.estage.com/cloud-backend-tasks
Part of the ESTAGE Support help center (https://support.estage.com). Full knowledge base: https://support.estage.com/llms-full.txt

---

Once your project **has an active Dedicated Cloud**, describe the data-backed feature you want
in a normal sentence. Genesis builds the backend part (tables, access rules, server functions)
and the pages that use it, in the same turn. No special syntax needed.

## How to ask

With a cloud active, just ask:

- *"create a table to save user feedback"*
- *"add a feedback form that saves to the database"*
- *"a members feed people can post to, with realtime updates"*

You can also pick **/backend Backend feature** in the `/` menu, which starts the message for you.

## What happens

Genesis checks the cloud's current state first, reads the live database structure before it
writes anything, and then:

- creates or changes tables and their **access rules** (who can read and write which rows),
- turns on realtime where the feature needs live updates,
- deploys server functions and stores the secrets they need,
- builds the UI wired to all of it.

The steps show in the chat's live action list as they run. Genesis also checks that money and
status fields can't be changed by a visitor from the browser, and locks them when they can.

It stays in scope: in *"make the button blue and add email capture"*, only the email capture
touches the backend; the color is a normal edit.

## No cloud yet?

Genesis can't create a Dedicated Cloud from the chat. Set one up in
**Settings → Dedicated Cloud** first, then ask for the feature. See
[Dedicated Cloud](https://support.estage.com/cloud) for plans and setup.

A bring-your-own Supabase project, connected as a [connector](https://support.estage.com/connectors), works with the
same kind of request. A project uses one or the other, not both.

## Things worth knowing

- **Say what must be kept.** Genesis writes schema changes so they can be re-run safely, but it
  doesn't undo them on its own. Before data is deleted, a copy is saved that you can put back
  from [Backups → Change history](https://support.estage.com/cloud-backups#change-history) for 14 days.
- **Be specific.** *"a members feed people can post to, backed by a real database"* reads
  clearly; *"make a feed"* can look like a visual-only request.
- You don't need a cloud for forms that collect leads — those go to your CRM. See
  [Forms](https://support.estage.com/visual-editor-forms).

More detail: [Building backend features with AI](https://support.estage.com/cloud-building-with-ai).