Scale your SaaS on flat-priced bare metal

A layout that carries many SaaS products from the first customers to serious scale, in one location:

• 2 × Core 16 as stateless app and API nodes, each running your containers behind NGINX or HAProxy.
• 2 × Pro 32 for PostgreSQL or MySQL: a primary and a hot standby replicating over the private VLAN.
• Redis or Valkey for sessions, queues and caching, on the database servers or the app nodes.
• Backups shipped every night to a server in a second location.

As an example, that is 2 × $299 plus 2 × $749, or $2,096/mo, with unmetered traffic and nothing billed for internal or outbound transfer. App nodes are the easiest tier to scale out, so watch the database first as you grow.

Put a CDN or an external load balancer in front, or publish both app nodes in DNS with health-checked failover, so you can take one node down for maintenance. Keep only the web ports public and everything else on the private network.

Start by mapping what you run today. On most clouds a vCPU is one hardware thread, so a Pro 32 with 64 threads covers about 64 vCPUs of compute, without a hypervisor in the way. Memory is often the bigger change: 384 GB in a single Pro 32 lets you consolidate services that were split across instances only to fit memory limits.

A low-risk migration path:

• Provision the new servers and deploy with the same Terraform, Ansible or container images you use today.
• Replicate the database from the current primary to the new servers, and test the application against the replica.
• Lower DNS TTLs a day ahead, switch traffic, and keep the old environment as a fallback until you're confident.

Move the steady baseline first; that is where a fixed monthly price helps most, and spiky or experimental workloads can follow later. Our engineers provide free migration help to plan the move with you.

Bare metal doesn't mean manual work. Every action in the control panel is available in the REST API, and the Terraform provider keeps servers in version control alongside the rest of your infrastructure. Rebuild a misbehaving node from a clean image instead of repairing it by hand.

Standard tooling covers the rest:

• Configuration: Ansible or immutable container images, so any node can be replaced.
• Orchestration: Docker Compose for a handful of services, k3s or Kubernetes once you run many.
• Observability: Prometheus and Grafana on the private network, plus the bandwidth and hardware health graphs in the FlexDedi panel.
• Security: follow our checklist for a new Linux server: SSH keys only, a default-deny firewall and automatic security updates.

Servers are unmanaged by default, so your team owns the OS and the application stack, while our 24/7 engineers handle hardware, network and platform issues.