Backend tasks
Once your project has an active Dedicated Cloud, just describe the data-backed feature you want in a normal sentence — Genesis understands the request and routes it to the backend builder. No special syntax needed.
How to trigger it
Section titled “How to trigger it”With a cloud active, just ask:
- “create a table to save user feedback”
- “add a sign-up form that saves to the database”
- “set up user authentication”
- “a newsletter subscribe button that stores emails”
What happens
Section titled “What happens”The backend agent inspects your cloud, creates or updates tables, security rules, realtime, and functions — then the UI is built wired to them. Progress shows in chat (“Cloud: Working on your backend…” with substeps).
It also stays in scope: ask for “make the button blue and add email capture” and only the email capture goes through the backend path — the styling is handled as a normal edit.
No cloud yet?
Section titled “No cloud yet?”Genesis offers to provision a cloud when it notices your request needs one (a chip-question: “This needs a backend — want me to set one up?”). Accept it and, on an active subscription, the cloud is provisioned for you before the feature is built.
- No cloud yet — just describe the feature; Genesis offers to set up the backend it needs.
- Be specific — a clear ask like “build a members feed people can post to, backed by a real database” reads unambiguously; a vague “make a feed” can look like a visual-only request. The more concrete the request, the better the result.
Full backend docs: Dedicated Cloud.