eCG Cloud: data and actions

eCG Data: your app's database

eCG Data is your app's own database. Learn how to set it up, read its status, check how safe each table is, and fix an app that shows an error.

eCG Data is the database of one app. It holds everything the app needs to remember: orders, bookings, sign-ups, stock counts and customer details. Each app has its own, kept apart from every other app.

You do not need to design it. When you ask the agent for a feature that stores information, the agent creates the tables for you. You use this page to check that eCG Data is healthy and to see what it holds.

Set up eCG Data

You can set it up in two ways. Both end in the same place.

From the Cloud page

  1. In the left sidebar, under Platform, select Cloud.
  2. Select Set up eCG Data. A list titled Create it for which app? opens.
  3. Choose the app. Its console opens.
  4. Select Provision.

If every app already has eCG Data, the list says "Every app already has eCG Data."

From the app's settings

  1. Open the project in the editor, open More actions, then Project settings.
  2. Under eCG Cloud, select eCG Data.
  3. Where it says No database yet, select Provision.

Setup takes a minute or two. You can leave the page. When it finishes, you see "Database provisioned!" and the console opens on the Overview tab.

Read the list of apps

On the Cloud page, the eCG Data tab lists every app that has it. Each row shows the app name, a short internal name for its database, a status, and the dates Created and Updated.

  • Type in Search eCG Data to find an app by name.
  • Use All statuses to show only active, provisioning or error apps.
  • The line at the bottom reads "Showing 3 of 5" when a filter is on.
  • Select a row to open that app's console.

What each status means

Status What it means What to do
active eCG Data works. Nothing.
provisioning It is being created. Wait a minute or two, then select Refresh.
deprovisioning It is being removed. In the console this reads Removing…. Wait. The row disappears when it is done.
error Setup failed. The reason is shown under the app name. Open the app and select Retry. See below.

If an app shows an error

An app in the error state counts under Need attention at the top of the Cloud page, and a card named Needs attention appears above the tabs.

  1. Select Open console on that card, or select the row.
  2. Read the red Provisioning failed card. It repeats the reason.
  3. Select Retry. The button reads Retrying… while it works.
  4. If the error returns, contact support and tell them the app name and the reason shown.

An app that fails to turn on is not charged.

Check the health of the data

Open an app's console. It starts on the Overview tab. Next to the app's internal name you see two badges:

Badge Meaning
Active, Provisioning…, Removing… or Error The state of eCG Data itself
Connected with a number such as "(24ms)" Your app can reach its data. The number is the reply time.
Disconnected Your app cannot reach its data right now. Hover over the badge to see the reason, then try Refresh or come back later.

Three tiles sit below:

Tile What it tells you
Speed How fast eCG Data answers, in milliseconds
Storage How much space the data uses
Security How many tables have row protection switched on, for example "3/4"

If the console cannot reach the data at all, a red line says Unreachable.

See how well each table is protected

Under Your tables, each table shows its approximate number of rows, its size and one badge.

Badge What it means
RLS off (red) Row protection is switched off. Anyone holding your app's public key can read this table. Ask the agent to protect it.
deny all (amber) Protection is on, but no rule lets visitors in. Visitors using the public key can neither read nor change it. Your app's eCG Actions still can.
2 policies (green) Protection is on, with one or more access rules that say who can do what.

New tables are created as deny all, so a table is private until a rule opens it. If the Security tile shows a warning such as "1 table with no policy (deny all)", that is a reminder, not an error. A table meant to be private should stay that way.

The Advanced details section, closed by default, holds technical numbers for people who are tracing a performance problem. You do not need it day to day.

How the agent uses eCG Data

  • The agent creates tables, adds columns and fills in starting data.
  • Changes that alter the structure of your database wait for your approval before they run. See Approve database and server changes.
  • The agent reads the current table list at the start of every request, so it knows what exists. You can say "add a phone column to customers" and it adds only that.
  • Keys that connect your app to its database are added to Secrets for you. You cannot edit or replace them. See Store keys and secrets safely.

If you press Sync in the console header, eCG Data sends the latest keys to your live preview. You need this only if the preview cannot find its data after you changed a secret. The button shows "Synced 4 secret(s) to the live preview" when it is done. On a phone, Sync and Delete sit under the three-dot More actions menu.

Connect other tools

If you also use Claude, Cursor or another AI tool, you can let it read your tables with an access key. See Connect other tools with access keys.

To think about how to organise what you store, see Organize your business data.

Delete eCG Data

Select Delete in the console header. A box titled Delete database opens.

  1. Read the warning. It says the database and all its data are deleted and this cannot be undone.
  2. Type delete my database in the box.
  3. Select Delete permanently.

The message "Database removed." confirms it.