Plans and pricing

For personal use, Aseptic is free: the window and the CLI, whole and uncut, with a daily AI allowance 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.

Free Beta

€0Personal use · all you need is an account

All of Aseptic, by hand.

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

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

To try the AI

150 calls a day to the MCP server
30 messages a day to the copilot

What it does not include

Use at work: using it for your job or your business requires a paid plan (terms)

Download Aseptic

Pro Yours

€89/yearor €9/month — save €19, two months free · per person · you pay for it, not your employer

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 AI free of the daily limit.

Everything in the Free plan
Commercial use: your job, your clients, your business
The licence is yours and follows you between employers
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
Email support

The person buys it. If your employer pays, what you need is Team.

Get Pro

Team

€299/yearper seat · from 5 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, per seat
Shared scenario catalogue
The licence belongs to the company, not to each person
Centralised licences and billing
SSO with your identity provider

Founding Team: the first ten teams pay half for their first two years, with the code FOUNDINGTEAM.

Get Team

What it adds to what you already use

Aseptic 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 Aseptic 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. Aseptic 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 working on 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 aseptic CLI carries the same engine logic, so what you set up by hand gets automated in CI without rewriting it.

And none of it asks you to rewrite your repos: Aseptic does not put a startup file inside your code, nor does it require the project to have been started from scratch around it — which is what separates this from the orchestrators you declare inside the application.

All of that is in the free plan, whole and for good. What you pay for is using it at work, and that is why there are two plans and not three: Pro when the licence belongs to the person, Team when the company buys it.

Pro or Team: whoever pays decides

Pro is an individual licence. The person buys it and pays for it, not their employer, and it is not meant to be expensed. In exchange it is yours: it holds at any job and you take it with you when you move. It is the same deal as JetBrains' personal licences, and it exists so that someone paying for their own tool is not charged what a company pays to equip its people.

Team is the company licence. If your employer is the one paying —an invoice in their name, seats added and removed as people join and leave, SSO, a shared catalogue of scenarios— that is Team.

What counts as a call

It depends on the surface. On the MCP server, a tool call: every action an external agent performs on Aseptic (start a scenario, read some logs, create a mock). On the copilot, a message: every time you write to it, including every action it takes to answer you.

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.

One being 150 and the other 30 is deliberate: a tool call is not a message. An agent spends twenty or thirty calls settling a single thing you asked for in one sentence.

The counter resets at midnight UTC. When little is left, the app shows it next to the model picker; from the terminal, aseptic 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

Aseptic 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. Aseptic 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 Aseptic 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 info@aseptic.dev and we will let you know as soon as the plans open.