ReleaseAnchor lets you control rollouts, experiments, and kill-switches with ultra-low latency flag evaluation โ without touching your deployment pipeline.
Free plan ยท No credit card required ยท Up and running in 5 minutes
Every fast-moving engineering team eventually hits the same wall: you can't ship fast without breaking things โ unless you decouple deploy from release.
Merge to main anytime. Hide unfinished features behind a flag and enable them only when you're ready โ in any environment.
When something breaks in production, flip a flag and it's gone โ in milliseconds. No hotfix, no rollback, no incident escalation.
Roll out to 1%, 10%, 50% of users. Watch your metrics. Scale up when you're confident. Pull back if something looks wrong.
Deploy code continuously. Release features deliberately. Decouple your deployment pipeline from your product decisions.
Start with the REST API or the JavaScript SDK today. More native SDKs are on the way.
Designed around the workflows that engineering teams actually use โ nothing bloated, nothing missing.
Production, staging, canary โ each environment has fully isolated flag state. No accidental cross-contamination.
Target beta users, internal teams, or enterprise customers. Define a segment once and reuse it across any flag.
Roll features to a precise percentage of users. Scale from 1% to 100% at your own pace โ no deploys required.
Toggle a flag and it takes effect in milliseconds. Stop a broken feature without a deployment or rollback.
Full change history โ who updated which flag, when, and from what state. Stay compliant, stay accountable.
Lightweight, stateless evaluation via official SDKs or a single REST endpoint. No runtime dependencies to worry about.
A clean, fast interface built for engineers โ not product managers.





One method call. One API endpoint. No complex configuration, no runtime overhead, no vendor lock-in.
// JavaScript SDK โ evaluate a flag in one line
const enabled = await releaseAnchor.evaluate("new-checkout", userId);
if (enabled) {
return newCheckoutFlow(req);
}
return legacyCheckoutFlow(req);# Or use the REST API directly โ no SDK needed
curl -s https://api.releaseanchor.com/v1/evaluate \
-H "X-API-Key: env_live_abc123" \
-d '{"flagKey":"new-checkout","userIdentifier":"usr_42"}'
# Response: { "value": true, "reason": "SEGMENT" }Flag evaluation happens fast โ because slow flags are worse than no flags.
Evaluation runs close to your users. Designed for low-latency delivery at any scale.
Ultra-low latency flag resolution on every request โ measured from API call to response.
No persistent connections, no state to manage. Each evaluation is independent and fast.
Built to handle millions of evaluations per month without degrading performance.
Most flag platforms nickel-and-dime you or cut off access the moment something goes wrong. We don't.
If you exceed your monthly limit, your service keeps running. We give you a grace period before evaluations are restricted โ time to upgrade without any sudden cutoffs.
Pay one flat monthly rate. No per-seat fees, no surprise bills when traffic spikes. Your cost is predictable every single month.
Toggle a flag and it takes effect on the very next request โ no CDN to invalidate, no cache to flush.
One GET request returns all flag states for a user. No heavyweight SDK, no agent, no YAML.
Create account, add flag, make API call. No infrastructure to provision, no onboarding call required.
Full change history of every flag update, rule change, and user action. Available on Team and Enterprise โ no need for an enterprise contract just to see who did what.
We build on proven infrastructure so your flag evaluations are fast, secure, and always available.
Hosted on Amazon Web Services infrastructure for global reliability and proven uptime.
Cloudflare sits in front of our API โ giving you fast evaluation and DDoS protection worldwide.
Designed with redundancy at every layer. No single point of failure. 99.9% uptime SLA.
All traffic over TLS. API keys are hashed at rest. User identifiers are never stored or logged.
Start free. Upgrade when you need more. No hidden fees, no overage surprises.
For individuals and small teams getting started with feature flags.
Start for freeNo credit card required
For growing teams that need segment targeting and advanced rollout control.
Credit card required ยท Cancel anytime
For larger teams with higher volumes and priority support needs.
Credit card required ยท Cancel anytime
For organizations that need compliance, security, and dedicated support.
Contact salesCustom quote ยท Talk to our team
No. The Free plan requires no credit card. You can create an account, set up flags, and start evaluating immediately. A card is only required when upgrading to a paid plan.
You don't get cut off immediately. When you cross your limit, a grace period activates and evaluations keep running normally. You'll receive an email notification with time to upgrade before anything changes. Only after the grace period expires do evaluations start returning the default (off) value. No surprise outages at midnight because a billing threshold was crossed.
Yes to all three. You can change your plan at any time from billing settings โ upgrades take effect immediately, downgrades at the end of the current billing period. If you cancel, you keep full access until the period ends. No cancellation fees, no locked-in contracts.
Free includes unlimited feature flags, 2 environments per project, 1 project, and up to 3 team members โ enough for a real production setup. The monthly evaluation limit on Free is 50,000 evaluations. Paid plans unlock more projects, more environments, higher limits, audit logs (Team+), and additional seats.
There are three rule types you can stack on a single flag. Static: always on or always off โ no conditions. Use this for global kill switches or completed rollouts. Segment: enabled only for users who match a named segment (beta users, internal team, paid accounts). You define the segment once and reuse it across any flag. Percentage rollout: enabled for a deterministic slice of your user base โ the same user always gets the same result for a given flag. Rules are evaluated top-to-bottom and stop at the first match.
No. The evaluation API is designed to fail safely. If a call times out or returns an error, the SDK returns the default value you defined in your code โ typically false. Your app keeps running exactly as if the flag is off. The JavaScript SDK also caches the last known state locally, so short network interruptions don't flip anything for active users.
On the very next evaluation call โ typically milliseconds. There is no polling interval or CDN cache in front of the evaluation endpoint. The moment you toggle a flag in the dashboard, the next API call returns the new value. No configuration required.
Never. Each environment (development, staging, production, or any custom environment you create) has completely isolated state. Enabling a flag in staging has zero effect on production. Rules, percentages, and segments are all per-environment.
Join engineering teams that use ReleaseAnchor to release faster, reduce risk, and stay in full control of every feature โ in every environment.
Start for freeFree plan ยท No credit card required