Benjamin Barbé
Founder · Infrastructure & CybersecurityThe invisible architect securing the most sensitive data in law.
Infrastructure, security, compliance. Every application we ship goes through his standards.
Hosting & managed operations
Your application hosted in France, and kept up to date.
€850 a month: the infrastructure on one side, an engineer day on the other. We don't sell one without the other.
Book 30 minNo lock-in period · The code and the data stay yours
-
ISO/IEC 27001 -
ISO/IEC 27017 -
ISO/IEC 27018 -
ISO/IEC 27701 -
AICPA SOC 2 -
HDS -
GDPR
Certifications of the infrastructure we deploy on — registry and cluster in the Paris region. We do not claim them as our own.
See the certifications in detail They build with us 
A server rents for ten euros a month. That's not what's expensive, and it is certainly not what protects you.
What costs is time. A vulnerability published on a library you use without knowing it. A certificate expiring on a Sunday. A database version reaching end of support. A disk filling up. None of these announce themselves.
Hosting without maintenance is an application ageing in silence. Until the day it falls over — or worse, opens up.
That's why we don't sell hosting on its own.
The founders
Two people behind every deployment.
No anonymous on-call rota, no ticket number. The same two people hold the infrastructure and the technical direction, and they are the ones you get on the phone.
Joachim Darmalingon
Founder · CTO7 years of fullstack legaltech development. Zero approximation.
Technical direction, software architecture, development, integrations and technology choices.
The architecture
What your application actually runs on.
Nothing exotic, and that's deliberate: standard building blocks, assembled the same way for every client. An architecture another team can take over is an architecture you are not stuck with.
01
The foundation
A Kubernetes cluster in France, Paris region. Each application gets its own reserved space, with a compute and memory quota that stops it spilling over onto its neighbours.
02
Two environments
A development environment and a production environment, genuinely separated: two spaces, two databases, two sets of secrets. Nothing being tested touches what is running.
03
The network
Closed by default, inbound and outbound. We open, case by case, what the application needs and nothing else. HTTPS everywhere, certificates renewed on their own.
04
The secrets
Passwords, API keys and tokens live in a vault, never in the code or a config file. They are injected at startup, and they differ between development and production.
05
The data
Managed database, daily backups, object storage for files. Schema migrations run before the new version starts: if they fail, the previous one stays in place.
06
The way out
The code is in your repository, the data exports, the infrastructure is described in files you can take with you. Leaving should stay a decision, not a project.
Your console
Two environments, and one button between them.
Development updates itself every time the code moves. Production waits for someone to decide. The same screen shows you both.
The code's path
From your repository to your users.
You push to main
The code lands in your repository.
The chain builds the image
Compilation, tests, an image stamped with the commit number.
Development updates
Automatically, within minutes. Migrations run before startup.
You take a look
On the development address, with test data.
You promote
One button. Production takes exactly the image you just approved — not a rebuild, the same one.
The day included
Half a day to hold, half a day to move forward.
The engineer day is not a support credit we hope you never spend. It is split in advance, because the two halves don't compete for the same urgency.
The maintenance half-day
It isn't negotiable: it is what makes the hosting sustainable.
- Dependency updates, and reading the vulnerabilities published on the ones you use.
- Version upgrades for the language, the framework, the database.
- Certificate renewal, secret rotation.
- Monitoring: logs, alerts, disk space, response times.
- Backup restoration actually tested, not merely configured.
The development half-day
It's yours, and you decide what it goes into.
- A feature that was missing.
- A screen to rework because your users keep stumbling on it.
- An integration with a tool you have just adopted.
- A fix that isn't urgent but has been sitting there for three months.
- Nothing at all, if the month is quiet: the time carries over to the next one.
Advice
And someone to ask.
The expensive part of a technical project isn't what you build. It's what you build twice.
You're hesitating between two tools. A vendor offers you a component whose price you have no way of judging. You wonder whether a given feature is worth building, or whether something already does it.
Those questions don't fill a quote, but they decide the year that follows. They are part of the package, and they are not counted in hours.
We answer even when the answer is “don't do it”.
Pricing
Two lines, and no third one.
Infrastructure €250 / month Cluster, database, storage, backups, TLS, two environments
One engineer day €600 / month Half a day of maintenance, half a day of development
The package €850 / month Both, inseparable · No lock-in period
A heavier application, unusual traffic or a specific requirement (health data, dedicated architecture) changes the infrastructure figure, not the logic of the package. We price it, and we tell you beforehand.
Security
Six things that don't depend on your vigilance.
The data stays in France. Image registry and cluster in the Paris region. No replication outside Europe, no US subprocessor in the hosting chain.
Everything is closed by default. The network refuses inbound and outbound connections until they are explicitly allowed. A compromised application cannot wander.
Secrets are never in the code. They live in a vault, are injected at startup and differ between development and production. A leaked repository grants access to nothing.
Production doesn't move on its own. Development updates on every push; production waits for a human gesture. No deployment surprises you on a Friday evening.
Backups are tested. A backup that has never been restored is not a backup. Restoration is part of the maintenance half-day.
You can leave. The code is yours, the data exports, the infrastructure fits in files you take with you. We don't hold your applications hostage.
Questions
What people ask us before signing.
Infrastructure hosted in France
Our applications run on OVHcloud infrastructure, the most certified European cloud provider. Your data stays in France, under European law, in audited datacenters.
See the certifications
Let's talk about your application.
Thirty minutes to look at what you have, what already runs and what it would take. We'll tell you whether the package makes sense for you — or whether it doesn't.
Book 30 min See the certifications