About us

We build Kaiten. Then we run on it.

Kaiten is the control plane for B2B SaaS: one model for what each customer bought, what they can use and what runs for them. We are four engineers, all co-founders, at Station F in Paris — and our own releases, hosted environments and Kaiten Cloud organizations live in our own Kaiten, so we meet its rough edges before you do.

Try the early accessWhy we built Kaiten
The Kaiten team, drawn as sushi chefs at work behind a restaurant counter

WHO WE ARE

Who builds Kaiten?

Kaiten is built by four engineers — all co-founders — at Station F in Paris. Each of us had built the same thing before, by hand, in the SaaS companies we come from: the code that decides what a product does for each customer. Kaiten is that code, built once, as infrastructure.

Kaiten is open source under Apache 2.0, from the engine to the SDKs and the CLI. Kaiten Cloud is how we make a living — we operate the same engine for teams that would rather not run it, dedicated or in their own VPC when they must.

OUR STORY

How Kaiten started.

  1. 01

    We built it before

    Each of us had built this second product by hand in the SaaS companies we come from: a licensing service here, a flag wrapper there, a spreadsheet of who runs which version.

  2. 02

    We looked for it elsewhere

    Dozens of conversations with founders, VPs of Engineering, product managers and account managers. Every one of them had built it too. The names of the tables changed; the story did not.

  3. 03

    We build it once, in the open

    One model for what each customer bought, what they can use and what runs for them — public code, with our own operations running on it.

Read why we built Kaiten

HOW WE WORK

Three rules we hold ourselves to.

  • It’s open source

    The rules that decide what your customers can use should be code you can read. Kaiten’s is, under Apache 2.0: audit it, run it on your own infrastructure, fork it, and keep it running whatever happens to us.

  • We say what’s shipped

    What exists is described in the present tense. What doesn’t is called “on the roadmap” in the same sentence — no badge, no footnote, no dates.

  • We use it first

    Our releases, hosted environments and Kaiten Cloud organizations live in our own Kaiten, configured through the same public API. Every friction reaches us before it reaches you.

    See how we run Kaiten on Kaiten

THE TEAM

The people who build Kaiten.

Four engineers, all co-founders. We started Kaiten at Station F after years of building this kind of infrastructure together.

Alexandre Bergere

Alexandre Bergere

Co-Founder & CEO

Alexandre has spent over a decade obsessed with making complex cloud architectures invisible so engineering teams can focus on their core product. Previously the Founder & CTO of DataRedKite—an observability solution acquired by DataGalaxy—he served as Principal Architect, leading Data & AI integration and cloud partnerships with GCP, AWS and Databricks. He also mentors the next generation of engineers at Sorbonne and EFREI. Alexandre co-founded Kaiten to eradicate 'Spaghetti SaaS' and the practice of hardcoding pricing plans, building an open-source control plane that restores engineering freedom by decoupling business logic from the codebase.

Tom Ribuot

Tom Ribuot

Co-Founder & CTO

Tom is a technical leader focused on industrializing stacks to ensure infrastructure strictly obeys business requirements. His background includes serving as a DevOps Engineer for CANAL+ Group and Lead Python Developer at DataGalaxy, where he mastered cloud automation using Terraform, Kubernetes, and Helm. Tom co-founded Kaiten to stop engineering teams from reinventing the wheel every time they need to manage a new pricing plan or feature rollout. By leveraging the OpenFeature protocol and event-driven hooks, he ensures that business packaging is transformed into strict, automated infrastructure rules.

Kevin Gonnord

Kevin Gonnord

Co-Founder & Founding Engineer

Kevin is a Fullstack Developer with nearly a decade of experience scaling B2B platforms and managing complex architectures. Having worked at major platforms like Meetic and DataGalaxy, he has a deep understanding of containerization and the governance flaws inherent in fragmented SaaS ecosystems. At Kaiten, Kevin focuses on ensuring that developers no longer have to pollute codebases with 'if/else' statements for Stripe limits or manually verify logs to debug blocked features. His goal is to provide native evaluation tracking and entitlements that work seamlessly without requiring extra code.

Tom Flenner

Tom Flenner

Co-Founder & Founding Engineer

Tom is a Software Engineer specializing in cloud-native, distributed systems and platform engineering. Currently a Staff Engineer at DataGalaxy and an active contributor to the CNCF ecosystem (including Dapr and OpenFeature), he has experience maintaining critical modules for national-scale organizations in defense and energy. Tom’s work at Kaiten centers on building high-performance, resilient platforms that handle complex entitlement logic and asynchronous metering. He is driven by the mission to decouple business logic, allowing engineers to move faster and experiment safely through standardized, open-source rollouts.

TALK TO US

Talk to the people who build it.

There is one team behind Kaiten. Pick the door that fits.

Where we work: Station F, 5 Parvis Alan Turing, 75013 Paris, France