Enterprise Self-Hosted Infrastructure

Cosmos Cloud Pro

10x cheaper than AWS. 10x easier than Kubernetes.

Scale your SaaS and internal services across clusters of servers — with the simplicity and security-first approach that makes Cosmos Cloud unique. Your infrastructure, your rules, your savings.

10x Cheaper

Fraction of the cost of hyperscalers. $1/GB RAM/month licensing — predictable, transparent, no billing surprises. Ever.

Save up to 82% vs AWS

10x Simpler

Do months of work in a few days. A clean UI to manage your entire cluster — deploy, scale, and monitor from one dashboard.

Deploy in minutes, not weeks

100% Yours

Self-host across any provider. No vendor lock-in, no data leaving your control. Switch providers at will without changing a single line of config.

Zero vendor lock-in

Predictable Pricing. No Surprises.

Starting at $16/month for 16 GB of RAM and 20 users. Beyond that, licence cost $1 per GB of RAM per month and $5.99 per user per month. That's it. No egress fees, no NAT gateway costs, no monitoring surcharges, no data-transfer markups. Bolt-on any hardware you want, and Cosmos takes care of the rest.

$16/mo
Base Commitment*
Includes 16 GB RAM + 20 users
$1/GB RAM/mo
Additional RAM
Scale to any cluster size
$5.99/user/mo
Additional Users
Grow your team as needed

* Waivable with custom pricing — contact sales.

Monthly cost comparison — 6 servers x 64 GB RAM (384 GB total)
Cosmos Pro + Hetzner$708/mo
82% less
License: $384Hardware: $324Egress: $0NAT: $0
AWS Equivalent$4,026/mo
EC2 (m6i.4xlarge): $3,364NAT Gateway: $232EBS Storage: $240ALB: $50CloudWatch: $50Data Transfer: $90
$3,318
saved per month
$39,816
saved per year
82%
cost reduction

AWS pricing based on us-east-1 on-demand m6i.4xlarge instances, March 2025. Hardware pricing based on Hetzner AX52 dedicated servers. Actual prices may vary by region and configuration.

Hours. Not Months.

Reverse proxy, HTTPS, SSO, VPN, WAF, monitoring, backups, load balancing — Cosmos ships all of it pre-wired. Building the same stack yourself means gluing together a dozen tools, each with its own config, upgrades, and failure modes.

Time to a production-ready 3-server cluster — one experienced DevOps engineer
Cosmos Pro~1 hour
same day
Install CosmosAdd servers to the clusterDeploy your appsHTTPS, SSO, VPN, WAF, monitoring, backups, load balancing, CI/CD and registry: included
DIY Docker Stack~2 weeks
Docker + CoolifyTraefik + Let's EncryptKeycloak + PostgresOIDC wiring for every appWireGuard mesh between serversPrometheus + Grafana + alertingCrowdSec / WAF / rate limitingBackups + restore drillDocker Swarm, load balancing, failoverPrivate registry + CI runners
Kubernetes~10 weeks
still going…
k3s / kubeadm HA control planeCilium CNI + NetworkPoliciesingress-nginx + cert-manager + external-dnsKeycloak + CloudNativePG operatorkube-prometheus-stack + Loki + alertingLonghorn storage + Velero backupsHelm charts + ArgoCD for every appHarbor registry + CI runnersRBAC, sealed-secrets, pod securityModSecurity WAF + rate limitingLearning curve, upgrades, debugging
1 hour
to production
2 weeks
saved vs DIY Docker
10 weeks
saved vs Kubernetes

Rough estimates for an engineer already familiar with each tool, targeting HTTPS, SSO, reverse proxy, monitoring, VPN, WAF, backups and failover across 3 servers. Ongoing maintenance not included.

Do You Really Need a Hyperscaler?

Probably not. Here's why.

99.99% vs 99.999% uptime

The difference is about 1 hour per year. Your application code or database will hit its own limits long before the underlying infrastructure does.

Your bottleneck is never the cloud provider

