flochai
Repositories and reviews
Infrastructure, pipelines, and configuration live in your version control and move through documented pull requests.
Your DevOps team.
Without building one.
For seed to Series B product teams
We own the pipelines, clusters, and platform backlog so your engineers ship product. Recurring engineering ownership, without waiting for a full-time hire.
Business-hours incident support is included. Named on-call windows are available separately; this is not a 24/7 pager rotation.
include: - project: components2010244/components-ci file: components/static-site-deploy.yaml deploy: extends: [.static-site-deploy, .pipeline-rules-main] environment: url: https://flochai.com variables: STATIC_SITE_BUCKET: www.flochai.com-devops-site STATIC_SITE_DISTRIBUTION_ID: E7S499IPMVXL2
Internationalstartup to enterprise
No black boxstep-by-step runbooks for deploys, recovery, infra
GCP + K8sGitLab, Terraform, AWS
EU remoteEnglish + French
DevOps as a Service.
Hiring DevOps takes months, and one hire can't cover pipelines, Kubernetes, cloud, and security anyway. The subscription can: real ownership, every week, without the recruiting.
Who it's for. Teams shipping product while the platform rides on one overloaded engineer, or on nobody. You need someone accountable for the infrastructure, not another ticket in a backlog.
What it replaces. A DevOps hire costs €100–120k a year once employer charges are counted, and takes two to four months to find, when the search works at all. This starts in days for about half that, and unlike an agency it doesn't disappear after handover. Same person, every week, who knows your stack cold.
From €4.9k/month, two days a week.
Monthly, three or six months.
Get in touch
Monthly, three or six months.
Own. The platform is ours to keep healthy.
Infrastructure as Code, CI/CD, clusters, upgrades, and security patches, kept versioned, reviewed, and boring.
Ship. Roadmap work in your sprint cadence.
Migrations, new environments, cost cleanups, and the platform features your product work keeps waiting on.
Answer. When production is on fire, you call.
Business-hours advisory: we get on the line and debug it with you, not a pager rotation that pages someone else. Want a named window with a response time you can hold us to? That's an add-on, priced openly.
Review. A monthly platform review, in writing.
What changed, what's at risk, and what's next, so the retainer never becomes a black box.
CI/CD & releasesKubernetes & GitOpsCloud infrastructure
ObservabilityDevSecOpsKafka & streaming
Explore technical capabilities →
The work stays yours.
Every change leaves a reviewable trail. If the engagement ends, your team keeps the platform, the decisions, and the path forward.
Runbooks and roadmap
Failure modes and recovery steps are written down; risks and platform work stay prioritized against the product roadmap.
Monthly platform review
What changed, what remains at risk, and what should happen next, delivered in writing.
No black box. You lose a vendor if we leave, not the knowledge required to run your platform.
Recent work, end to end.
Scoped, built, and handed over with docs and runbooks the teams actually use.
GitLab CI components library ↗
A shared library of agnostic pipeline components: build, deploy patterns, health checks, integration tests, rollback. Every service inherits the same seven-stage flow instead of one-off scripts, and this site's own deploy job is one of its components.
Migration · recent
Full enterprise migration to a new domain
Moved with zero downtime, and the shareholder deadline held.
Problem
An enterprise platform had to move to a new domain end to end, at scale.
Constraint
No downtime, a shareholder deadline that could not move, and the legacy stack in service throughout.
Contribution
DNS, API gateways created and reworked, managed certificates, ingresses, new microservices, and the networking back to the legacy stack.
Artifacts
The migrated platform, and the testing that proved nothing broke.
Reliability · 2026
Self-hosted GitLab recovery
A one-hour recovery point objective, written down, with two recovery paths the team can rehearse.
Problem
A self-hosted GitLab instance needed CVE upgrades while a background migration had been failing for four months.
Constraint
The production service had to remain usable while the failure was traced through GitLab and PostgreSQL.
Contribution
Carried out the upgrades, diagnosed the migration as an upstream issue, and defined the recovery approach.
Artifacts
Hourly backup design, snapshot process, recovery runbook, and two documented recovery routes.
Three tiers, two projects.
Everything lands in your repos with runbooks, and invoices hold no surprises. If we vanished tomorrow, you'd lose a vendor, not your platform.
Choose your commitmentSix months is selected by default and carries the best rate.
Named on-call windowEvery tier covers business hours. A named window (weekdays 07:00–22:00, weekends 09:00–19:00 CET, 30-minute acknowledgement) adds 30% with a €1,200 monthly minimum, and Scale already includes one.
The retainer · ongoing ownership
Essential
€2.7k / monthon a six-month term
One day a week. For small teams that need the platform looked after properly, not owned outright.
- One day a week, in your sprint cadence
- Monthly platform review, in writing
- Business-hours advisory
- Monthly, three or six months: your call
CoreMost popular
€4.9k / monthon a six-month term
Two days a week. Infrastructure ownership on subscription, for companies that need real DevOps without a full-time hire.
- Two days a week, in your sprint cadence
- Monthly platform review, in writing
- Business-hours advisory
- Monthly, three or six months: your call
Scale
€8.4k / monthon a six-month term
Three days a week, with a named on-call window. For platforms whose production genuinely cannot wait until Monday.
- Three days a week, in your sprint cadence
- Named on-call window, included
- Monthly platform review, in writing
- Monthly, three or six months: your call
Every price, all three terms
Flexibility costs more than commitment does. Start monthly if you want to see the work first, then move down the table once you have. Thirty days' notice either way.
| Term | Essential | Core | Scale |
|---|---|---|---|
| Monthly, 30 days' notice | €3,100 | €5,600 | €9,600 |
| Three months | €2,900 | €5,200 | €9,000 |
| Six monthsbest rate | €2,700 | €4,900 | €8,400 |
On-call, when you need it named. Essential and Core cover business hours.
The add-on names the window: weekdays 07:00–22:00, weekends 09:00–19:00 CET,
a production incident acknowledged within 30 minutes and worked within the hour, six hours
a month included. Nights and 24/7: quoted case by case, with named collaborators.
+30% / month, min. €1,200
Project work · fixed scope
Platform audit
€4.9k fixed / one week
- Full review of CI/CD and infra
- Risks and fixes, ranked by impact
- A restore drill, so recovery is measured not assumed
- A 90-day plan and walkthrough call
- Credited in full against month one on a 6-month term, within 60 days
Build / migration
€750 from / day
- Scoped builds: CI overhaul, K8s, GitOps
- Runbooks and handover docs
- 30-day post-launch support
Prices ex. VAT. US company? Prices in dollars.
What teams say.
Tenacity, reliability, and a strong sense of ownership. He quickly became someone the team could rely on.
Gustavo Alfaro
Director of Software Engineering, MTN Global
Son engagement, sa rigueur et son attitude proactive font de lui un profil capable de contribuer à des projets DevOps exigeants.
Fall Lewis Yomba
Senior Technology Instructor, MCT, Microsoft & AWS
Questions teams ask.
What does the subscription actually include?
On Core, two days a week of hands-on DevOps work in your sprint cadence: platform ownership, roadmap delivery, business-hours advisory when something breaks, and a written monthly review. Essential is one day a week, Scale is three, and more days can be arranged when the roadmap needs them.
Are you a one-person operation or an agency?
A small team of mixed levels, lean by design. For larger builds we bring in trusted collaborators for frontend, security, or SRE, with clear scoping so you always know who owns what.
Do you work with startups or larger companies?
Both. Most retainers are seed to Series B startups that need real infrastructure ownership without the cost of a full hire, plus the occasional larger team that wants outside eyes on a specific platform problem.
Will our team be able to maintain what you build?
That's the whole point. Everything lives in version control, gets reviewed by your team as it's built, and ships with runbooks for the top failure modes. No lock-in, no mystery scripts.
Do you do 24/7 on-call?
Not as a pager rotation. Every retainer covers business-hours advisory: when something is on fire you call us and we debug it with you. The named on-call add-on is a defined window: weekdays 07:00–22:00 and weekends 09:00–19:00 CET, public holidays included except 24–25 December and 1 January. A production incident is acknowledged within 30 minutes and worked within the hour, with six hours a month of out-of-hours work included. Scale includes it. Nights and true 24/7 are quoted case by case, because they take a rota of named collaborators rather than one person, and we would rather price that honestly than sell a pager one person cannot hold. Projects include a 30-day post-launch support window.
What time zones do you cover?
Based in Europe (CET), full-day overlap with EU teams and mornings with US East. Async first: Slack, Linear, and email over back-to-back meetings.
How do we get started?
Send what you're building and where it hurts through the contact page. You'll get a reply within a business day: either a discovery call slot or a pointer to someone better suited if it's not our wheelhouse.
Tell us what you're shipping.
Share your stack and where it hurts. The engineer who would do the work replies within one business day. No sales layer.
Start the conversation →Not sure which engagement fits? That is part of the first conversation.