Apps

From Dockerfile to production in one command.

zwrm deploy builds your image, turns it into a Firecracker microVM, issues TLS, and scales it under load. Vibe-coded or hand-written, it ships the same way.

Deploy your first app Talk to an expert
  • Firecracker microVMs
  • TLS out of the box
  • Autoscaling
my-app
Deploying Healthy
12%84%31% Avg CPU
1 2 3 Machines running
Autoscale +2 machines · CPU above 75% for 60s
Machines Scale
  • Running 9a3f 2 vCPU · 4 GB
  • Running c71e 2 vCPU · 4 GB
  • Running e204 2 vCPU · 4 GB
Works with your stack

If it builds into a container, it runs on zwrm.

Any language, any framework

A Dockerfile is all zwrm needs. Bring Node, Python, Go, Rust, or whatever your app is written in; databases and metrics are one link away.

From repo to URL

Ship in three steps.

  1. 01

    Run zwrm deploy

    From your repository or CI. zwrm builds the image from your Dockerfile and converts it into a microVM.

  2. 02

    Get a URL

    Your app is live at my-app.zwrm.app with a TLS certificate, or on your own domain. The proxy and routing are handled.

  3. 03

    Let it scale

    Machines are added when CPU stays high and removed when traffic drops. Link a database and volumes as you need them.

What you get

Production plumbing, provisioned.

Everything between git push and a healthy app, without running the platform yourself.

  • Build from Dockerfile

    Every deploy builds a fresh image from your Dockerfile, so what runs is exactly what you committed.

  • Firecracker microVMs

    Each app runs in its own microVM with hardware isolation, not a shared container host.

  • Proxy and TLS

    HTTPS, certificates, and routing come with the deploy. Custom domains are a DNS record away.

  • Autoscaling

    Set CPU thresholds and a machine range. zwrm adds and removes machines as load changes.

  • Linked services

    Attach a managed Postgres database and persistent volumes; connection strings are injected as environment variables.

  • Metrics included

    Requests, latency, errors, and deploy markers for every app, with exports to Grafana and OpenTelemetry.

EU hosting and self-hosting

Hosted in the EU. Or on your infrastructure.

Deploy to our managed European infrastructure or run the zwrm platform in your own data center. The deploy command is the same.

Discuss your deployment
Managed by zwrm

zwrm Cloud

Apps run on managed infrastructure in European data centers operated by European providers, ready in minutes.

  • Hosted in European data centers
  • Managed operations and updates
  • Isolated microVMs for every app
Managed by you

Your infrastructure

Install zwrm in your own data center or private cloud. Your network, data location, and access controls stay under your control.

  • On-premises or private cloud
  • Direct access to internal systems
  • Your security and compliance policies
Questions, answered

Before you deploy.

What do I need to deploy?

A Dockerfile. zwrm builds the image, converts it into a Firecracker microVM, provisions a machine, and issues a TLS certificate in one command.

Can I use my own domain?

Yes. Point a DNS record at your app and zwrm issues and renews the certificate for it.

How does autoscaling work?

You set a CPU threshold and a minimum and maximum number of machines. When CPU stays above the threshold, zwrm adds machines; when load drops, it removes them.

What is a microVM?

A lightweight virtual machine with its own kernel, started by Firecracker in milliseconds. Your app gets hardware isolation from other tenants without the overhead of a full VM.

Can I deploy from CI?

Yes. Run zwrm deploy from GitHub Actions or any CI with an API token. Every deploy shows up as a marker in your metrics.

Where does my app run?

On European infrastructure operated by European providers, or on your own infrastructure if you self-host zwrm.

One command away

Ship your app to EU infrastructure today.

Deploy in minutes, or talk with us about your architecture and compliance requirements.

Deploy your first app Talk to an expert