Infrastructure

Enterprise feature flag and experimentation platform

Tillgate · Self-hosted feature flags and experiments that run inside your own network

WatchingDraft scoreEstablished market · since 2014 · AI estimate

59PWAS score

Confidence

Based on 9 of 9 factors

Overview

AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.

Problem: Engineering teams need to manage feature flags, A/B testing, and progressive rollouts across distributed systems, but existing SaaS platforms lock them into cloud hosting and vendor dependencies. Self-hosted solutions give teams control but are complex to deploy and operate.
Solution concept: A self-hosted, enterprise-grade feature flag platform that combines the operational ease and feature richness of SaaS platforms with the control and data sovereignty of on-premise deployment. It would offer a unified interface for feature flags, A/B testing, progressive delivery, and entitlements without vendor lock-in.
Who has it: Engineering teams and DevOps at mid-market to enterprise companies that require on-premise or self-hosted infrastructure, particularly those with regulatory, security, or architectural constraints against cloud-based SaaS.
How they handle it today: Teams today use either commercial SaaS feature flag platforms hosted in the cloud, open-source libraries with limited UI and operational overhead, or build custom in-house solutions. They manage flags, experiments, and remote configurations through vendor dashboards or code.
Why now: Regulatory pressure (SOC 2, data residency laws), increased scrutiny of cloud costs, and the maturation of self-hosted infrastructure tooling make on-premise solutions more competitive. Enterprises increasingly demand control over critical deployment infrastructure.
How it could charge: License-based pricing for self-hosted deployment (per-server, per-engineer, or per-feature), subscription tiers for managed versions, or professional services for enterprise deployments and support.

Score breakdown

A model sorted each factor into a rubric bucket; code turned buckets into numbers. Unknown factors are left out of the score and lower confidence instead.

Market validation

Confidence 95 · 2 evidence · Multiple established paid competitors (LaunchDarkly, Statsig, CloudBees) demonstrate clear market demand for feature flag platforms, and the opportunity identifies a specific gap (self-hosted/on-premise) that these incumbents do not fully address.

Revenue evidence

Confidence 95 · 2 evidence · Multiple established competitors with publicly stated pricing and revenue models: LaunchDarkly and Statsig both run commercial paid plans and offer free tiers, showing the market supports paid feature flag solutions.

Growth

Confidence 95 · 1 evidence · The GitHub repository gained 1938 stars over 1504 days, roughly 1.3 stars per day, indicating modest steady interest rather than rapid growth or breakout momentum.

Problem severity

Confidence 30 · Judged from the description · Feature flags, A/B testing, and progressive rollouts are critical for safe continuous delivery and revenue optimization; mismanagement risks deployment failures and lost revenue, making this a costly pain for engineering teams.

Economic proximity

Confidence 30 · Judged from the description · Feature flags and A/B testing directly influence product decisions, user experience, and revenue outcomes; they sit close to money changing hands through experimentation and progressive customer acquisition.

Distribution

Confidence 30 · Judged from the description · A/B testing and feature experiments inherently require collaboration across engineering, product, and analytics teams; the platform would need multiple users to deliver value, and experimentation results are shared across teams.

Buildability

Confidence 30 · Judged from the description · A self-hosted, enterprise-grade platform requires complex integrations with distributed systems, operational maturity (deployment, upgrades, monitoring), database management, and compliance infrastructure—more demanding than commodity components.

Differentiation

Confidence 70 · 1 evidence · Self-hosting and on-premise deployment is a clear gap that users name (regulatory, security, architectural constraints) and that SaaS incumbents do not serve; this addresses a specific pain point LaunchDarkly and Statsig explicitly do not solve.

Retention and timing

Confidence 30 · Judged from the description · Feature flags are embedded in the continuous delivery workflow and used daily by engineering teams; the timing tailwind is strong as enterprises increasingly prioritize data sovereignty and on-premise control over cloud-only SaaS.

Risk penalties

Depends on one platformA self-hosted platform that integrates deeply with customer infrastructure may create switching costs and vendor lock-in for teams that heavily customize or extend it, though the self-hosted model itself is positioned as a solution to cloud vendor lock-in.−6

Score history

43 · confidence 41 · config v1First score · 10 Oct 2026
59 · confidence 57 · config v1Evidence changed · 10 Oct 2026

Enterprise feature flag and experimentation platform

Overview

Build this business

Verdict

Score breakdown

Risk penalties

Score history

Validation gate

Evidence · 6 items

Market validation

Revenue evidence

Growth

Differentiation

Market

Existing products

Build

Legal reconstruction check

Community