Unleash Self-Hosted
Feature management and controlled application rollouts in your own environment.
2 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official Docker/Compose deployment with PostgreSQL; choose the licensed edition.
Runs in
Documented customer environment
Customer-operated feature-management service, database and SDK integrations
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer operates the service and database and manages SDK credentials, availability and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Unleash self-hosting in a customer AWS account ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Docker/Compose deployment with PostgreSQL; choose the licensed edition. |
|---|---|
| Infrastructure | Servers / containers The documented self-hosted runtime uses an application server or container with persistent state services. Hosted vendor editions are outside this listing. |
| Licensing model | Open Source / Open Core AGPL-licensed Open Source is available alongside commercially licensed Enterprise capabilities. The entry covers both self-hosted edition choices. |
| License | AGPL-3.0 Open Source; Enterprise features require separate commercial licensing |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
The Enterprise SSO guide documents SAML 2.0 and OIDC, configured by an administrator with the selected IdP. Self-hosted Enterprise needs a valid licence key; core password login is a different path. Configure claim/account mapping and session policy; an IdP may not honor forced re-authentication requests identically.
Current self-hosted Enterprise user login, including documented v8.3 session qualifications · Source ↗ · Self-hosted Enterprise licence keys ↗ · Reviewed 2026-11-20
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The upstream Compose file supplies Unleash and PostgreSQL but explicitly restricts that recipe to demo, development and learning. It is not a production deployment recommendation.
Upstream development/demo Compose only · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The configuration guide suggests 0.5–1 vCPU and 512 MiB–1 GiB for an application container, plus a PostgreSQL starting point of 1 vCPU, 1 GiB RAM and 5 GiB SSD. Flags, SDK request rate, replicas, storage and database availability determine the real footprint; these small component baselines do not size a 1 TB HA deployment.
Current application/database starting allocations, not total production capacity · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed v8.3.1 upstream core is AGPLv3, so older Apache-2.0 descriptions must not be applied to this release. Self-hosted Enterprise requires a separate licence key with seat-count/expiration enforcement. Hosted pricing, Enterprise entitlements, support and your PostgreSQL/application infrastructure are separate.
Published application source licence and self-hosted Enterprise licensing · Source ↗ · Self-hosted Enterprise licence-key and seat rules ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was v8.3.1, published 2026-10-29. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream Unleash/unleash release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The self-hosted Open Source and Enterprise editions have different capabilities. Vendor-hosted Enterprise is a separate option. The installation guide documents version-check behavior and how to configure it; verify governance requirements against the selected edition.
Category fit
- Feature management
- Feature flags, activation strategies and controlled feature rollout using a self-hosted management service and SDKs.
Compare within Feature management
- Flagsmith Self-HostedFeature management platform for targeted rollouts and remotely configured application behavior.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- GrowthBook Self-HostedFeature flagging and experimentation platform with a self-operated application and SDKs.
- Railway
These products address related workflows; read their category-fit notes before comparing scope. See all of Feature management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Self-hosted deployment and database ↗docs.getunleash.io
- Feature platform and current open-source license ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Unleash self-hosting in a customer AWS account ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor describes self-hosting the full Unleash server in the customer AWS account, including ECS/Fargate, EC2, Elastic Beanstalk and EKS options. PostgreSQL, credentials, networking, backups and upgrades remain customer responsibilities; Unleash Cloud and Marketplace SaaS are separate options.
- Unleash self-hosting in a customer AWS account ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked