[mb]

Runs in your AWS and Cloudflare accounts

Your AI DevOps team. In your own cloud.

Describe what you need. microbuilder’s AI engineers design it, build it in your own AWS and Cloudflare accounts and keep it running: networks, clusters, apps and monitoring. When you are done, it cleans up after itself.

Connect your AWS account through an IAM role. No long-lived keys.

Who it is for

Real infrastructure, without a platform team.

microbuilder does the work a DevOps engineer would do, in the accounts you already own.

Startups and small teams

Real infrastructure on AWS before you have a DevOps engineer: foundations, deploys and monitoring without hiring one first.

Agencies and consultants

Build environments in each client’s own accounts, one workspace per client, and hand them over cleanly. It was always theirs.

IT and platform teams

Landing zones, VPNs and Zero Trust built the same way every time, network monitoring with a live map, and SSO for the team.

What you can build

From the network up to the app on top of it.

Built the same careful way every time, in your account, and removable without a trace.

AI engineers

A team of specialist AI engineers plans what you ask for, builds the deployment and checks it before anything is created.

Landing zones and networks

VPCs across two zones, peering, Transit Gateway hubs, site-to-site VPNs and Zero Trust, routed and recorded.

Clusters and apps

ECS, EKS or K3s, and apps from a description, an image or a GitHub repository. Public behind a load balancer or private behind a tunnel.

Blueprints

Fourteen tested stacks, from a landing zone to WordPress, n8n or Metabase with a private database. Running cost shown up front.

Monitoring

Collectors on your network, SNMP devices, a live network map, dashboards and alerts. Your metrics stay with you.

Storage and data

S3 and R2 buckets attached to apps with least-privilege access, and databases kept in private subnets.

Also included

AI-designed websites with forms and analytics Running-cost estimates for everything built AI traces in your own Langfuse Single sign-on with your identity provider

Why your own cloud

You are handing over cloud credentials. We know.

So microbuilder is built around one rule: everything it makes is yours, in your accounts, and it can always be removed.

It stays yours

Networks, clusters, databases and DNS live in your own accounts, on your own bill, with no markup. Stop paying us and they keep running.

It cleans up after itself

Every build records what it created, so removing it sweeps all of it. A scanner finds anything tagged by microbuilder that was left behind.

It answers to your security team

A scoped IAM policy, IAM roles with an external ID, encrypted keys, SSO with your identity provider, and one workspace per company.

How it works

From cloud keys to a running app in three steps.

Nothing to install on your servers. No Terraform state to look after.

  1. Step 1

    Connect your accounts

    AWS through an IAM role or keys, scoped by the policy we give you, plus Cloudflare and your AI provider key.

  2. Step 2

    Describe it or pick a blueprint

    Say what you need in plain words, or start from a tested blueprint with its running cost shown up front.

  3. Step 3

    Watch it build in your account

    Live progress as every resource is created. Change it later, or tear it down and nothing is left billing you.

The alternative

The speed of a platform. The ownership of doing it yourself.

A hosting platform
Your apps run on their servers, at their markup. Leaving means migrating.
Doing it yourself
Terraform, IAM, networking and state files: weeks of specialist work before the first app runs.
A consultant
Expensive, slow to change, and the knowledge leaves when they do.
microbuilder
Running in your own account this afternoon, built to a tested standard, changed by asking, and removable without a trace.

Questions

What people ask before they sign up.

What exactly is microbuilder?

A control plane for your own cloud. You connect your AWS and Cloudflare accounts and an AI provider key; microbuilder’s AI engineers design what you ask for and build it in those accounts: networks, clusters, apps, websites and monitoring. It keeps a record of everything it creates, so it can change it or remove it cleanly.

Do you host my apps?

No. Everything runs in your own AWS and Cloudflare accounts, on your own bill. microbuilder never resells compute, so there is no markup on your cloud costs, and if you stop using microbuilder everything keeps running.

Do I need to know AWS or Kubernetes?

No. You can describe what you want in plain words or pick a blueprint. If you do know AWS, everything is visible in your own console, tagged, and nothing is hidden from you.

Which AI does it use?

Yours. You bring your own key (Anthropic, OpenRouter, Cloudflare AI Gateway or your own vLLM endpoint). AI usage is billed by your provider, not marked up by us, and you can see every request in your own Langfuse.

Is it safe to give microbuilder access to my AWS account?

You decide how much access it gets. We give you a scoped IAM policy, you can connect through an IAM role with an external ID instead of long-lived keys, and keys are encrypted at rest (AES-256-GCM) and never shown again once saved. See the Security page for the details.

What does it cost?

There is a free plan for good, with no credit card. Paid plans are priced per seat and add clusters, more cloud accounts, monitoring and single sign-on. Your cloud and AI usage are billed by AWS, Cloudflare and your AI provider directly.

Another question? Ask us

Your first environment, this afternoon.

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

Start freeSee pricing

Free plan. No credit card.