Kaiten

Stop building flag systems in Year 3. Start with OpenFeature on Day 1. Here's the story every B2B SaaS team eventually lives through: - Year 1: small team, hardcoded if user.plan == 'pro' checks scattered across 5 files. It's fine. - Year 2: pricing evolves, plans multiply, plan checks are now in 47 files. It's getting weird. - Year 3: engineering grows to 15 people. CEO wants A/B testing. PM wants progressive rollouts. CFO wants entitlements that match the contract. You finally adopt a flag system. You spend a quarter refactoring three years of conditionals. This refactor is the most predictable, most preventable technical debt in B2B SaaS. OpenFeature is the discipline that makes it unnecessary. It's not a flag tool. It's a Cloud Native Computing Foundation (CNCF) open standard — the JDBC for feature flags. You write your code against a standard API on Day 1. Behind the scenes, a "provider" plugs in: → Day 1: a local YAML file (zero infrastructure) → Year 2: an open-source server (flagd, GO Feature Flag) → Year 3: Kaiten, with entitlements built in Zero application code changes between these. The migration cost across providers is zero. Compare: 🔴 Year 3 refactor: a quarter of engineering time, refactor bugs, vendor lock-in to whichever SDK you commit to. 🟢 Day 1 adoption: an afternoon to install. Optionality preserved forever. Same logic as TypeScript, structured logging, OpenTelemetry. The teams that adopt these on Day 1 never regret it. The teams that wait pay a tax. Weekly Stack #06 is the deep dive: what OpenFeature actually is, why Day 1 matters, the 4 capabilities most teams miss (Hooks, Multi-Provider, OpenFeature CLI, OFREP), and how Kaiten fits in the ecosystem. → Link in comments. #WeeklyStack #SaaS #FeatureFlags #OpenSource #BuildInPublic

Every B2B SaaS over 50 enterprise customers has built one. Most don't have a name for it. It's called a control plane — the layer that decides how your application behaves for each customer. Identity, contract, code, runtime, reactions. Today it lives across Stripe, LaunchDarkly, a custom licensing-service, and a Notion doc nobody reads. We wrote a piece on what it actually is, what it's made of, and the three options once you recognize the pattern in your own stack. Link in the first comment ↓ #SaaS #Architecture #PlatformEngineering

May the 4th be with you. To every founder, every engineer, every contributor building B2B SaaS in the trenches — the ones writing glue code at 2am to keep their feature flags in sync with their billing. The ones rebuilding their licensing service for the third time. The ones who shipped despite the legacy stack screaming in protest. You're the rebels. We see you. At Kaiten, we're building the open-source control plane we wished we had at our last companies. Not against the Empire — alongside the rebels. May your tests pass, your deploys succeed, and your data model stay unified. ✨ #MayThe4th #OpenSource #B2BSaaS

You ship a feature behind a flag. A PM asks you to restrict it to Pro users. You add a targeting rule: plan == "pro". It works. You move on. Three months later, pricing changes. Stripe is updated. Someone updates the flag — two days late. Free users see a Pro feature for 48 hours. This isn't hypothetical. It happens every week in B2B SaaS teams that treat feature flags as the place to encode business logic. Here's the thing: OpenFeature — the CNCF standard for feature flagging — explicitly warns against this. Their own docs say: "Entitlement flags are usually long-lived or permanent. Seriously consider whether this is business logic that should not live within a flag at all." The people building the open standard are telling you: don't use flags for entitlements. Why? Because they answer two fundamentally different questions: → Feature flags ask: "Is this code ready to run?" → Entitlements ask: "Is this customer allowed to run it?" One is about delivery. The other is about rights. One changes when engineering ships. The other changes when revenue closes a deal. One is short-lived. The other lives as long as the plan does. We wrote a long piece unpacking the difference, why teams keep blurring it, and what a unified model looks like (with OpenFeature + OFREP on the flag side, first-class typed entitlements on the commercial side, one shared audit trail). Full article → link in first comment #openfeature #saas #platformengineering #featureflags

