Comparison
Railflag vs ConfigCat: an honest comparison
ConfigCat and Railflag share a lot: flat published prices with no per-seat fees, evaluation in your process, and data in the EU. ConfigCat has far more SDKs, including mobile and game engines. Railflag streams changes in real time and can pause a rollout when your metrics drift. Here is how to choose.
Choose ConfigCat if you need SDKs for mobile, C++, Unity or Unreal, or a very cheap plan for a handful of flags. Choose Railflag if you want changes to reach every server within a second, rollouts watched against your monitoring, and approvals with an MCP server built for agents.
At a glance
IncludedPaid tiers only, add-on or limitedNot available
| Railflag | ConfigCat | |
|---|---|---|
| Free plan | Starter: 3 members, 3 environments, 10,000 browser users a month, never cut off | Unlimited seats, 10 flags, 2 environments |
| Published prices | Team €249 and Business €899 a month; browser users above the plan at a published rate | Flat tiers: Pro $110, Smart $325, Enterprise $900 a month |
| No per-seat fees | Unlimited members on paid plans | Unlimited seats on every plan |
| Evaluates flags in your process | Always, from rules held in memory; keeps serving if it can't reach us | From a cached config file, refreshed every 60 seconds |
| Changes reach SDKs in real time | Streamed within a second, polling as a fallback | SDKs poll; push needs the self-hosted ConfigCat Proxy |
| OpenFeature providers | Node, browser, Python, Go and Java | Over a dozen languages, including Go, Java, .NET, Node and Python |
| Approval before a change goes live | Every plan, the free one too; Production requires one by default | Approval flow for flag changes; plans not published |
| Audit log | Every plan, the free one too | Every plan; 7 days on Free, longer on paid plans |
| Pauses a rollout when metrics go bad | Release Watch on Team and Business reads Datadog, Prometheus, New Relic or Sentry | No automatic rollback |
| MCP server for AI agents | Hosted; agents can request Production changes, never approve them | Local, using Management API credentials |
| Data stored in the EU | Always: stored in the EU (Amsterdam) | EU infrastructure, with an EU-only CDN option |
| Self-hosting | Hosted only | On-premise plan, quoted |
| Built-in experiment statistics | Consistent assignment; analysis in your own analytics tool | Analysis in Amplitude or Mixpanel |
| Mobile SDKs | Not yet | iOS, Android, Flutter, Kotlin Multiplatform, Unity and more |
Checked against ConfigCat's public pricing and documentation on 19 November 2026 (see their pricing). Vendors change quickly. If a row above is out of date, tell us and we will correct it.
When ConfigCat is the better choice
- You need SDKs Railflag doesn't have. ConfigCat covers over 20 platforms, including iOS, Android, Flutter, Unity and Unreal. Railflag covers Node, the browser, Python, Go and Java.
- You only need a few flags. ConfigCat's free plan has unlimited seats and 10 flags, which suits small projects well.
- You need a long-established vendor with an SLA up to 99.99% and on-premise as an option.
When Railflag is the better choice
- Changes must land everywhere at once. Railflag streams changes within a second. ConfigCat SDKs poll a cached config, every 60 seconds by default; push needs its self-hosted proxy. For a kill switch, that minute matters.
- You want rollouts watched. Release Watch reads Datadog, Prometheus, New Relic or Sentry during a rollout and pauses it when error rates or latency drift. ConfigCat has no automatic rollback.
- Production needs a reviewer. Approvals are on every Railflag plan, with Production requiring one by default, and AI agents can request changes but never approve them.
- You want a richer free plan. Railflag's Starter has no flag limit and 3 environments.
Moving from ConfigCat
Railflag's automated migration supports AB Tasty and Unleash today, not ConfigCat. A move from ConfigCat is done by hand or with our engineers, and the order matters:
- Put flag checks behind OpenFeature while still on ConfigCat, using its OpenFeature provider. After that, switching is a provider change. See the OpenFeature guide.
- Clean up first. Remove flags that have been fully on or off for weeks.
- Recreate configs as Railflag projects and environments. ConfigCat targeting rules on user attributes map to Railflag rules on context attributes.
- Treat percentage rollouts separately. Every platform hashes users differently, so a 30% rollout reaches a different 30% after the move.
- Switch one service and one environment at a time, Staging first.
Want help? Assisted migration is a one-off €4,900, credited in full against your first year of Business; choose "Something else" as your current tool.
Frequently asked questions
- Can Railflag import my flags from ConfigCat automatically?
- Not yet. Railflag's automated migration supports AB Tasty and Unleash today. Moving from ConfigCat is a manual or assisted process.
- Is Railflag cheaper than ConfigCat?
- Not always. ConfigCat's paid plans start lower. Railflag includes approvals, real-time streaming and, on Team, Release Watch. Compare with your own numbers on both pricing pages.
- How fast do flag changes reach my servers?
- With Railflag, within a second over a streamed connection, with polling as a fallback. ConfigCat SDKs refresh on a polling interval, 60 seconds by default.
- Do I have to change the code that checks flags?
- If your code calls flags through OpenFeature, only the provider changes. If it calls the ConfigCat SDK directly, moving to OpenFeature first lets you switch later without touching call sites again.
Try Railflag next to ConfigCat
Start free, point one service's OpenFeature provider at Railflag in Staging, and compare.
Start for free