It's your code, your database queries, your architecture. Paying 5x more for infrastructure doesn't fix application-level problems.

Even companies on AWS have outages

Uptime comes from good architecture, not expensive providers. A well-configured cluster on dedicated hardware achieves the same real-world reliability.

The 1% who need hyperscale know who they are

If you're not processing millions of transactions per second, you're paying for capacity you'll never touch.

The Per-Hour Pricing Trap

Let's do the math.

“$0.768/hr” sounds cheap

Run it 24/7 and that's $560/month per server. Per-hour pricing exploits the gap between how the price feels and what it actually costs.

Production runs 24/7 — spot jobs don't

The only workloads where per-hour pricing makes sense are batch jobs on idle machines — and those are cheap anyway. Your production servers never sleep, so per-hour is just monthly pricing dressed up to look smaller.

Right-size your infrastructure, absorb spikes without the cost spike

A properly sized flat-rate cluster handles traffic bursts gracefully, without a surprise bill for auto-scaled capacity you didn't ask for.

Flat-rate = know your cost before you deploy

$1/GB RAM/month. No calculator needed, no bill shock at end of month.

Everything You Need to Scale

Cosmos Pro is the exact same software as Cosmos Cloud, with the building blocks of a real platform on top: multi-server deployments and functions, managed databases, S3 storage, and CI/CD with your own private registries.

Cluster & Deployments

Run apps and functions on many servers

Describe the app once, say how many copies you want, and Cosmos does the rest.

Your Cosmos servers connected through Constellation already form a cluster. A Deployment is the same compose file you use for a ServApp, run as replicas across your nodes and served behind a single URL. For the small stuff, Cloud Functions skip the container entirely: publish a JavaScript or Python package and it answers on a URL.

  • Fixed count, Autoscale (min / max), or Fill: one replica on every node that matches your tags
  • Placement by tags (gpu, nvme, zone-eu) and by load: round-robin or least-busy
  • Rolling updates one node at a time. A failed replica pauses the rollout, the rest keep serving
  • A node goes down: replicas are rescheduled within seconds. A leader goes down: another manager takes over
  • Scale to zero: idle tools stop after an hour and restart on the next request
  • Cloud Functions for webhooks, small APIs and cron jobs: asleep when idle, spread across nodes under load, versioned with one-click rollback
Read the Cluster & Deployments docs
wiki
wiki.mydomain.com
Running · 3 / 3
Autoscale 1 – 4Least-busytag: web
hetzner-1
62%
hetzner-2
48%
ovh-1
71%
home
no tag
Rolling update: replica 2 of 3 restarted, waiting for healthy…
Managed Databases

PostgreSQL in one click

Private to your network, one database per app, backed up every night.

Create a PostgreSQL server from the dashboard, then hand each application its own database with its own user and password. Nothing is reachable from outside your Constellation unless you say so.

  • Per-application databases with isolated credentials and one-click password rotation
  • Reference credentials from any compose with template variables, so secrets never live in your config
  • Scheduled restic backups to disk or any remote storage, with retention policies
  • Restore any snapshot as a new database next to the live one. The original is never touched
  • Size, connections and resource graphs, plus a full event history
Read the Managed Databases docs
maindb
PostgreSQL 16 · home node: hetzner-1
Live
Constellation onlyBackups nightly 4:0012 snapshots
Application databases
wikiown user · own password
nextcloudown user · own password
apiown user · own password
DATABASE_URL=${db.maindb.wiki.url}
Object Storage (S3)

Your own S3, spread across your servers

Anything that speaks S3 can use it. Every file is copied to another node.

Tag the nodes that should hold data and Cosmos deploys an S3-compatible storage across them, powered by SeaweedFS. Backup tools, media apps, Nextcloud, your own code: point them at the endpoint and go.

  • Choose your replication level: survive losing one node, or two
  • Grow by tagging another node. Shrink by draining one before you remove it
  • Automatic maintenance: vacuum, replica scrubbing, health checks, optional erasure coding for cold data
  • Highly available S3 gateways behind your load balancer, with valid HTTPS on your own domain
  • Private to Constellation by default. Make it public in one click when a remote service needs it