I’ve been building and scaling B2B platforms for years, and one thing keeps coming back to frustrate me. As engineers, we spend weeks designing clean, scalable, cloud-native systems… only to undermine them with hardcoded pricing logic. ``` if (user.plan == "pro") ``` or ``` if (usage > limit) ``` And just like that, the codebase stops being about the product. It becomes about billing rules, Stripe edge cases, and entitlement workarounds. I see this all the time. The reality is: the true value of a product isn’t defined in a slide deck. It’s defined in the code - by what we choose to enable (or block). This isn’t theoretical. I’ve felt this pain firsthand. That’s why we teamed up with Alexandre BERGERE, Tom Ribuot, and Kevin Gonnord to build Kaiten - an Open-Source SaaS Control Plane 🔥 🚀. Not because we thought it would be useful. Because we needed it. A way to: • Decouple business logic from application code • Manage entitlements & quotas without polluting services • Align feature control with the full product lifecycle & SDLC (thanks OpenFeature) • Track usage without slowing down critical paths In short: a control plane for SaaS - built by product makers, for product makers. We’re still early, building in the open, and learning with the community. If you’ve ever felt like a “billing janitor” instead of a builder… you’ll understand why this matters. Let’s fix this together 🚀 👉🏻 Join the Kaiten OSS Waitlist: https://lnkd.in/e3mwsGcz

Huge news: Kaiten is officially landing at STATION F! 🚀 We are thrilled to announce that Kaiten has been selected to join Landing Zone at STATION F, the world's largest startup campus. As we build the Unified SaaS Control Plane, there is no better place to scale our vision than in the heart of the most vibrant startup ecosystem in Europe. Why does this matter for Kaiten? Scaling a B2B SaaS shouldn't be a nightmare of "glue code" and manual infrastructure syncs. By joining Station F, we’re surrounding ourselves with the best mentors and peers to accelerate our mission: decoupling business logic from infrastructure once and for all. What’s next? This move comes at a pivotal moment for us: ✅ Our Early Access is growing every day. ✅ Our Open-Source core is evolving fast. ✅ Our new website & docs are live for the community. A huge thanks to the team at STATION For their trust. We are ready to turn "SaaS Scaling Paradoxes" into seamless growth for engineering teams worldwide. Special shout-out to the founding team making this happen: Alexandre BERGERE, Tom Ribuot, Kevin Gonnord & Tom Flenner 🚀 The journey is just beginning. Want to see what we're building? 👇 Join the waitlist and secure your spot in our private beta: https://lnkd.in/esvfi2s6 #Kaiten #StationF #LaLandingZone #SaaS #CloudNative #StartUp #ControlPlane #OpenSource #BuildInPublic

As a Full-Stack Engineer, I've always hated the "Double Logic Trap." You know the drill: 1. You write a back-end check to enforce a quota: if (usage > limit) return 403. 2. You then have to replicate that exact same logic in the front-end to disable a button or hide a menu. 3. Stripe updates, the plan changes, and suddenly your stack is out of sync. We've all been there—writing "glue code" that has nothing to do with the actual product features. That's why I'm thrilled to announce I'm co-founding Kaiten: The Open-Source SaaS Control Plane. 🚀 Kaiten is the tool I've always wanted as a builder. It's designed to be the single source of truth for your business logic, from your infrastructure up to your UI: ✅ In the Back-end: Our high-performance Edge SDK handles entitlements and quotas without polluting your core services or slowing down your API. ✅ In the Front-end: Standardized Feature Flags (OpenFeature) allow you to gate UI components seamlessly, based on real-time business rules. ✅ The Bridge: No more manual synchronization. Your code—front and back—strictly obeys the business state defined in Kaiten. I'm building this with Alexandre BERGERE, Tom Ribuot & Tom Flenner because we believe developers should focus on creating value, not building "billing plumbing." We are SHIPPING today: 🎨 New Website: Check our vision at https://kaiten.sh/ 📖 Next-Gen Docs: Live on Fumadocs for maximum speed: https://docs.kaiten.sh/ 🤖 LLM-Ready: We even have a full-text version for your AI coding assistants (ChatGPT/Claude): https://lnkd.in/enUrZemQ Kaiten is Open-Source and we are officially in Early Access. 👇 Join the waitlist and help us kill the "glue code" forever: https://lnkd.in/efqnBucn #FullStack #Kaiten #SaaS #OpenSource #BuildInPublic #DevEx #OpenFeature #CloudNative

Your feature flag tool doesn't know what the customer paid for. Your billing tool doesn't know which features are live. Your deployment pipeline doesn't know either. That's why every scaling B2B SaaS ends up with thousands of lines of glue code holding it all together. We built Kaiten to fix this. Kaiten is an open-source platform that unifies feature flags, entitlements, and deployment topology in one data model. One plan change cascades across permissions, feature access, metering, and infrastructure — automatically. Today we're opening early access, with a redesigned website and the first edition of our documentation. What you can do with Kaiten right now: → Define plans and entitlements (including AI token quotas) → Ship features with flags that know about your customers' contracts — entitlements gate access, flags control rollout, both in one system → Model your deployment topology across clouds and regions → Track usage with immutable audit trail and metering → Let AI agents configure everything via MCP — no console needed Kaiten is open-source, designed for developers and agents, and built for the era where SaaS costs are dynamic, not static. Early access is open. Link in comments. #opensource #b2bsaas #infrastructure #devtools #entitlements #featuremanagement

