Plans and pricing

For personal use, MicroLab is free: the window and the CLI, whole and uncut, with a daily AI allowance to try it out. To use it at work —or to lift the AI limit— you need a paid plan.

Free Beta

€0Personal use · all you need is an account

All of MicroLab, by hand.

The window and the terminal, uncut: scenarios, microservices, mocks, libraries, Docker and logs.

  • Unlimited scenarios and microservices
  • Full microlab CLI, in CI too
  • Docker infrastructure, mocks and local libraries
  • Logs, checks and the dependency graph
  • Export and adopt scenarios

To try the AI

  • 50 calls a day to the MCP server
  • 25 calls a day to the copilot

What it does not include

  • Use inside an organisation: using it at work requires a paid plan (terms)
Download MicroLab
Pro AI

€89/yearor €9/month · per person · use at work included

Let the AI build it.

Describe the flow in plain language and let MicroLab assemble and run it. With an MCP server to plug in your own agents.

  • Everything in the Free plan
  • Built-in copilot, no daily limit
  • MCP server, no daily limit
  • Connect Claude Code, Claude Desktop or Cursor
  • Macros: the copilot builds its own tools
  • Use at work
Get Pro
Team

€149/yearper seat · from 3 seats

The same environment for everyone.

A catalogue of scenarios the team shares: whoever joins clones it, starts it and is already working.

  • Everything in the Pro plan
  • Shared scenario catalogue
  • Centralised licences and billing
  • SSO with your identity provider
Get Team

What it adds to what you already use

MicroLab does not replace docker compose, Testcontainers or WireMock: it leans on the same pieces. What it adds is what none of them covers on its own. In more detail, and with what MicroLab does NOT do, in the comparison with Docker Compose and local Kubernetes.

  • Communication between services, resolved per dependency. A compose brings up processes; deciding that this service talks to the one on your laptop, that other one to the shared environment and a third to a mock still means editing configuration by hand in every repo. MicroLab rewrites those URLs on start, with -D flags or environment variables, without touching your files.
  • An environment that lives while you work. Testcontainers ties the lifecycle to the test and tears it down at the end; here the scenario stays up, with its logs and its health, while you debug.
  • Native and containerised at once. The service you are touching runs natively, with hot reload; the background ones run in Docker. You choose per service.
  • The same from the window and from the terminal. The microlab CLI carries the same engine logic, so what you assemble by hand automates in CI without rewriting it.

All of that is in the free plan. What you pay for is having the AI assemble and drive it for you.

What counts as a call

A tool call: every time an agent —or the copilot— performs an action on MicroLab (start a scenario, read some logs, create a mock). What you type and what the model answers do not count, only the actions it performs.

Using the app by hand consumes nothing, whatever you do with it. The two allowances are independent: spending the copilot's does not touch the MCP server's.

The counter resets at midnight UTC. When little is left, the app shows it next to the model picker; from the terminal, microlab mcp-usage says so at the bottom.

Why you need to sign in

The free allowance goes per account, not per installation: it is the only way for it to be the same for everyone and for reinstalling not to reset it. The account is free and is not needed to use the app: only for the metered surfaces.

The copilot uses your own key

MicroLab does not resell AI tokens. The copilot talks to the provider you choose (OpenAI, Anthropic, Google, or anyone speaking OpenAI's protocol) with your key, and they bill the usage. What you pay for here is the integration with the engine, not the model.

Everything runs on your machine

The microservices, the containers and the mocks all run on your computer and do not leave it. MicroLab runs no code of yours on any server of ours, and data processing is limited to anonymous diagnostics you can turn off.

And if I run out of calls?

Nothing in MicroLab stops. What rests until the next day is the copilot and the MCP server; the window and the CLI keep doing exactly what they did before, because they are free. If the allowance falls short for you daily, write to [email protected] and we will let you know as soon as the plans open.