Service Roles in the Chain

To use SPG99 confidently, it helps to understand the role of each service in the overall chain.

Landing

Landing is the public entry point of the platform: the website, documentation, and general product information.

Console

Console is the main user-facing web interface. It is used to create tenants and databases, retrieve a DSN, and inspect logs, metrics, and activity.

Control Plane

Control Plane is the management core of the platform. It:

• stores the resource catalog;
• issues credentials;
• tracks database state;
• manages leases;
• coordinates writer startup and stop;
• runs the autoscaler and profile handoff.

Gateway

Gateway is the single PostgreSQL entry point. Applications, drivers, and psql connect to it.

It:

• accepts TLS connections;
• checks tenant credentials;
• wakes the database when needed;
• holds the lease;
• freezes new checkouts during controlled cutover;
• routes traffic to the active writer.

Provisioner

Provisioner materializes the decision “a writer must be started” into a real compute resource. In the new autoscale scheme, it also participates in preparing the candidate generation.

Compute

Compute is PostgreSQL itself, which executes SQL and serves active workload. In the new model, it starts from soft basebackup and keeps only the minimal local working layer.

Pageserver

Pageserver:

• serves soft basebackup;
• stores data history;
• handles remote read-through;
• allows the writer to start without a full local user-data disk.

Safekeeper

Safekeeper is responsible for WAL durability and, through that, for write reliability.

Observability

Platform metrics and logs are collected separately and are available through Console and dashboards. Because of that, SPG99 remains for the user not a “black box,” but a transparent system with understandable diagnostics.

Short chain for the user

Console / API -> Control Plane -> Gateway -> Compute -> storage chain

The most important thing to remember from this chain is simple:

• the user always works through Console, the API, and Gateway;
• the storage chain is responsible for reliability;
• Compute is responsible for SQL speed;
• the autoscaler safely manages transitions between writer generations.