A feature-flag platform for startup engineering teams. Target any audience you can describe: users, devices, organizations, sessions, or any custom group. Rich comparison rules for text, numbers, dates, and versions. Sticky rollouts keep the same audience on the same variation across sessions. Five SDKs that all evaluate flags the same way. Start simple, then turn on approvals, custom roles, and gradual rollouts when your team is ready.
Studio-grade sound, 38-hour battery, active noise cancelling.
Target any audience you can describe: users, devices, organizations, sessions, or any custom group you define. Rich comparison rules for text, numbers, dates, and versions. Combine with AND and OR for full control. Save reusable audiences. Live preview as you compose.
Ship a flag to 10% of pro-tier organizations in Germany with one click. Sticky rollouts keep the same audience on the same variation across requests, sessions, and devices. Different rules can carry different splits, with a fallback split that catches everyone else.
Production requires approval. Staging doesn't. Configure how many approvers, whether comments are required, and whether requests expire, per environment.
Server keys for back-ends, mobile keys for native apps, browser-safe keys for client-side code. Each tuned to its runtime's security model. One SDK contract across all three.
Every change captured with full before-and-after history, who made it, and why. 30 days on Free, 3 years on Scale, custom on Enterprise.
Every change propagates everywhere in seconds. Your SDK keeps a local copy and evaluates flags in your runtime, so there's no network call per flag check. SSE push updates are coming soon for sub-second propagation. JavaScript, Python, Go, Ruby, and an Edge Worker SDK all evaluate the same way, so what your back-end returns matches what the edge serves.
Ship to 1%, watch the metrics, ramp up. Every change is instant. No redeploys, no flag drift.
A built-in statistical engine, variant tracking, and metric integrations are on the way. Today: ship the slider on the left and bring your own analytics for measurement.
Five SDKs that all evaluate flags the same way: JavaScript, Python, Go, Ruby, and an Edge Worker SDK. What your back-end returns matches what the edge serves. OpenFeature provider for JavaScript and the Edge Worker. REST API for anything else.
// Local cache; in-process eval after first sync import { FeatClient } from '@feathq/js-sdk' const feat = new FeatClient({ apiKey: process.env.FEAT_KEY!, dataPlaneUrl: 'https://data.feat.so', }) await feat.ready() const { value } = await feat.evaluate('new_checkout_v2', false, { targetingKey: user.id, user: { key: user.id, plan: 'pro' }, })
Something on fire? Hit kill. The change propagates everywhere in seconds. Every SDK picks it up on its next refresh, 30 seconds by default and configurable lower for emergencies. SSE push updates are coming soon for sub-second propagation. No rollback. No redeploy. No standup.
The basics every team gets, on every plan. No setup, no settings page.
Flip on what your team is ready for. Disabled features vanish from the console, so it never grows past what you actually use.
