One-click scenarios
Group the services of a flow into a scenario and start or stop the whole thing with one button. Start order, health and dependencies sorted for you.
What a scenario isLocal microservice orchestrator
Run your microservice scenario locally in one click
Every dependency points wherever you say: at the service you have open, at the cloud —your shared dev environment— or at a mock. MicroLab rewrites the URLs as it starts everything, so you never touch a line of your repositories.
Dependencies Change a target and watch the URL
bff-catalog→orders-core http://localhost:8081
bff-catalog→payments-core https://api.dev.acme.io/payments
orders-core→catalog-api http://localhost:8500/catalog
On start · MicroLab injects these URLs into each service
From a 40-step LOCAL_SETUP.md to one click
Building a local microservice environment is slow, brittle and hard to repeat. MicroLab turns it into something visual, reproducible and non-invasive. Why it exists and who builds it.
Before By hand
- Start Docker and bring up Kafka, Redis and PostgreSQL
- Create the database and run the migrations
- Launch each service with its flags and profile
- Rewrite the URLs between services by hand
- Decide what to do with every dependency
- Repeat every time… and get it working for your team too
With MicroLab One scenario
- Pick the scenario and press Start
- The app manages the shared infrastructure in Docker
- Each dependency: local, cloud or mock
- URLs rewrite themselves, with no changes to any repo
- Status, health and live logs, like an IDE
- Exportable scenarios: reproducible for the whole team
Everything you need to test end-to-end flows
A tool built for teams working with a lot of microservices.
Local / cloud / mock, per dependency
For every connection you choose whether it points at the real service running locally, at the cloud (your shared dev environment) or at a mock. MicroLab rewrites the URLs automatically, with no edits to your repositories.
How each dependency is resolvedNative or containerised
Mixed mode: the service you are working on runs natively, fast and with hot reload; the ones you only need in the background run isolated in Docker. You decide per service.
Native or containerisedManifest autodetection
“Add service” detects the stack, the ports, the infrastructure and the dependencies from the repo. Zero manual configuration to get going.
The manifest and the stackMock Studio
Capture calls and turn them into stubs in one click, generate response skeletons from OpenAPI and organise variants per service. With hot reload, Postman-style.
Mocks in the appShared infrastructure, managed
Kafka, Redis and PostgreSQL run in Docker, managed by the app, remapping ports automatically when
they collide. No hand-written docker compose.
IDE-grade observability
Live logs colour-coded per service, with search and follow-tail; health on every card, and a navigable graph of the scenario to see who talks to whom.
Live logsA CLI with full parity
Everything the UI does, the microlab CLI does too. Automate scenarios in CI or from
your terminal, running the same engine logic.
microlab CLI Exportable scenarios
Import and export self-contained scenarios to share with your team. The same environment, reproducible on any machine.
Sharing a scenarioHow it works
From nothing to a running scenario in four steps. If you are still deciding how to build it, the guide explains what a local microservice environment needs and what each approach solves.
- 1
Add your services
Point at the repo folder. MicroLab detects the stack, the ports, the infrastructure and the dependencies automatically.
Adding a service, step by step - 2
Assemble the scenario
Choose which services come up together and, for each dependency, whether it goes local, to the cloud or is simulated with a mock.
Your first scenario - 3
Press Start
The app starts infrastructure and backends in the right order, rewrites the URLs between them and waits until they are healthy.
Your first run - 4
Test and watch
Run your whole flow. Follow the live logs, check health and edit mocks on the fly without restarting anything.
Activity and checks
Inside the window
A scenario actually running: which service is healthy, where each dependency points and what is happening right now.
Technology-agnostic
The engine carries no logic for any particular stack: that knowledge lives in declarative profiles. Adding a technology means adding a profile, not rewriting the orchestrator.
- Quarkus ready
- Spring Boot ready
- Node / Angular ready
- .NET prepared
- Python prepared
- Go prepared
Plans
Free for personal use — the window and the CLI, whole, with a daily allowance of AI calls to try it out. Using it at work, or without the AI limit, needs a paid plan.
All of MicroLab, by hand.
The window and the terminal, uncut. The microlab CLI carries the same engine logic and
full parity with the app, in CI too.
- Unlimited scenarios, mocks, Docker and libraries
- Full CLI, ready to drop into CI pipelines
- A daily AI allowance to try it out
Let the AI build it.
A copilot assembles and runs scenarios for you: describe the flow in plain language and let MicroLab orchestrate it, with a built-in chat and an MCP server for your own agents.
- A copilot that creates and drives scenarios for you
- MCP server to plug in your own agents
- No daily limit, and use at work
The same environment, for everyone.
A catalogue of scenarios the team shares: whoever joins clones it, starts it
and is already working, without reading anybody's LOCAL_SETUP.md.
- Everything in Pro, per seat
- Shared scenario catalogue
- Centralised licences, billing and SSO
Download MicroLab
Beta First public beta. Not signed yet: your OS may warn about an unverified app.
Windows
.exe installer · Windows 10/11 (x64)
macOS
The macOS installer will follow.
Coming soonLinux
AppImage · .deb
.deb package Frequently asked questions
Do I have to reconfigure my microservices to use MicroLab?
No. MicroLab is non-invasive: it injects configuration as each service starts
(-D flags or environment variables) and rewrites the URLs between services,
without touching the code or the files in your repositories.
Which technologies does it support?
The engine is stack-agnostic: it uses a declarative registry of profiles. Today it runs JVM (Quarkus, Spring Boot) and Node/Angular; .NET, Python and Go are ready. Adding a technology means adding a profile, not touching the orchestrator.
Can I mix services running locally with others pointing at the shared environment?
Yes. For each dependency you decide whether to resolve it locally, against the shared development environment (VPN where needed) or with a mock. That is the point of MicroLab: testing the part you care about without bringing up everything else.
Which infrastructure does it bring up for me?
Kafka, Redis and PostgreSQL in Docker, managed by the app itself, remapping ports automatically when they collide. You need Docker Desktop (or a Docker engine) installed.
Can I download it yet, and is it free?
You can download it now: there are beta installers for Windows and Linux, and the macOS one will follow. It is free for personal use —learning, evaluating, your own projects—; using it at work requires a paid plan.
Can I share a scenario with my team?
Yes. Scenarios export as self-contained, importable files, so the whole team brings up exactly the same environment, reproducibly.
Stop building the environment by hand
Download the beta and have your microservice scenario running in minutes.
See downloads