Try: Feature Flags Shouldn't Require a Separate Service
Posted3 months ago
atono.ioTechstory
calmpositive
Debate
10/100
Feature FlagsSoftware DevelopmentDevops
Key topics
Feature Flags
Software Development
Devops
The article discusses the idea that feature flags shouldn't require a separate service, and presents a solution at atono.io, with the HN community showing mild interest.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
N/A
Peak period
1
Start
Avg / period
1
Key moments
- 01Story posted
Sep 23, 2025 at 8:31 PM EDT
3 months ago
Step 01 - 02First comment
Sep 23, 2025 at 8:31 PM EDT
0s after posting
Step 02 - 03Peak activity
1 comments in Start
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 23, 2025 at 8:31 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45354677Type: storyLast synced: 11/17/2025, 1:10:53 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
The insight: Every time a dev wanted to flip a flag, they had to context-switch to another tool, find the right flag, talk to PM, worry about permissions, then context-switch back.
We realized the issue was around the story or issue object - so we rethought that.
How it works: Feature flags are built directly into stories - toggle them ON/OFF right where you're working Control by environment, customer segment, or location Based on openfeature.dev standard (so you're not locked in) No separate service, no extra $20/user billing, no permission tickets
What else we built: Stories that evolve with your work (not tickets that close and lose context) Chrome extension that captures full diagnostics for bug reports in one click AI tool outputs stay with the relevant work (no more "which ChatGPT thread was that in?") The architecture bet: We treat stories as mutable objects rather than immutable tickets. This lets us embed live controls (like feature flags, usage, etc.) directly into the work context. Free forever for teams up to 5. Just sign up and start using it.
Here's the deal: First 50 people who sign up, invite one teammate, and create a feature flag get our limited edition Capybara t-shirt (our Chief Chill Officer). Email info@atono.io with your username.
Find a bug, get a mug (of coffee)? We'll send you a $10 Starbucks card for the coffee you'll drink while we fix it.
Not trying to be everything to everyone - we specifically built this for SaaS teams who are building production-level products - Interested in your your advice on what we add in next - Try it and break it: atono.io