Deploy apps

Production infrastructure, in your AWS account.

microbuilder builds the whole stack, from the network to the running app, the way an experienced platform engineer would. Every resource is tagged, recorded and removable.

Three layers

Foundation, cluster, apps.

Each layer is built once and reused: many clusters in a landing zone, many apps on a cluster.

1. Landing zone

The foundation: a VPC with public and private subnets across two availability zones, internet and NAT gateways, routing and an S3 endpoint. Peer them, or join them to a Transit Gateway.

2. Cluster

ECS on Fargate, EKS, or K3s on your own machines, inside the landing zone, with a load balancer, logs with sensible retention, and rollback on a failed deploy.

3. Apps

Your services on the cluster: containers, environment and secrets, volumes, health checks, autoscaling, and the address people reach them on.

A landing zone, built and recorded step by step.

An ECS cluster inside it, with EKS alongside.

Three ways in

Start from words, an image or your code.

Describe it

“A Node API with Redis and a Postgres database.” The AI engineers design the services and how they connect.

A container image

Any public or private image. microbuilder sets ports, health checks and sizing to match the platform.

A GitHub repository

Connect GitHub and deploy a repository. The image is built from source in your own account, and build errors are explained.

Running it

Everything a running app needs.

Public or private

Behind an Application Load Balancer, or private behind a Cloudflare tunnel with no open ports.

Custom domains

Point your own domain at an app, with HTTPS.

Secrets kept secret

Secret values go to AWS Secrets Manager or Kubernetes secrets, never into plain environment variables.

Storage attached

Give an app access to an S3 or R2 bucket, with a role scoped to exactly that bucket.

Scale and logs

Change replicas and autoscaling, read logs and see service health from the app’s page.

Clean teardown

Delete an app, cluster or landing zone and everything it created goes with it, in the right order.

Blueprints

Complete stacks in one step.

A blueprint is a tested stack: pick it, fill in a short form, and microbuilder builds every resource it needs, in any region, with its running cost estimated before you start. It knows how to take it all down again.

The microbuilder Blueprints catalogue, Workloads tab: your app with Postgres and file storage, popular apps (n8n, Metabase, Umami), WordPress with a private database, and Nginx on ECS and EKS, each with what it builds and its estimated monthly running cost.

Foundations

  • Landing Zone
  • Paired Landing Zones (prod and non-prod)
  • Peered Landing Zones
  • Transit Gateway hub and spokes

Workloads

  • Nginx on ECS Fargate with a load balancer
  • Nginx on EKS with a load balancer
  • WordPress with a private database
  • Your app with Postgres and file storage
  • Popular apps: n8n, Metabase, Umami

Zero Trust and hybrid

  • Site-to-site VPN to on-premises
  • Zero Trust landing zone (Zscaler ZPA)
  • Zscaler HA VPN to AWS
  • Zscaler VPN with private DNS to EC2
  • Zscaler VPN with self-hosted DNS to EC2

Build your first landing zone today.

Connect a cloud account, describe what you need, and watch it build. The free plan is free for good.

Free plan. No credit card.