ConfigCat's hosted, download-priced flags against self-hosted Unleash: local evaluation in both, targeting and segments, what Unleash Open Source limits to 1 project and 2 environments, the AGPLv3 change and Unleash Edge end of life, and who runs the server.
ConfigCat against self-hosted Flagsmith: flags, remote config and segments, Flagsmith's open-source edition with no API request limits, the features that need Flagsmith Enterprise such as SAML and RBAC, and the Kubernetes and PostgreSQL work of running it.
Moving from ConfigCat to Unleash: listing products, configs and flags through the Public Management API, mapping targeting rules and percentage options to Unleash strategies, recreating environments, swapping SDKs and handling the users who are re-bucketed in partial rollouts.
Moving from ConfigCat to Flagsmith: exporting flag definitions through ConfigCat's API, recreating projects, environments, segments and remote config values in Flagsmith, swapping SDKs, and replacing the ConfigCat Proxy with Flagsmith's Edge Proxy where needed.
Cost of ownership by component: ConfigCat plans priced by config JSON downloads, flags and environments, from Forever Free to Dedicated, against self-hosted Flagsmith's free or Enterprise edition, Kubernetes and PostgreSQL, migration and the people who keep it running.
ConfigCat has no single bulk export, so flags leave through the Public Management API: what you can read (products, configs, environments, flags and targeting), handling rate limits, keeping the audit log within its retention window, and checking the export before the plan ends.
For teams that need flags inside their own network: ConfigCat's on-premise Docker service at a quoted flat price, or its Proxy in offline mode, against running open-source Unleash or Flagsmith, compared on licensing, updates, support and who holds the data.