Who builds MicroLab
MicroLab 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.
<h2>Why it exists</h2>
<!-- REVISAR: igual que en la versión española, este bloque habla en tu nombre.
Si cambias el relato allí, cámbialo también aquí. -->
<p>
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
<code>LOCAL_SETUP.md</code> every team has, and which breaks every time somebody
changes something.
</p>
<p>
What was missing was not another way to start containers: <code>docker
compose</code> already does that. What was missing was being able to decide,
<strong>per dependency</strong>, whether this call goes to the service I have
open, to the shared dev environment or to a mock — and to have something rewrite
those URLs for me, without touching the repositories. That is MicroLab.
</p>
<h2>Since when</h2>
<p>
The first commit is from <strong>16 June 2026</strong>. 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.
</p>
<h2>How it pays for itself</h2>
<p>
For <strong>personal use</strong> —learning, evaluating, your own projects—
MicroLab is free and complete: the window and the CLI, uncut. Using it
<strong>at work</strong>, 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
<a href="/en/pricing">Pricing</a>.
</p>
<p>
Nothing you do with MicroLab leaves your machine: the microservices, the
containers and the mocks all run on your computer. The little that is processed
is detailed in the <a href="/privacy">privacy policy</a>, with every third party
named in the <a href="/subencargados">list of sub-processors</a>.
</p>
<h2>Write to me</h2>
<p>
<a href="mailto:[email protected]">[email protected]</a>. If something does not
work, if your stack is missing, or if MicroLab 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.
</p>
<!-- PENDIENTE: aquí irían los perfiles públicos, igual que en la española. -->