The Platform
A managed PaaS that treats every site like production.
One control plane. Per-site isolation. Real edge TLS. Durable provisioning workflows. The boring parts done well, so your sites stay fast under load.
The stack
What runs your sites, end to end.
No black boxes. We publish exactly what we run, so you can audit it, benchmark it, and ask hard questions.
Caddy at the edge
Automatic HTTPS via Let's Encrypt with on-demand TLS. HTTP/3 + h2 + h1. Zero manual cert wrangling.
NGINX + PHP-FPM 8.3
Per-site PHP-FPM pool, dedicated Linux user, dedicated cgroup. Sites cannot starve each other.
MySQL 8 + Postgres 16
Choose your DB. Dedicated instances on private network. Daily encrypted off-site backups, 30-day retention.
Redis object cache
Per-site Redis with sane eviction defaults. WP, Magento, and Laravel pre-wired.
Varnish where it counts
For Magento and high-traffic publishers. ESI + checkout-aware bypass rules tuned by humans.
Temporal-driven workflows
Provisioning, migrations, scaling — durable workflows you can replay, audit, and trust on failure.
WAF + brute-force defense
Edge ruleset blocks the obvious. Per-site origin rules block the targeted. Anomaly alerts to your inbox.
SSH-CA host certificates
No long-lived static keys. Short-lived, audited, revocable. Your team gets SSH; we get sleep.
Atomic deploys
Symlink swaps with rollback. Cron + queue workers drained gracefully on deploy. Zero-downtime by default.
Multi-tenancy
One server, many sites — no shared fate.
The expensive lesson we learned from Cloudways and Pressable: Docker-per-site is wasteful, shared PHP-FPM is dangerous. Linux already solved this.
CubitRace
One Linux user + one cgroup + one PHP-FPM pool, per site.
- • Hard CPU and memory limits enforced by systemd slices (cgroups v2).
- • A runaway plugin can spin its own pool — it cannot OOM the box.
- • Dedicated user means a compromised site cannot read another site's files.
- • No Docker layer overhead, no per-site image cache to invalidate.
Typical shared host
Shared PHP-FPM pool, shared user, "fair share" CPU.
- • Noisy neighbor on one site degrades every other site on the box.
- • "CPU shares" sound dedicated but float under contention.
- • Shared file ownership is a frequent source of cross-site escalation.
- • Burst limits are documented in the FAQ, not the dashboard.
See the platform
Spin up a real site in 90 seconds.
Free trial includes the full platform. Migration assistance is on us if you want to switch.