Self-Hosted: Deployment Overview

This page primarily applies to self-hosted scenarios. If you are a regular user of the managed platform spg99.ru, you can skip it: all components described below are already deployed and operated by SPG99 infrastructure.

What is usually needed for a self-hosted installation

A minimum setup includes:

• a Kubernetes cluster;
• persistent storage for stateful components;
• S3-compatible object storage;
• DNS / ingress / load balancers to publish Gateway, Control Plane, and Console;
• secrets and TLS materials;
• monitoring / logging backends.

Which services are deployed

A typical installation includes:

• control-plane;
• gateway;
• provisioner;
• pageserver;
• safekeeper;
• console;
• optionally landing and admin.

What is important to understand architecturally

• compute starts on demand and usually does not store durable state locally;
• reliability is built around pageserver + safekeeper + object storage;
• for the user, PostgreSQL is still available through a single Gateway.

When self-hosted makes sense

This scenario is for teams that want to manage the entire environment themselves: networking, secrets, storage, ingress, and the release cycle. For most users of spg99.ru, this is not necessary — that work is already handled by the platform infrastructure.