Idea checked
a feature flag service for small teams
There is demand for lightweight feature flags, but the search did not find a clear small-team-only service with strong traction.
Confidence: medium — We found 6 named projects, 37 first-hand complaints, 15 stated wants, and 3,451,248 monthly downloads on the biggest package. But most competitors are unclear or stale, so the gap is still only partially supported.
- hackernews 30
- github 20
- githubissues 17
- discourse 20
- intent 15
- stackexchange 3
- registries 13
- tavily 8
- devto 10
Interest over time From data
Hacker News stories mentioning feature flags rollouts (topic read as “feature flags”), by year — 17 in total, currently falling.
- 2021
- 2022
- 2023
- 2024
- 2025
- 2026
This counts discussion on Hacker News, not global search demand. For developer tooling the two move together; for a local service business they do not.
Who is already building this From data
-
flags by Vercel is the strongest usage signal in the search: an npm feature-flags toolkit for Next.js and SvelteKit with 3,451,248 monthly downloads.
-
@openfeature/core is a shared OpenFeature JS package with 22,639,228 monthly downloads, so this ecosystem already has heavy usage for flag-related building blocks.
-
gofeatureflag/go-feature-flag is a self-hosted feature flag solution with 281,150 monthly Docker pulls.
-
gofeatureflag/go-feature-flag-cli has 69,003 monthly pulls, and go-feature-flag-lint has 10,162 monthly pulls, which suggests a real toolchain around that project.
-
TinyToggle is a very small GitHub project with 3 stars and a last push on 2026-05-31; it is still maintained, but tiny.
-
feature-flag-service is another small GitHub project with 1 star and a last push on 2026-01-24; it is still maintained, but also tiny.
-
Flagix is a 2-star TypeScript repo last pushed on 2026-04-16, and CipherFlags is a 2-star TypeScript repo last pushed on 2025-05-09; both are live but very small.
-
Two GitHub repos in the search look dead or stale competitors: chrisneagu/FTC-Skystone-Dark-Angels-Romania-2020 has 297 stars and last pushed on 2024-04-12, and redesigned-pancake has 253 stars and last pushed on 2021-05-16.
What people actually say From data
-
"Does your team use feature flags? If not, why not?" This HN thread got 149 points and 140 comments, which shows active curiosity about adoption.
-
"I work for a startup and as we grow we are increasingly depending on feature flags for releases." This HN comment ties feature flags directly to startup release workflows.
-
"One of the side-effects that come with more feature flag(FF) use is the FF cleanup burden." The same HN comment points to maintenance pain as adoption grows.
-
"We had a feeling that feature flags should be simple and effective, not complicated, slow, or expensive." This HN launch post is a direct statement of the small-team desire.
-
"Feature flags become technical debt." This HN post is explicit about the long-term cost of flagging systems.
-
"Teams spend 3-5 hours/week manually auditing and removing stale flags." This same HN post quantifies the cleanup burden.
People asking to be sold to From data
-
"We need the team to be able to make changes to flags without redeploying" is the core ask implied by multiple feature-flag posts and requests in the search.
-
"Could you please enable the AI Agents (Beta) feature flag for my n8n cloud workspace?" is a direct request to turn on a specific flag for a workspace.
-
"Would it be possible to split `--org-mode` into granular per-category flags so users can opt into only the org features they actually use?" is a willingness to pay for finer control over flags, not just basic toggles.
-
"I would love to have more different flags for finer admin control." This is a plain request for more granular flagging.
-
"I recently asked whether HN used feature flags with their teams, turns out quite a few of us do!" shows active team usage and likely willingness to evaluate tools around it.
Where the opening is Model estimate
The model's read of the signals below — not something anyone measured.
-
The search does not show a clear product built specifically for small teams that want feature flags without enterprise complexity, setup, or pricing friction.
- hackernews FlagSwift – Feature flags for teams who can't afford other feature flags tools 2025-11-21
- hackernews Self-host a robust feature flag tool for your team for just $5 2024-03-19
- hackernews Show HN: FeatureFlare – Feature flags for SaaS teams tired of rolling their own 2026-02-20
- tavily 9 Top Feature Flag Solutions for Modern Product Teams in 2026
- tavily Feature Flag Tools Compared: 10 Platforms for Safer Releases
- tavily The 10 top feature flag management tools in 2026 | Kameleoon
- tavily 7 Best Practices to Implement Feature Flags at Scale in 2026 | Growthbook Blog
-
Existing players split into big generic systems, self-hosted OSS, and tiny side projects; none of the named projects in the search clearly own the 'small team, simple, affordable' wedge.
-
The data also does not show a strong niche around cleanup, lifecycle management, or flag-sprawl prevention for small teams as a bundled service.
How big the market might be Model estimate
The model's read of the signals below — not something anyone measured.
-
This search found 6 named projects: 3 container images, 2 open-source repositories, and 1 package.
-
2 of those projects are dead or stale, and 4 have unknown activity, which means the competitive field is real but not crowded with obviously dominant maintained repos.
-
The largest monthly usage signal was 3,451,248 downloads for the npm package flags.
-
The search surfaced 37 first-hand complaints, 15 stated wants, and 3 unsolved questions across 8 matching community forums.
- hackernews Ask HN: Does your team use feature flags? 2022-01-28
- hackernews Ask HN: How do you deal with feature flag cleanup? 2024-12-01
- hackernews Show HN: FlagShark – Automatically removes stale feature flags via PRs 2025-06-14
- githubissues Feature request: granular opt-in flags for org-mode tool categories (Teams chat, channels, SharePoint, etc.) 2026-04-15
- githubissues [Feature Request]: Additional FTB Teams flags for better admin control 2024-04-03
- discourse Request to enable AI Agents (Beta) feature 2025-11-11
- discourse Feature Request: Prioritize Professional Post-Error Behavior in Enterprise/B2B Contexts – Quick Accountability Over Verbose Recovery 2026-02-13
- discourse Rclone 1.43 release 2018-09-08
- hackernews Self-host a robust feature flag tool for your team for just $5 2024-03-19
- hackernews LaunchDarkly for Prompt Management 2024-03-19
- tavily Feature Flag Tools Compared: 10 Platforms for Safer Releases
- tavily Statsig Glossary - Feature Flag Services
- tavily 7 Best Practices to Implement Feature Flags at Scale in 2026 | Growthbook Blog
- tavily 9 Top Feature Flag Solutions for Modern Product Teams in 2026
- tavily The 10 top feature flag management tools in 2026 | Kameleoon
- hackernews Ask HN: Feature Flags? 2011-09-23
What could go wrong Model estimate
The model's read of the signals below — not something anyone measured.
-
Feature flags are already a mature category, so a new small-team service will be compared against established names and open-source alternatives immediately.
-
The biggest demand signals in the search are not about buying a new service; they are about cleanup, simplicity, and specific flag requests inside existing products.
- hackernews Ask HN: How do you deal with feature flag cleanup? 2024-12-01
- hackernews Show HN: FlagShark – Automatically removes stale feature flags via PRs 2025-06-14
- hackernews Show HN: FlagShark – Automatically remove stale feature flags via GitHub PRs 2025-06-04
- discourse Request to enable AI Agents (Beta) feature 2025-11-11
- githubissues Feature request: granular opt-in flags for org-mode tool categories (Teams chat, channels, SharePoint, etc.) 2026-04-15
- githubissues [Feature Request]: Additional FTB Teams flags for better admin control 2024-04-03
-
A small-team-only product may struggle if it looks like a thin wrapper over existing flag SDKs instead of solving setup, governance, and cleanup end to end.
What to do this week Model estimate
The model's read of the signals below — not something anyone measured.
-
Build for one narrow promise: lightweight feature flags for teams under about 20 engineers, with setup measured in minutes, not days.
-
Make cleanup a first-class feature, because the strongest pain in the search is stale-flag debt and manual auditing.
-
Lead with a simple hosted service plus a tiny SDK, then add self-hosting only if users ask for it; the search shows OSS and containers already exist, but small-team simplicity is the opening.
-
Validate willingness to pay by interviewing people who already asked for granular flags or workspace-level enablement, since those are the clearest buying signals found.
Competitor strength From data
Counted, not judged. Only projects that expose a hard number — stars, downloads, last commit — appear here, so they stop looking identical to each other. Products with no public metrics are discussed above instead of being given a row they cannot fill.
| Project | Stars | Downloads / mo | Activity |
|---|---|---|---|
| chrisneagu/FTC-Skystone-Dark-Angels-Romania-2020 | 297 | — | Dead 2024-04-12 |
| Sfedfcv/redesigned-pancake | 253 | — | Dead 2021-05-16 |
| npm: flags npm | — | 3,451,248 | — |
| docker: gofeatureflag/go-feature-flag docker | — | 281,150 | — |
| docker: gofeatureflag/go-feature-flag-cli docker | — | 69,003 | — |
| docker: gofeatureflag/go-feature-flag-lint docker | — | 10,162 | — |
- 2 open source
- 1 package
- 3 container
- 2 dead
- 37 first-hand complaints
- 15 stated wants
- 8 communities discussing it
Domain names From data
Checked live against the registry, built from the subject of the idea rather than the first words of the sentence. A literal check is a fact; a brandable suggestion would be noise.
- featureflags.com taken
- featureflags.io available
- feature.com taken
- getfeature.com taken
Was this useful?
Noted — thank you. Nothing was sent anywhere else.