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 isRun your microservice scenario locally in one click
Every dependency points wherever you say: at the service you have open, at your cloud environment, or at a mock. Aseptic rewrites the URLs as it starts everything, so you never touch a line of your repositories.
- local the service you have open
- cloud your shared environment
- mock a simulated response
Dependencies Change a target and watch the URL
bff-catalog→orders-core http://localhost:8081
bff-catalog→payments-core https://api.cloud.acme.io/payments
orders-core→catalog-api http://localhost:8500/catalog
On start · Aseptic injects these URLs into each service
The scenario, running
The same checkout from the hero, now up: the three services coming online in order, and every call going out where it should.
- bff-catalog stopped starting healthy :8080
- orders-core stopped starting healthy :8081
- payments-core stopped starting healthy :8082
infra kafka, redis and postgres up
bff-catalog listening on http://localhost:8080
orders-core listening on http://localhost:8081
payments-core listening on http://localhost:8082
mock GET /catalog/scopes → 200
This is what it replaces
Building a local microservice environment is slow, brittle and hard to repeat. And the document explaining it ages worse than the code. Why it exists and who builds it.
- Start Docker Desktop and wait for the daemon
- Bring up Kafka, Redis and PostgreSQL from the compose file
- Create the database and run the migrations
- Export all 14 environment variables
- Start
orders-corewith its profile and its-Dflags - Rewrite the core URLs in your
application.yml - Remember to undo that before you commit
…and 33 more steps
$ aseptic up checkout
or you press Start in the window
Three decisions
Everything else follows from these three: what starts together, where each call goes, and how each service runs.
Local / cloud / mock, per dependency
For every connection you choose whether it points at the real service running locally, at your cloud environment or at a mock. Aseptic 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 containerisedAlso included
-
Manifest 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 stack -
Mock Studio
Capture calls and turn them into stubs in one click, generate response skeletons from OpenAPI and organise variants per service, with hot reload.
Mocks in the app -
Shared infrastructure, managed
Kafka, Redis and PostgreSQL run in Docker, managed by the app, remapping ports automatically when they collide. No hand-written
The shared infrastructuredocker compose—and where Compose stops paying off is a longer story. -
Logs, health and graph
Live logs colour-coded per service, with search and follow-tail; health on every card, and a navigable graph to see who talks to whom.
Live logs -
A CLI with full parity
Everything the window does, the
TheasepticCLI does too, running the same engine logic. Automate scenarios in CI or from your terminal.asepticCLI -
Exportable scenarios
Import and export self-contained scenarios. The same environment, reproducible on any machine on the team.
Sharing a scenario -
Your own libraries, unpublished
Aseptic builds your local library and links it into the services that consume it —npm, Maven, Gradle and Python—, rebuilding on the fly. Unlinking only undoes what Aseptic put there.
Local libraries
From zero to running
Four steps, once. If you are still deciding how to build it, the guide explains what a local microservice environment needs and what each approach solves.
- 01
Add your services
Point at the repo folder. Aseptic detects the stack, the ports, the infrastructure and the dependencies.
Adding a service - 02
Assemble the scenario
Choose which services come up together and, for each dependency, whether it goes local, to the cloud or to a mock.
Your first scenario - 03
Press Start
It starts infrastructure and backends in the right order, rewrites the URLs between them and waits for health.
Your first run - 04
Test and watch
Run your flow. Follow the live logs, check health and edit mocks on the fly without restarting.
Activity and checks
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
- Python ready
- .NET prepared
- Go prepared
Local libraries have their own registry: npm, Maven, Gradle and Python, each linked wherever its own ecosystem resolves it.
Plans
Free for personal use: the window and the CLI, whole, with a daily allowance of AI calls to try it out. What you pay for is using it at work: Pro if the licence is yours, Team if your company buys it.
All of Aseptic, by hand.
The window and the terminal, uncut. The aseptic 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
Use it at work.
A commercial licence in a person's name: it holds at any company and it follows you if you move. With the copilot and the MCP server free of the daily limit.
- Commercial use, and the licence is yours
- Copilot and MCP server with no daily limit
- The person pays for it, not the company
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
Beta First public beta. Not signed yet: your OS may warn about an unverified app.
Windows
.exe installer · Windows 10/11 (x64)
macOS
.dmg image · universal (Intel and Apple Silicon)
Not signed yet: the first time, open it with right-click → Open.
Linux
AppImage · .deb
.deb package Frequently asked questions
What gets asked most before installing it. Everything else is in the documentation.
Do I have to reconfigure my microservices to use Aseptic?
No. Aseptic 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), Node/Angular and Python; .NET and Go are prepared. Local libraries have their own registry: npm, Maven, Gradle and Python. Adding a technology means adding a profile, not touching the orchestrator.
Can I test my own library without publishing it?
Yes. Aseptic builds your local library and links it into the services that consume it, each one wherever its ecosystem resolves it: node_modules for npm, the local ~/.m2 repository for Maven and Gradle, the virtual environment for Python. With watch mode it rebuilds and relinks on the fly. It is reversible and non-invasive: the consumer's dependency file is never touched, and unlinking only undoes what Aseptic put there.
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 Aseptic: 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, macOS and Linux. 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