After weeks of late-night coding, architectural debates, and way too much coffee, I’m incredibly proud to announce that Kaiten is finally live. As a CTO, I’ve seen the same "SaaS Scaling Paradox" break great teams over and over: 1. Sales sell custom plans in the CRM. 2. Product toggles features in a siloed dashboard. 3. Engineering deploys blindly, oblivious to the actual customer contracts. We built Kaiten to kill the "glue code," the flaky scripts, and the broken webhooks that try (and fail) to bridge these worlds. Kaiten is the missing link between your Business and your Infrastructure. We’ve unified three critical pillars into a single engine: - Orchestration & Deployments: Knowing exactly which version runs for which client, anywhere (AWS, GCP, or On-Prem). - Feature Management (OpenFeature compatible): Decoupling deployment from release to mitigate engineering risks. - Monetization & Entitlements: Forcing the code and the infrastructure to strictly obey business rules in real-time. No more "phantom resources" being consumed by expired licenses. No more manual synchronization. Just a clean, business-to-infrastructure state controller. We are officially opening our Private Beta. We’re looking for engineering teams and founders who are ready to stop "taping" their tools together and start scaling with a true Control Plane. Join the waitlist here: 👉 https://lnkd.in/eQU9TVXk Kaiten is just getting started. I can't wait to see what you’ll build with it. #BuildInPublic #SaaS #CloudNative #Kaiten #EngineeringManager

In June 2021, my first startup, DataRedKite, was acquired by DataGalaxy. A month ago, I officially closed that 5-year chapter as Partner and Principal Architect. Leaving DataGalaxy was one of the hardest professional decisions I’ve ever made. I joined through an exit, but I stayed for the people and the mission. From leading Data & AI strategies to scaling core architectures, it was a 5-year masterclass in building a global SaaS leader. I’ve been lucky to work with every team: Engineering, Product, Sales, and partners like AWS, GCP, Azure, and Databricks. A special thanks to Sébastien (Seb) Thomas, Lazhar Sellami, and Nicolas Averseng for your trust. And to Teddy Wagnac, my DataRedKite co-founder—thank you for starting this journey with me. To my colleagues: Alex Jaglale, Alexandre Mutel, SIDLER Alexandre, AYOUB HAMAOUI, Camille Farineau, Chirine Sammouda, Christophe Lemonnier, Déborah Rouiller, Emmanuel JANY, Hannah Pelletier, Jason Gulledge, Julie BIASION ✨, Julie Sartoretti, Julie VIALLET, Julien Laguilhomie, Kevin Gonnord, Kseniia Ilchenko, Laura Corbet Delabre, Laurie du Boullay, Laurent Dresse ☁, Lindsay Paoli, Maïlys Trzcionka, Michel Balter, Noah Michel, Thomas Lathuiliere, Tom Flenner, Tom Ribuot, Tristan CARIOU, Réda Mattar, Rémy Villain, Romain Ourgorry, Victor VINCENT, Vincent Bolon, Vincent Ledoux Thank you for the ride. You’ve shaped the founder I am today. (LinkedIn limits my tags, but the heart is there for everyone I’ve crossed paths with!) But as a builder, I kept seeing a recurring friction. Throughout these years—from my first lines of code at DataRedKite to leading global architectures—one problem never went away: the toxic bridge between "Revenue Logic" and "Engineering Reality." For several months now, I’ve been working behind the scenes with a core group of partners to solve this. We went back to the IDE to build the missing piece of the modern SaaS stack. I am thrilled to finally reveal Kaiten. Kaiten is the Open-Source SaaS Control Plane. It’s the engine we wish we had while scaling platforms over the last decade. Built for performance and developer experience, Kaiten offers:  • Entitlements: Manage access quotas and tiered limits via a 0ms-latency Edge SDK. • Feature Flags: Power your rollouts using the OpenFeature standard.  • Metering: Native evaluation tracking that streams directly to billing engines like Lago or Stripe. Kaiten is my next chapter. We are building it Open Source because you should never have to trust a black box with your core business logic. Follow our journey on the Kaiten for upcoming technical deep dives and OSS updates. Link to the waitlist in the first comment 👇 DataGalaxy, thank you for the ride. To my partners and the community, let’s build the future of the SaaS state. 🚀 #OpenSource #Engineering #SaaS #Architecture #DataGalaxy #Kaiten #Builder