Flagsmith’s cover photo
Flagsmith

Flagsmith

Software Development

London, England 3,225 followers

Ship faster and control releases with feature flag management. Built with 💜 for the open source community!

About us

Decouple deploy and release. Flagsmith helps you ship faster and continuously improve digital products with feature flags. Open source, with flexible deployments for control over your flags. Flagsmith lets you manage feature flags and remote config across web, mobile and server-side applications. • Deliver true continuous integration. • Get builds out faster. • Control who has access to new features. • Stop monster-coded PRs. • Ship features to production that just work. We're 100% open-source. Host with us or on your own infrastructure. Flagsmith combines the concepts of feature toggles with the flexibility of remote config. Rather than just switching features on and off, you can configure them for individual segments, users and development environments. Utilise our powerful rules engine to manage your features for the users you wish to target. Use segments for staged rollouts or a/b testing.

Website
https://www.flagsmith.com/
Industry
Software Development
Company size
11-50 employees
Headquarters
London, England
Type
Privately Held
Founded
2018

Products

Locations

Employees at Flagsmith

Updates

  • 👀 Job Alert! We're hiring a Product Marketer. You’ll be responsible for defining Flagsmith’s positioning and crafting a marketing strategy that makes enterprise engineering leads trust our tools for shipping features where even tiny mistakes could cost them their jobs. You’ll own every launch, every channel, and the whole site. You’ll shape the release playbook and keep making it better with each launch. You’ll need to be technical enough to understand what engineers really care about and tactful enough to make them feel like you’re offering a solution — not just pitching. You’ll work alongside Asaph Kotzin. If you have any questions, feel free to DM him. Fully remote. Apply here → https://lnkd.in/dhSKfF8P

  • We're going to DevOpsCon. Come say hi 👀

  • 🚨 BREAKING: A rogue AI chef has reportedly been instructing unsuspecting users to add pasta to the pot before the water boils. LangWatch is currently investigating the matter, but early findings suggest the only way to stay safe is to sign up for our product iteration webinar: https://lnkd.in/eKeHX8_U

    Claude Code is down (again) which means my target audience is scrolling through LinkedIn right now. And that’s a perfect opportunity to shamelessly plug the upcoming webinar I’m running with Rogério Chaves We've got a self-improving cooking recipe agent on the loose. He’s been serving recipes to real people, but users keep asking for substitutes it couldn’t handle. So we’ll show you how we used Flagsmith and LangWatch to validate new features and roll out changes safely. Here’s what else we’ll talk about: - Shipping fast with AI without blowing up prod - Product iteration at speed - Releasing new features to select users with feature flags - Adding pasta before or after water’s boiling If you’re interested (or you’re waiting for token limits to reset), come hang with us: 🗓️ Thursday, April 23, 2026 ️ ⌚ 8am PST, 4pm, BST, 5pm CEST Signup link in comments.

    • No alternative text description for this image
  • Pictured: Our engineering team after using compression to shrink doc sizes by 90% and sidestep DynamoDB limits. No, but seriously. We just compressed the JSON documents sitting behind our feature flags. And we did it without blowing up prod. What we used to monitor rollout: - Prometheus for metrics - Grafana dashboard - Flagsmith for feature flags Spoiler: We did run into a critical bug at one point. Here’s what went wrong and how we dealt with it: https://lnkd.in/ee6vudkp

    • No alternative text description for this image
  • Remember when McDonald's built an AI drive-through system that kept messing up orders? 🍟 People love dredging up that story as an example of AI product development gone wrong. But you can learn a lot about product management from it, especially when it comes to designing effective product learning loops. Or so thinks our own Asaph Kotzin. Read about it in his latest blog: https://lnkd.in/e7YCQczT

  • Ignore Matt's comment section and read the blog here 🤭👇 https://lnkd.in/efmHMPzk

    Shipping fast is cool, but  we’re inching dangerously close to turning it into a vanity metric. I’d have entertained giving extra weight to release velocity prior to AI and Claude Code, because writing code was a real bottleneck. But we’ve moved past that point. Shipping fast is easy, if you put out buggy software. The difficult part is shipping fast *and* reliably. I’ve been thinking a lot about the OpenAI x Statsig buyout lately. OpenAI was already using Statsig for feature flagging and real-time product decisioning. They didn’t have to spend $1.1B for the technology. I knew it was more than a technology deal when Statsig CEO Vijaye Raji was appointed OpenAI CTO. Vijaye spent a decade leading large-scale consumer engineering at Meta. That entire job is about shipping software to millions of people reliably. And breaking as few things as possible when shipping fast. The only way to accomplish that at scale is with feature flags. I’ve jotted down a few more thoughts on the OpenAI x Statsig acquisition, why we should all be using feature flags, and why feature flagging is more than just a “front-end convenience.” Link in comments. PS: Great tweet Sam Lambert, hilarious reply Damian Schenkelman.

    • No alternative text description for this image
  • AI can generate code in minutes. But: - You still need to test it - You still need to control who sees it - You still need a way to turn it off instantly That’s where feature flags come in.

    AI is changing how software gets built. You can go from idea to working code in hours. We know this. But releasing that code safely? We're still collectively figuring this out. Most teams are just moving the bottleneck—from development to release gates that block developer productivity. 📅 Join Kyle Johnson and I on March 24th for a live webinar: After AI Builds It, How Do You Ship It Safely? If you’re bringing AI into your workflow, but haven't experienced the velocity gains, this is the missing piece. We’ll cover: - Why traditional release strategies break under AI speed - How to decouple deployment from release - How to test AI-assisted features safely in production - Progressive rollouts + instant rollback strategies Join us: https://lnkd.in/g6qw6fZJ

    • No alternative text description for this image
  • 🪄 We've got the answer...

    Feature flags are great for shipping fast with safely. But the more you ship, the more flags you have to manage. That’s when flag management can turn into a problem. Unless you have a solid post-release flag management workflow in place. Asaph Kotzin and I are running a webinar on how large orgs can avoid post-release feature flag debt with simple automation to: - Continuously monitor flag health - Surface deprecation candidates and recommend next steps - Free your engineers from manual triage Move from reactive cleanup to proactive lifecycle management with: - Visibility into code and usage - Clear ownership and audit trails - Early detection of stale or risky flags 🗓️ March 17 ⌚️ 3pm GMT / 4pm CET / 11am EDT / 8am PDT Sign up → https://lnkd.in/g8xwet4D

  • KubeCon, but without the expo floor. On March 25th during KubeCon + CloudNativeCon Europe, we’re running small 90-minute canal tours in Amsterdam for engineers who actually ship things. No decks. No demos. No badge scans. Just ~12 people on a boat talking about scaling systems, feature flags, infra, production outages, and the strange joy of a clean deploy. Hosted by Flagsmith × Stategraph. First come, first aboard → https://lnkd.in/eKSs5gUj

    • No alternative text description for this image

Similar pages

Browse jobs

Funding

Flagsmith 1 total round

Last Round

Undisclosed

Investors

Polychrome
See more info on crunchbase