Platform services
Load balancers, managed databases and a container registry, managed in the same account as your servers.
The building blocks around your application
Platform services are the managed parts you would otherwise run yourself: traffic distribution, databases, container images and the tools to deploy them. Each is created in the same account, the same project and the same VPC as your servers, and each shows up on the same invoice. You choose a region and a plan, and the platform builds and maintains the rest.
- Managed load balancers, public or private, in all 12 locations
- Managed database clusters, created next to the networks they use
- Private container registry with vulnerability scanning
- REST API, Go SDK, Terraform and CLI for every service listed here
Load balancers
A dedicated instance in front of your application, not a slice of a shared appliance. Capacity is yours alone, and its traffic, certificates and configuration are isolated from other customers.
Public or private
A public one has an internet IPv4 address and is the single entry point while your servers keep private addresses. A private one lives inside a VPC and balances traffic between tiers. Backends in several VPCs are attached automatically.
Protocols
HTTP, HTTPS, HTTP/2 and WebSockets for web traffic. TCP on any port for databases, mail, MQTT and other services, with TLS passthrough when you want the backend to hold the certificate.
One IP, many rules
Run HTTP on 80, HTTPS on 443 and a TCP service on 5432 behind the same address. Each rule pairs a protocol with a front port.
Host-based routing
On HTTP rules every domain or subdomain is matched by its Host header and sent to its own server pool, with its own back-end port, scheme, algorithm and health check.
Client address preserved
Your application still sees the visitor. The original IP and scheme arrive in X-Forwarded-For, X-Forwarded-Proto and X-Forwarded-Host, or through the PROXY protocol on TCP rules.
Changes without drops
A new domain, an extra server or a renewed certificate is applied with a graceful reload, so connections in flight finish normally.
Certificates and health checks
The two settings that most often break a front door are handled by default and can be tuned per domain.
| Setting | Default or behavior | What you can change |
|---|---|---|
| Check interval | 1,000 ms between probes of each server | Interval, timeout and request path per domain |
| Response timeout | 500 ms | Set per domain; TCP-only checks are available |
| Unhealthy threshold | 2 failures in a row remove a server | Raise it for slow-starting applications |
| Healthy threshold | 5 successes in a row bring it back | Lower it for faster recovery |
| Algorithm | Round robin | Least connections, plus cookie-based sticky sessions with a cookie name you choose |
| Certificates | Let's Encrypt for the domain and its wildcard in one DNS-validated certificate, renewed inside a 32-day window | Upload your own certificate; SNI lets each domain present its own |
| HTTP to HTTPS | One switch per domain sends port 80 visitors to the secure site with a 301 | On or off per domain |
Global front door and extended settings
Any reachable IPv4 address can be a backend: VPSie servers in other regions, other clouds, on-premises hosts or external sites. Health checks fail traffic over when a site goes dark, and a standby pool can take over only when the primary fails.
- Publish regional load balancers through VPSie DNS, one hostname per region or one shared hostname
- Front an on-premises system first and shift traffic to VPSie as workloads move
- Path and URL-prefix routing, weighted canary pools, mutual TLS and HTTP/3 are enabled by VPSie Support through a ticket
- Heavy settings such as compression and caching need CPU headroom; Support recommends a plan
Databases, registry and deploy tools
Managed database clusters are created and listed through the console, API, Terraform and CLI, next to the networks they run in, and can be reachable only inside the VPC. Container Registry holds your images privately and works with standard docker login, tag, push and pull.
- Registry repositories can be public or private per repository
- Vulnerability list for any image tag, with a severity breakdown, and automatic scanning you can enable per repository
- Create a registry in the location closest to your clusters and assign it to a project
- 22 registry API operations, plus vpsie_registry and vpsie_managed_database Terraform resources
Observe and protect the traffic path
Load balancers connect to the rest of the platform instead of standing alone.
Graphs and alert rules
CPU, memory, disk and network graphs from an hour to a year, with PDF export. Threshold rules send email and can reboot, power off or auto-scale on a crossing.
Firewall on the balancer
Firewall groups, IP allow and deny lists, geo-blocking and per-client rate limits are enabled by VPSie Support on request. See security.
Status pages
Link Statuspage, Instatus, Uptime Kuma or UptimeRobot, or use the built-in HTTP probe from the console.
Activity log
Create, rule, domain, backend and delete events are kept for every load balancer.
Kubernetes front door
Pick worker nodes as backends and route each domain to a NodePort, or let multi-master clusters sit behind their own API balancer on port 6443. See Kubernetes.
Build against one API
Platform services use the same interfaces as everything else. A token limited to one role and one IP range is honored in curl, the CLI, Go and Terraform alike.
API endpoints
One OpenAPI 3.0 reference at apidocs.vpsie.comTerraform data sources
Alongside 33 resourcesGo SDK service clients
Load balancer, registry, databases and Kubernetes includedWays to call it
REST, Go SDK, Terraform or OpenTofu, and the CLIHow the services combine
A typical three-tier layout, all inside one VPC.
Front door
A public load balancer is the only internet entry point. Application servers stay on private addresses.
Application tier
Servers or a Kubernetes cluster run the code. Firewall groups apply per tier.
Data tier
A managed database is reachable only inside the VPC. Backups protect it.
A reference Terraform stack of exactly this shape is available: a project, a private VPC, two application servers without public addresses, a public load balancer, a managed database and a firewall policy per tier. It was applied, planned again with no changes, and destroyed against the API.
Learn more: HAProxy one-click Container registry MongoDB one-click
Questions about platform services
Do I share a load balancer with other customers?
No. Every VPSie load balancer is a single-tenant instance, so its traffic, certificates and configuration are isolated.
Can the load balancer point at servers outside VPSie?
Yes. Backends can be any reachable IPv4 endpoint, including other clouds and on-premises systems.
Can I keep my application servers off the internet?
Yes. Put them on private addresses and expose only the public load balancer.
Do certificates renew by themselves?
For domains hosted on VPSie DNS, yes. The platform requests a Let's Encrypt certificate that covers the domain and its wildcard, installs it and renews it before it expires. Domains hosted elsewhere can use a certificate you upload.
Can I manage all of this as code?
Yes. Load balancers, databases, registries and Kubernetes clusters all have Terraform resources and API endpoints.
Does it all work in a private cloud?
The same services run in a private cloud on your site.
Put a load balancer in front of your app
Create an account and add one in a few clicks.