Read the Object Storage (S3) docs
media
https://cosmos.mydomain.com:8600
Ready
replication 0013 nodes2.4 TB free
hetzner-1
72%
hetzner-2
68%
ovh-1
41%
Scrub replicas · monthly
Vacuum · nightly
Health check · 5 min
Index backup · nightly
CI/CD & Registries

Push to git, live on your cluster

The Vercel workflow, on servers you own. Builds, images and packages never leave your network.

Connect a repository from GitHub, GitLab, Gitea or Bitbucket. Every push is built on one of your nodes, stored in your own private registry and rolled out as a deployment, a static site or a function. No Dockerfile? Cosmos detects the language and builds it anyway.

  • Builds from a Dockerfile, an auto-detected language, your existing Woodpecker pipeline, or a cosmos.json next to your code
  • A preview deployment with its own URL for every pull request, removed when it is merged
  • Branch environments: develop goes to staging automatically, main waits for your click
  • Private registries for Docker images, npm and Python packages, files and static sites, with scoped deploy tokens
  • One-click rollback to any previous build, commit statuses on your git provider, alerts when a build fails
Read the CI/CD & Registries docs
shop-api #128
main · 1a2b3c4 · fix checkout rounding
Running
Dockerfile detectedmain → productionPR previews
Checkout2s
npm test41s
Build & push1m 12s
Deployrolling 2 / 3
docker.mydomain.com/shop-api/api:sha-1a2b3c4d5e6f
Previous build one click away: Deploy this build rolls back without rebuilding.

And everything around it

Plus all of Cosmos Cloud: reverse proxy, HTTPS, SSO, app market, backups and the Constellation VPN.

Built-in Load Balancer

One URL for all replicas, wherever they run. Round-robin or nearest-healthy, sticky sessions, and unhealthy replicas pulled from rotation within seconds.

SmartShield

Adaptive rate limiting, anti-DDoS, bot protection and geo-blocking on every route, sized for thousands of users. A ban on one server applies to the whole cluster.

Constellation Mesh

Encrypted network between all your servers, across providers and regions. Databases and storage stay private to it by default.

Monitoring & Events

CPU, memory, network and traffic graphs for every deployment, database and storage, plus a history of everything the cluster did.

Scheduled Jobs

Backups, maintenance and your own tasks run from one scheduler, on the node that owns the data, with retention policies.

Groups & Permissions

Go beyond User and Admin: custom groups with granular permissions, shared across the cluster, sudo-style elevation and scoped API tokens.

Your Global Infrastructure

Deploy clusters across regions and providers. Every connection encrypted, every request load-balanced, every server under your control.

1
Add Servers
From any provider or bare metal
2
Form a Cluster
Auto-connected via encrypted VPN
3
Deploy Services
One-click with auto load balancing
4
Scale at Will
Add servers, Cosmos rebalances
requestsrequestsrequestsrequestsrequestsrequestsUS West3 nodesEU Central3 nodesAsia Pacific3 nodes

All inter-cluster traffic is encrypted end-to-end via Constellation VPN. Requests are automatically routed to the nearest healthy node.

How Cosmos Pro Compares

More features, less complexity, a fraction of the cost

FeatureCosmos ProAWS / GCP / AzureDigitalOceanRailway
Infrastructure
Auto-Scaling Replicas
Reverse Proxy + HTTPS
Anti-DDoS / WAF
Built-in VPN
Security by Default *
Ownership
All Included in Base Price
Predictable Pricing
Self-Hostable
No Vendor Lock-in
Multi-Provider Support

* Security by Default: every service you deploy automatically gets HTTPS, authentication, rate limiting, DDoS protection, monitoring, and encryption — with zero configuration required.

Ready to cut your cloud bill by 82%?

Get in touch with our team to discuss how Cosmos Cloud Pro can transform your infrastructure.