Eighty-four projects on our own servers, on open source

What we did

• check_circleEverything is self-hosted on dedicated servers in France: the Git repository, continuous integration, the image registry, SSO, DNS, databases, metrics, logs, monitoring, the inbound mail server. No hyperscaler anywhere in the chain.
• check_circleDeliberately simple orchestration that two people understand in full — not Kubernetes. Choosing a tool you have not mastered moves the risk rather than reducing it, and an outage at three in the morning is not solved by reading documentation.
• check_circleOne delivery pipeline for all 84 projects: one command, the tests run, the image is built, the new version proves it responds before the old one stops, and rolling back takes a minute.
• check_circle238 automated checks re-read every project's code continuously: vulnerable dependencies, exposed secrets, conventions, dangerous queries, pages missing structured data. What they find becomes a ticket, not an email someone archives.
• check_circle125 services checked from the outside every minute, logs centralised and searchable over a month, metrics per container and per server. Including the overnight jobs, whose failure raises no visible error.
• check_circleThe few exceptions are deliberate and written down: outbound mail delivery goes through a specialist provider, because an IP sending reputation cannot be manufactured in-house. Self-hosting is not a dogma, it is a trade-off — and it is justified line by line.

The services involved

This engagement drew on the following expertise. Each has its own page, with its method and its deliverables.