Run
Infrastructure and hosting
Your servers, held by people who administer them daily for other clients too.
Two situations come to us regularly. The first: three-euro shared hosting where the site falls over as soon as there is traffic and nobody answers the phone. The second, more serious: a server set up six years ago by someone who has left, never updated, whose password nobody knows and whose backups have never been restored. We take on both. A backup only exists if it has been restored at least once — otherwise it is a belief.
The method
How we work
- 01
We inventory what is actually running
Active services, versions, certificates and their expiry, where the data lives, who owns the domain name. That inventory is nearly always missing, and it is what will be missing on the day of the outage.
- 02
We isolate each application
Each in its own container, with its dependencies. An application needing an old version of a component stops preventing every other one from being updated.
- 03
We back up, then restore to check
Regular backups, off the server they protect, and a tested restore. It is the test, not the backup, that makes the difference on the day it counts.
- 04
We keep updates going over time
System security patches, language versions, certificates renewed automatically. An unpatched server has no problem — until it has a very large one.
What you get
Deliverables
- check_circleHosting in France, on dedicated servers, over HTTPS with automatic renewal
- check_circleScheduled off-site backups, and the report of their last restore test
- check_circleAn up-to-date inventory: services, versions, deadlines, access
- check_circleSystem updates applied and logged
- check_circleThe recovery procedure: what to do, in what order, if the server disappears
The proof
Where we have done it
STS Arbres et Jardins
Since 2026A one-year-old site built on an abandoned theme, with an American contact page still live. Full rebuild, migration off WordPress, and local pages built on verified facts.
Read the case studyarrow_forward
Andrée Putman
Since 2025Reissued furniture, interior architecture projects, collaborations: a bilingual site that shows a body of work and sells pieces, without keeping visitors waiting.
Read the case studyarrow_forward
FlatBay
Since 2015Agencies drowning in incomplete files. An assistant that chases missing documents, computes the affordability ratio, and only passes on complete applications.
Read the case studyarrow_forward
Référentiels de données
Since 2024Addresses, public transport, property sales, land registry: four services answering the same questions as paid APIs, built from open public data, running on our servers.
Read the case studyarrow_forward
Gextra
Since 2010Patient referrals, care records, team scheduling, recruitment, billing, mobile apps: a complete business system, sixteen years of rules, thirty sites — and an interface being rebuilt screen by screen without ever stopping the work.
Read the case studyarrow_forward
Gextra Academy
Since 2026The vendor was cutting off access: courses, materials and assessments would have left with the subscription. Everything was recovered, then put back in service on a platform the organisation owns.
Read the case studyarrow_forward
Premium Goods — site public
Since 2018Vanilla, flavours, tobacco: the same product is not named the same way in Europe and in the United States. The public site handles that, from the copy through to the form.
Read the case studyarrow_forward
Clinalliance — réservation
Since 2016A centre opens its slots, clients book, pay and get their invoice. The service has been running since 2016 and has followed every version of our stack.
Read the case studyarrow_forward
Vins de Pomponette
Since 2026An organic estate in the Minervois, a presentation poster and four wines. A site built from scratch — design, development, SEO, hosting — without a single cookie or a request to a third party.
Read the case studyarrow_forward
HAY HuaHin
Since 2024A studio rental in Hua Hin, Thailand. Site rebuilt, hosted, deployed and optimised by us — and it is our own money going into the Google Ads campaigns.
Read the case studyarrow_forward
Notre flotte
Since 2010Git, continuous integration, image registry, SSO, DNS, metrics, logs, monitoring: all of it runs on our own machines, on open-source components. Not out of principle — because it holds load better, costs a fraction, and does not stop when a vendor changes its mind.
Read the case studyarrow_forwardFrequently asked questions
- Does my data stay in France?
- Yes, on dedicated servers hosted in France. It is a strict requirement as soon as personal data is involved, and particularly health data — a field we work in.
- What happens if we part ways?
- You leave with your data, your domain name and the operational documentation. We support the handover to the next supplier. Keeping a client through the difficulty of leaving is not something we practise.
- Do you handle domain names and email too?
- Yes, and we insist the domain name stays registered in your name. On email, caution: a badly handled switch makes incoming mail disappear with no visible error. We never touch mail records at the same time as website records.
Also in “Run”
CI/CD and DevOps
Deploying should be a non-event, several times a week, with no meeting.
speedWeb performance
A slow site loses customers before it has introduced itself. That can be measured and fixed.
monitor_heartMonitoring and on-call
Knowing the site is down before your customer calls to tell you.
mark_email_readEmail and deliverability
Do your automated emails actually arrive? Usually, some of them do not.
Let's talk about your project
Thirty minutes is enough to tell whether we are the right fit. We reply within 48 hours, and we say no when it is not for us.