Atoms Cloud Database stores and manages the structured data your app relies on, including products, bookings, orders, form submissions, and user-generated content. In the Database module, you can view environments and tables, search and edit records, inspect table structures, and import or export data using CSV files.

This guide covers the database built into Atoms Cloud. If your project uses Supabase, see Supabase Connect instead.

Open a database

Before opening a database, connect your project to Atoms Cloud. If it is not connected yet, follow the connection steps in Atoms Cloud.

1. Open your project on a desktop device.
2. In the same workspace toolbar where the App Viewer is, select Atoms Cloud.
3. Select Database in the Atoms Cloud sidebar.
4. Under Databases, select which database you want to inspect. The Development and Production database cards appear when they are available for the project.

Each database card shows how much storage is being used and the total amount available. Use Development while building and testing your app. Changes made in Production may affect the live app’s data, so always check which environment you are in before making changes.

Choose the Development or Production database.

Browse and filter table data

1. Select the Development or Production database card, depending on the environment you want to work in.
2. Use Search tables to find a table, or select one directly from the list. Each table card shows its row count and whether it is read-only.
3. Use Search rows to search within the current table, or select Filter to narrow the results using one or more fields.
4. Use the page arrow controls below the table to view additional rows.
5. To inspect the table’s structure, open the ••• menu and select Schema.

The Schema view shows each field’s name, data type, key status, requirements, constraints, and default value. Select Copy to copy the displayed schema.

Add, edit, or delete rows

When you have found the database you want to make changes to, you can use these actions to do so:

Operation	How to do it
Add a row	Open ... and select Add Row. Enter values that match the available fields, then submit the row.
Edit a row	Double-click a cell and enter the new value. Select Commit Changes to save all pending edits, or Discard to remove them.
Delete rows	Select one or more rows, select Delete, then confirm. Row deletion cannot be undone.

Adding a row or confirming a deletion applies the change immediately to the selected database. Only inline cell edits require you to select Commit Changes or Discard. If you have any pending edits, commit or discard them before adding a row, importing or exporting a CSV file, changing the search or filters, or navigating to another page.

If the project is in a workspace, only Editors and the workspace owner can edit rows in writable tables. If Atoms cannot detect a primary key for a table, you cannot edit or delete its rows because Atoms cannot reliably identify individual records.

Review a pending row edit, then commit or discard the change.

Create tables or change the schema

Open the database environment you want to update, then follow the instructions for the change you want to make:

Operation	How to do it
Create a table	In the table list, click ..., and select Create table. Enter a valid table name and the initial fields, then submit the request. Wait for the Agent to finish, reopen Database, and verify the table.
Change the schema	Click the table you want to make changes to, then click ..., and select Schema. Use Add Field to create a field, or select an eligible field to edit it. You can change its name, type, default value, required status, or uniqueness. You can also mark non-key fields for deletion. Select Submit Changes to send the request to the Agent, or Discard to clear your pending changes.

Only the workspace owner can create tables or change a table’s schema.

Submitting a schema request does not mean the migration is complete. Wait for the Agent to finish, verify the result in Database, and test your app afterward. Primary-key fields and read-only tables cannot be modified this way.

Enter the new field’s details in Add Field.

Review pending schema changes before selecting Submit Changes.

Import or export CSV data

Select the table you want to work with, then follow the instructions for the relevant operation:

Operation	How to do it
Import CSV	Click ... and select Import CSV. Choose a .csv file no larger than 10 MB, then review the file name, estimated row count, selected table, and environment before confirming. The CSV columns must match the table schema. Imported rows are added immediately and cannot be automatically undone, so consider exporting the existing data first.
Export CSV	Click ... and select Export CSV. If a search or filter is active, only the matching rows are exported. Otherwise, all data from the current table is exported.

Only the workspace owner can import or export CSV files. For read-only tables, Export CSV is the only available option.

Permissions and protected tables

Action	Who can perform it	Additional requirements
Add, edit, or delete rows	Editor or workspace owner	The table must be writable. Editing and deleting rows also require primary-key information.
Create tables or change schemas	Workspace owner	Primary-key fields and read-only tables cannot be modified.
Import or export CSV files	Workspace owner	CSV files cannot be imported into read-only tables.

Protected system or user tables may display a Read-only badge. You can view their data and inspect their schema when available, but you cannot modify their rows or structure from this page.

Fix common database problems

“No databases found” or “No tables found”

Make sure Atoms Cloud is connected to the project. If it is already connected, confirm that your app includes a feature that stores persistent data. If needed, ask the Agent to add the database-backed feature. Once the Agent has finished, reopen Database or select Refresh.

A database action is missing or unavailable

Check whether the table has a Read-only badge, then review the permissions above to confirm that your workspace role allows the action. Editing and deleting rows also require primary-key information.

Pending row edits can prevent other actions. Select Commit Changes or Discard before adding a row, importing or exporting a CSV file, changing the search or filters, or moving to another page.

If the action is still unavailable after these checks, contact Support and include the project or Chat link, environment, table, workspace role, action attempted, and exact error text.

A CSV file cannot be imported

Only the workspace owner can import data, and the destination table must be writable. Make sure that:

• The file uses the .csv format.
• The file is no larger than 10 MB.
• Its columns and data are compatible with the destination table’s schema.
• You have committed or discarded any pending row edits.

If the import still fails, contact Support and include the project or Chat link, environment, destination table, workspace role, file name and size, action attempted, and exact error text.

FAQ

My production database is not syncing. What should I do?

If Development works normally but the live site (Production) shows missing tables, columns, or migration errors:

Important: Do not rebuild or overwrite the production database on your own.

Information needed:

• Chat link and live URL
• Full SQL error message
• Missing table/column names
• Last database schema change
• Last working live version
• Whether production data must be preserved
• Whether you want to fully sync Development data or only fill in missing structures

Contact support with these details so we can compare Development/Production versions, migration status, and schema differences before making changes.

Why is my development data different from production data?

If you've published multiple times but Production still shows old data while code updates work fine:

Before contacting support, confirm:

1. Must the current production data be preserved?

2. Do you want to fully overwrite with current Development data, or only fill in missing records?

3. Do you already have a backup?

4. What is your acceptable maintenance window?

We will not overwrite or rebuild production data until the data handling goal is confirmed. Provide the Development/Production URLs and example record IDs or counts showing the difference.