Manage your data

The Backend view shows what is in your project’s backend: its tables, users, files and logs. Open it from the switch at the top of a project by clicking Backend.

What each section shows

Section	What you can do there
Database	See every table and its estimated row count. Click a table to see up to 100 rows. Click a row to edit it, then click Save
Storage	See your storage buckets and whether each is Public or Private
Authentication	Choose whether people can sign up, and set up the Email, Phone and Google sign-in methods
Users	A chart of sign-ups over the Last 90 days, Last 30 days or Last 7 days, and a list of recent users
Secrets	Add, see and delete API keys. See Secrets and outside APIs
Logs	Pick a log type, like Function Edge Logs, Authentication Logs or PostgreSQL Logs, to see recent activity and errors
Suggestions	Security and performance advice for your backend, marked ERROR, WARN or INFO

To look something up, click Query your database in the Database section, write a query and click Run Query. Queries there only read data. To change the shape of your tables, ask the Polymet Agent in the chat.

What the agent does, and when it asks

The agent writes the backend code for you: tables, the rules for who can see each row, and functions. Some steps run on their own. Steps that change your live backend wait for you.

The agent wants to	You see	It waits for you?
Check the backend, list tables, functions or secrets, read logs	A card such as Checked integration status or Retrieved backend logs	No
Write a new table change into your code	Created database migration	No. Nothing changes in the database yet
Apply table changes to the database	Deploy database migrations now?	Yes: Deploy or Reject
Run a query against your data	Accept this SQL query on your database?	Yes: Accept or Reject
Put functions live	Deploy backend endpoints now?	Yes: Deploy or Reject
Remove live functions	Delete these backend endpoints?	Yes: Delete or Reject
Store an API key	A form titled Requesting backend secrets	Yes: Deploy Secrets or Skip

The arrow next to Deploy, Accept or Delete opens Accept all in this session. It approves every later confirmation in the session without asking, including calls to your agent connectors.

On a branch

Every branch shares the project’s one backend. So on a branch the agent does not apply table changes, put functions live or remove them, or set secrets. You see a card such as Migrations not deployed — runs on main only, where main is your default branch’s name. Table changes the agent writes on a branch stay in that branch’s code. Merging does not apply them. After you merge, switch to the default branch and ask the agent to apply the pending migrations.

Add a backend — enable the backend and what comes with it
Secrets and outside APIs — store keys for payment and email services
Branches — what runs only on the default branch

Get started

Design on the canvas

Backend

Publish and share

GitHub

Polymet MCP server

Design systems

Work together

Plans and credits

Agent connectors

Settings and account

Help

What each section shows

What the agent does, and when it asks

On a branch

​What each section shows

​What the agent does, and when it asks

​On a branch

​Related

What each section shows

What the agent does, and when it asks

On a branch

Related