Console: Overview

SPG99 Console is the user-facing web interface of the SPG99 platform. Through it, users do most day-to-day work with their account and databases: sign in, create tenants and databases, get connection strings, monitor metrics, view logs, check limits, and contact support.

Put simply, Console is the control point for your part of the platform.

How Console fits into the system

For the user, the chain looks like this:

User -> Console -> Control Plane -> platform services -> monitoring and logging

The role of each link is very simple:

• the user works in the browser through Console;
• Console sends commands to the Control Plane;
• the Control Plane performs management operations and returns resource state;
• separate monitoring and logging layers provide metrics, logs, and diagnostic data back to Console.

This gives three clear advantages:

• a single point of entry for management;
• fast access to the real state of resources;
• transparent diagnostics without switching between different systems.

Main interface sections

Console usually includes several key sections:

• Overview — an account summary: tenants, databases, active and stopped resources, recent activity, usage, and quick actions.
• Tenants — create tenants, view their contents, and retrieve template DSNs and credentials.
• Databases — a single list of all account databases, search for the required database, and quick access to its details page.
• Monitoring — metrics, logs, active queries, query statistics, and operations.
• Activity — a working log of actions initiated through the UI.
• Settings — profile, token, limits, logout, and account deletion.

The interface usually also provides language switching, theme selection, a documentation link, and a support form.

Login and security

Console login uses two inputs:

• email;
• API token.

During login, Console validates the token through the account profile in the Control Plane and then opens a private working session. In practical security terms, the following matters:

• the token is validated before login;
• user sections are unavailable without authentication;
• the token is stored in a protected HttpOnly cookie rather than being sent by the frontend as an open parameter in every request;
• management requests go through a server-side proxy to the Control Plane;
• the session is cleared on logout.

If some actions are unavailable in the UI, the reason is usually one of two things:

• the token does not have enough permissions;
• the Control Plane is temporarily unavailable.

Why Console is convenient for the user

Console is valuable not only because it lets you create databases. Its main benefit is that it brings the entire resource lifecycle together in one place:

• creation;
• connection;
• observation;
• diagnostics;
• support;
• limit control;
• support requests.

Because of this, the path from “created a resource” to “connected the application and checked the logs” takes a minimum number of steps, and the platform state remains transparent even when the number of projects and databases grows.