Skip to main content

Your project's infrastructure

Every project's Overview in the dashboard opens with a map of the whole project: your database and, for a cluster, its router and every node; its copy in another zone when it has one; its backups; and the services it runs. Each zone it uses is a panel of its own, and beside the map (or under it, when there are several zones) a note for each zone says what runs there and how it is, in plain words. Details opens the Infrastructure tab, under Manage, which has the same map over a card for each copy and the full list of services. Both only show: nothing on them changes your project.

On the map​

  • Your database, drawn as a drum, with a soft halo while it runs. Its last report from its server follows its name, "10s", and turns amber after a minute without one and red after three.
  • Its backups, beside it: every change, kept in object storage in its region. The line to them carries the word "backups".
  • The router and the nodes, for a project spread over several nodes. The router sends queries to the database and to every node that holds data. A node still standing by is drawn dashed and follows the database; it holds a copy and serves nothing until a table is spread onto it.
  • Its copy in another zone, when the project is set to Never lose a write, in that zone's panel, with what your commits are doing on the line to it ("sync", "waiting", "catching up").
  • Its services, as small tiles under the database, in the zone where they run today: the ones the project runs itself (the Data API, Auth, the AI gateway, Push) and the ones its server shares with other projects (Functions, Realtime, Storage, marked "shared"). A tile's light is green while it runs, amber when its server could not update it, and off while the project is paused.

Green on the map and in the notes means live: running, routing, in sync. Something standing by or paused has a quiet grey dot, never a green one.

On the Infrastructure tab​

Under the map, a card for your database and for its copy in another zone:

  • the region and zone of the server it runs on, and how long ago that server last reported;
  • for a copy in another zone, since when it has kept your writes, and what your commits are doing:
    • Every commit is on two machines: the normal state.
    • Commits are waiting for its copy: a short wait, at most about 20 seconds.
    • Its copy is catching up: until it has, commits are on one machine and in object storage within a minute. This heals by itself.
    • Being made ready: a new copy, for a project just made or just moved up to Pro, until it has caught up with your database, usually within a few minutes. Until then your project is protected as on Stay available.

Then Nodes, for a project spread over several nodes: one line when they all agree ("3 nodes, all in sync"). When one differs, the line names it and the list of nodes opens. Last, Services: each service with where it runs and whether it is running. A function that could not be prepared is named there too.

A state such as "in sync" also says how long it has held ("for 4 days"). That time comes from when the state last changed, so a quiet project's states are often days old, and that is fine. How fresh the page is comes from the servers' reports, which is the line under each copy.

A paused project says so: nothing of its own is running, and it starts on the next connection.

What it never shows​

A server appears only as its region and zone. Neither page ever shows a server's name or address, a storage bucket, or anything about another project, including whether one shares a server with yours.

Services and placement​

Today each service runs beside your database, on its server. When placement covers your project, copies of a service on other servers will appear on the same map.