Open Source Tggl Alternatives

Unleash separates deploying code from releasing a feature. A change can go to production switched off and be turned on when the team is ready, which retires the long-lived feature branch and the merge that comes with it.

Flags are evaluated by an SDK inside your application through a single function call, so the language you work in barely matters. Unleash supports 15 official client and server SDKs and more than 15 community ones, and writing your own is a documented option.

The self-hosted server covers the core of feature management, while several governance capabilities belong to the Enterprise edition.

• Flag evaluation: backend and frontend SDKs check state against the Unleash API at runtime.
• Testing in production: run new code against real production data without exposing every user to it.
• Parallel work: several features move at once without a branch per feature.
• Role-based access control: Enterprise adds rules for who may change which flags.
• Change requests: Enterprise gates flag changes behind review before they take effect.
• SSO and SCIM: Enterprise adds single sign-on and automatic user provisioning.

Getting started locally takes git and Docker. Clone the repository, bring the compose file up, and the interface answers on port 4242 with a default admin login. Running the source directly through Node.js is covered in the contributing guide.

For production, Unleash needs a persistent server, with deployment guides for Heroku and DigitalOcean and documentation on configuration options for anything more involved.

Flagsmith wraps a section of code in a flag so a feature can be switched on or off for different environments, users or user segments, without shipping new code to do it. It removes the deploy-to-change cycle that turns every small release decision into a full build.

The platform covers web, mobile and server side applications through SDKs for more than fifteen languages, among them TypeScript, .NET and Java, and it integrates with frameworks such as React and Next.js. A single Docker Compose file brings up the whole stack and bootstraps an admin user, an organization and a project on first run.

The feature set centers on controlling who sees what and when.

• Feature flags: release code behind a switch and toggle it remotely per environment.
• Segments: target beta testers or cohorts, then run A/B and multivariate tests against them.
• Remote configuration: change values in running applications without deploying again.
• Organization management: keep work in organizations, projects and roles for team members.
• Integrations: connect Flagsmith to the tools a team already uses.

Hosting runs on premise or in a private cloud, which keeps flag evaluation and user data inside your own network. Most of the platform is open source under the BSD 3-Clause license, with a few repositories under MIT, while enterprise governance features need a paid license. A hosted version exists for teams who would rather not run it themselves.

FeatBit separates deploying code from releasing features. Something ships dark, goes to one percent of users, expands as it holds, and switches off without a redeployment when it does not, all controlled by a simple if or else in your own code rather than a DevOps task.

Getting running takes a git clone and a docker compose up, after which the portal answers on port 8081. You then import an official SDK and call a variation function with a user object; the SDK returns that user's value and the code branches on it. SDKs cover .NET, JavaScript, React, Node.js, Java, Python, and Go, alongside OpenFeature providers.

Around the flags themselves sits the machinery a team needs.

• Targeting and segments: assign users to specific variations, or include and exclude them by attribute through reusable segments.
• Experimentation: run feature-level A/B tests anywhere in the stack and read usage insights during a rollout.
• Feature workflow: flag triggers, scheduled changes, and change approval requests automate how a flag moves.
• Access control: define access levels per project, environment, or team, with an audit log of flag changes.
• Integrations: webhooks reach DataDog, New Relic, Grafana, Growthbook, and Slack, while OpenTelemetry carries traces and metrics.
• Relay proxy: host a flag service in a customer's private environment or nearer end users.

Deployment runs from docker compose to Kubernetes manifests and Helm charts. FeatBit is open core: the bulk of the code is MIT, certain features need a valid license key, and a professional edition targets teams past millions of daily users.