Who builds Aseptic
Aseptic is built by Juan García Valero, a developer, on his own. There is no company behind it, no team and no funding round: there is one person with a specific problem and the evenings he has left.
Why it exists
Working on a system spread across many microservices, the work before writing a
single line of code ate the morning: start Docker, bring up Kafka, Redis and
PostgreSQL, run the migrations, launch each service with its flags, and then
decide by hand what each dependency should do — do I bring that one up too? do
I point it at the shared environment? do I fake it? That forty-step
LOCAL_SETUP.md every team has, and which breaks every time somebody
changes something.
What was missing was not another way to start containers: docker
compose already does that. What was missing was being able to decide,
per dependency, whether this call goes to the service I have
open, to the shared cloud environment or to a mock — and to have something rewrite
those URLs for me, without touching the repositories. That is Aseptic.
Since when
The first commit is from 16 June 2026. The first public beta, with installers for Windows and Linux, came six weeks later. It is still in beta: you can download it and use all of it, and it will keep changing.
How it pays for itself
For personal use —learning, evaluating, your own projects— Aseptic is free and complete: the window and the CLI, uncut. Using it at work, or lifting the daily AI limit, needs a paid plan. That is what keeps this going, and it is spelled out without small print in Pricing.
Nothing you do with Aseptic leaves your machine: the microservices, the containers and the mocks all run on your computer. The little that is processed is detailed in the privacy policy, with every third party named in the list of sub-processors.
Write to me
info@aseptic.dev for anything, or soporte@aseptic.dev if something does not work. If your stack is missing, or if Aseptic solves —or fails to solve— what you expected, I want to know: right now the product is corrected by what the people using it tell me.
If you have found a security flaw, please write to security@aseptic.dev instead of disclosing it publicly.