Skip to content
YAML in. Servers out.

Define. Deploy. Done.

Infrastructure as code. Not infrastructure as tickets. Write a config, run a command, and get back to building your product.

Config-driven 99.99% SLA < 30s deploys
stackserver.yaml
1# stackserver.yaml
2version: "2"
3service:
4  name: my-app
5  region: eu-west-1
6  instances: 3
7  resources:
8    cpu: 4
9    memory: 8GB
10    storage: 100GB
11  scaling:
12    min: 1
13    max: 10
14    target_cpu: 70

Your Workflow. Not Ours.

Four steps. That's the entire deployment lifecycle.

01

Write

Define your stack in YAML or use our CLI to scaffold a config. Version it with your code.

02

Test

Preview infrastructure changes before they hit production. Dry-run deploys catch issues early.

03

Deploy

One command to ship to any region. Zero-downtime rollouts with automatic rollback on failure.

04

Monitor

Real-time logs, metrics, and alerts. Trace requests across services with built-in observability.

The Developer Stack

Run your language of choice. We keep runtimes up to date so you don't have to.

terminal
 $ stackserver runtimes
  
 RUNTIMEVERSIONS
 node18, 20, 22
 python3.10, 3.11, 3.12
 go1.21, 1.22
 rust1.75, 1.78
 php8.2, 8.3, 8.4
 ruby3.2, 3.3
  
 $

Why Not Just Use [Big Cloud]?

You could. But you'd spend more time on infrastructure than on your product.

No 200-Service Menu

Compute, storage, networking, DNS. That's it. You don't need a service catalog the size of a phone book. We ship what developers actually use.

No Surprise Bills

Flat, predictable pricing. You pick your resources, you know the cost. No hidden egress fees, no bandwidth surcharges, no "we'll figure out the bill later."

No PhD Required

Deploy in minutes, not months. You shouldn't need a certification to run a web server. If you can write YAML, you can run infrastructure.

Questions You'd Actually Ask

Straight answers. No marketing fluff.

We give you the 5% of cloud services that cover 95% of use cases — compute, storage, networking, and DNS — without the 200-service menu. Everything is config-driven. No console-clicking, no IAM policy nightmares, no 47-page billing statements.
Yes. Stackserver works with GitHub Actions, GitLab CI, Bitbucket Pipelines, or any CI system that can run a CLI command. Add `stackserver deploy` to your pipeline and you're done. We also support webhooks for git-push-to-deploy workflows.
First-class Docker support. Bring your own Dockerfile or use our optimized base images. We handle the registry, builds, orchestration, and networking. Multi-stage builds and private registries are supported out of the box.
Minimal and predictable. `stackserver init` to scaffold, `stackserver deploy` to ship, `stackserver logs` to debug. Every command supports `--json` for scripting. The CLI is open-source and available via npm, brew, and curl.
Yes — staging, production, feature branches, whatever you need. Each environment gets its own isolated resources. Promote between environments with `stackserver promote staging production`.
Yes. The free tier includes 1 shared-CPU instance, 512MB RAM, and 10GB storage. No credit card required. It's enough to run a side project, test the platform, or prototype your next idea.

Write YAML. Ship servers.

Your first deploy is free. No credit card, no sales call, no 30-page form.

$ stackserver init && stackserver deploy