Back to all companies
Sign in
Back to all companies
DevCycle logo

DevCycle

Winter 2014Acquired

Feature Flag Management Built for Developers

Save
DevCycle logo

DevCycle

Winter 2014Acquired

Feature Flag Management Built for Developers

Save
Company details

DevCycle empowers development teams with seamless management of code deployment and feature releases. Our flexible and integrated Feature Management solution, specifically designed for developers, grants teams full control over their feature flags while preventing the accumulation of tech debt. With our scalable and cost-efficient platform, teams can focus on what truly matters—building exceptional software—without being bogged down by the complexities of feature management.

Previously known as Taplytics, born at Y Combinator in Silicon Valley as an A/B Testing and Experimentation solution for product and marketing teams, we have evolved into DevCycle, a trusted Feature Management Solution utilized by some of the world's largest brands. Serving millions of end-users and launching billions of events, we understand the demands of high-scale operations.

Location
Toronto, ON, Canada
Founded
2011
Category
SaaS
YC Directory Pagedevcycle.com
Founders
  • AN
    Andrew Norris
    Founder/COO
    X / TwitterLinkedIn
  • JN
    Jonathan Norris
    Founder/CTO
    X / TwitterLinkedIn
  • CD
    Cobi Druxerman
    Founder/CPO
    LinkedIn

DevCycle empowers development teams with seamless management of code deployment and feature releases. Our flexible and integrated Feature Management solution, specifically designed for developers, grants teams full control over their feature flags while preventing the accumulation of tech debt. With our scalable and cost-efficient platform, teams can focus on what truly matters—building exceptional software—without being bogged down by the complexities of feature management.

Previously known as Taplytics, born at Y Combinator in Silicon Valley as an A/B Testing and Experimentation solution for product and marketing teams, we have evolved into DevCycle, a trusted Feature Management Solution utilized by some of the world's largest brands. Serving millions of end-users and launching billions of events, we understand the demands of high-scale operations.

Location
Toronto, ON, Canada
Founded
2011
Category
SaaS
YC Directory Pagedevcycle.com
Founders
  • AN
    Andrew Norris
    Founder/COO
    X / TwitterLinkedIn
  • JN
    Jonathan Norris
    Founder/CTO
    X / TwitterLinkedIn
  • CD
    Cobi Druxerman
    Founder/CPO
    LinkedIn

Pressure-test this opportunity

Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.

On this page
  • Overview
  • Founding Story
  • Timeline
  • What They Built
  • Market Position
  • Target Customers
  • Market Size
  • Competition
  • Business Model
  • Traction
  • Post-Mortem
  • The pivot moved closer to engineering value
  • Open standards traded lock-in for strategic reach
  • Observability completed the feedback loop
  • Key Lessons
  • Sources

This report was generated by our Deep Research agent and may contain mistakes.

Did we get something wrong? DM @oscrhong and we'll fix it ASAP!

Startups.RIP — Dead startups, alive ideas
PricingContactPrivacyGot feedback? DM @oscrhong
Exec Briefing

Actionable insights

If you only have a few minutes to spare, here’s what investors, operators, and founders should know about DevCycle (W14).

  1. The mechanism became the product. Taplytics sold mobile experiments; DevCycle isolated the runtime control beneath them. Engineering teams had a broader, more frequent need for safe releases.
  2. Open standards improved the fit. OpenFeature reduced SDK lock-in but made DevCycle compatible with more stacks. That neutrality also let Dynatrace add control without replacing customer instrumentation.
  3. Action needed evidence. DevCycle could change production exposure instantly; Dynatrace could measure errors, latency, and outcomes. Joining them closed the loop between release intent and observed health.
  4. Strategic logic is not a return multiple. The product continued and entered a larger platform, but undisclosed terms and absent financials prevent a stronger verdict on the acquisition.

Overview

DevCycle was the second act of Taplytics, a Toronto company that began with mobile A/B testing and spent more than a decade controlling what software users saw. In 2022, the team turned that experience into a developer-first feature-flag platform built around the OpenFeature standard.[1]

Dynatrace acquired DevCycle in January 2026 because feature flags were becoming part of observability's control loop. DevCycle could change production behavior instantly; Dynatrace could measure the result. The deal validated DevCycle's pivot while showing why an independent flag dashboard was strategically incomplete.[2]

Founding Story

The company that became DevCycle started as Taplytics. Aaron Glazer led the original business, while Andrew Norris, Jonathan Norris, and Cobi Druxerman are the founders YC now associates with DevCycle. The team joined Y Combinator's Winter 2014 batch and initially sold A/B testing for mobile apps.[3]

Taplytics let a product team change an app experience, split users into cohorts, and measure behavior without waiting for a complete release cycle. By May 2015, it had expanded into analytics and push notifications. Glazer described the ambition as “a full-blown mobile optimization solution” and said the company wanted to “drive higher mobile engagement and higher monetization through the entire user lifecycle.”[4]

The company raised a $2.4 million seed round from YC and a long list of operator-investors, including Alexis Ohanian, Paul Buchheit, Mark Pincus, and Kevin Hale. Glazer said Taplytics had delayed announcing the already-closed round because “we’ve just been putting all of our resources towards product development.”[4]

Over time, the mechanism beneath experimentation became the larger opportunity. Feature flags decoupled deployment from release: teams could ship dormant code, expose it gradually, test variants, and turn it off without another deployment. In March 2022, Taplytics raised $5 million to launch DevCycle as a separate feature-management suite for engineering teams.[1]

Timeline

  • 2011: YC's company record uses this as the founding year for the Taplytics/DevCycle business.[3]
  • 2014: Taplytics joins YC W14 and launches mobile A/B testing.
  • 2015: The company announces a $2.4 million seed round and expands into analytics and push notifications.[4]
  • 2022: Taplytics raises $5 million to launch DevCycle; OpenFeature enters CNCF that June.[1][5]
  • 2023: OpenFeature reaches CNCF Incubating status; DevCycle commits to it across supported languages.[5]
  • 2026: Dynatrace acquires DevCycle for undisclosed terms.[2]

What They Built

DevCycle gave developers a control plane for features already present in deployed code. An engineer wrapped a behavior in a flag, created targeting rules, and exposed the feature to selected environments or cohorts. The team could increase exposure gradually, compare variants, schedule a release, or disable a problem without rebuilding the application.

The platform included SDKs for common languages, centralized flag configuration, real-time updates, permissions, audit logs, experiments, reusable targeting, and integrations with GitHub, Jira, Terraform, Slack, webhooks, and Vercel Edge Config.[6] The product also emphasized flag cleanup, a necessary defense against old branches becoming permanent code debt.

Its decisive design choice was OpenFeature. The CNCF project standardizes the application-facing API for feature flags, separating instrumentation from the vendor that evaluates a flag. CNCF accepted OpenFeature in June 2022 and promoted it to Incubating in November 2023.[5] DevCycle publicly committed to the standard across its supported languages and onboarding in 2024.[7]

That openness reduced customer lock-in, but it also made DevCycle easier to combine with another control system. Dynatrace could consume OpenFeature data and join a flag change to latency, error, or conversion signals without forcing customers to replace every SDK.

Market Position

Target Customers

DevCycle sold to engineering, platform, and site-reliability teams that released frequently enough to need runtime control. Taplytics had originally addressed product and marketing teams; DevCycle moved the buyer and daily workflow closer to code, CI, and incident response.

Unlock the full DevCycle teardown

Read the complete post-mortem, the rebuild playbook, and the exact reasons DevCycle is still worth studying now.

See Pro plans