FusionAuth Self-Hosted

Proprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.

  • AWS
  • Azure
  • Google Cloud
  • DigitalOcean
  • Render
Customer-operated Servers / containers Commercial Only

7 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

FusionAuth 1.71.0 security and redirect configuration review

The release hardens SAML parsing and rejects redirect URLs containing fragments. It also adds an optional Enterprise passwordless-code rate limit.

Scope: FusionAuth 1.71.0 release notes; the vendor does not establish a complete affected-version range or CVE for every change.

Exposure depends on SAML/redirect configuration. The new Enterprise rate limit is disabled by default and applies to the documented FormField strategy.

Action: Remove fragments from registered redirects before upgrading, test SAML integrations and explicitly configure the paid rate limit if required. Recheck older provider packages.

Primary source · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    Vendor Kubernetes/Helm guides, DigitalOcean Kubernetes 1-Click package, or Render application/PostgreSQL blueprint; versions and production topology differ

  2. Operated by

    Your team

    Customer configures application releases, plan features, database/search, networking, TLS, secrets, backups and capacity. Kubernetes operations apply to cluster deployments; Render operates its platform while the customer configures the web service and managed database.

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.

    FusionAuth on Amazon EKS ↗ · Source checked 2026-11-18

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    FusionAuth on Azure AKS ↗ · Source checked 2026-11-18

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    FusionAuth on Google GKE ↗ · Source checked 2026-11-18

  • DigitalOcean: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    FusionAuth in customer DigitalOcean Kubernetes ↗ · Source checked 2026-11-18

  • Render: Customer platform workspace · Customer-operated

    Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.

    FusionAuth and PostgreSQL in customer Render ↗ · Source checked 2026-11-18

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVendor Kubernetes/Helm guides, DigitalOcean Kubernetes 1-Click package, or Render application/PostgreSQL blueprint; versions and production topology differ
InfrastructureServers / containers
FusionAuth uses provisioned application capacity and persistent database state. Kubernetes and Render have different platform-operation boundaries; the customer selects and configures the application and database deployment.
Licensing modelCommercial Only
FusionAuth is proprietary under its Customer License Agreement, including the no-cost Community plan; paid plan capabilities require corresponding entitlements.
LicenseFusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.

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.

12 of 12 fields researched (100%) · 9 documented · 3 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

DigitalOcean documents a FusionAuth Kubernetes 1-Click application, currently packaged as 1.53.3. That older package must not be presented as upstream 1.71.0. FusionAuth’s AWS Marketplace guide instead describes FusionAuth Cloud hosting; it is not the self-hosted EKS product.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · AWS offer is hosted FusionAuth Cloud ↗ · Vendor DigitalOcean package guide ↗ · Offer fusionauth ↗ — FusionAuth; Kubernetes 1-Click application; package 1.53.3 · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

The vendor’s AWS Marketplace subscription is FusionAuth Cloud. Its procurement terms do not establish commitment credit for a self-hosted licence. Confirm the selected self-hosted Enterprise order and buyer agreement separately.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · AWS commitment qualification is product/agreement-specific ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

Self-hosted FusionAuth provides SSO between applications through its own login/session system and OIDC/SAML integration. Distinguish FusionAuth acting as the application identity provider from connecting an external IdP, and confirm the selected plan’s optional features.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

SCIM 2.0 is an Enterprise-plan feature available from 1.36.0. FusionAuth acts as an inbound SCIM server for users/groups, with OAuth client credentials and configurable mappings. It is not a SCIM client provisioning other services; application registration remains separate.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

FusionAuth’s August 2025 announcement identifies AssurancePoint as its ISO 27001:2022 auditor. The current certificate/SOA and SOC 2 report remain request-gated, so their validity and self-hosted system boundary were not independently checked here. Its licence FAQ limits report access and requires Enterprise plus HA hosting for a BAA. Assess the actual report/customer controls; FIPS mode is explicitly not FIPS certification.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Licence and assurance FAQ ↗ · FIPS mode versus certification ↗ · Named auditor and original announcement ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

Enterprise self-hosted FIPS mode is available from 1.62.0 only for new installations and requires every node in the cluster to use that mode, with separately compliant database/search components. This is a scoped configuration feature, not FIPS certification. SSO, token and provisioning controls require explicit configuration.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · SCIM access control ↗ · Application SSO/session behavior ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation

Enterprise documents an air-gapped licence, offline key activation and an expiry without a grace period; network-backed features and update feeds need separate handling. The requirements also state Community can block outbound access without a paid licence. Choose the plan and disable or supply reachable dependencies explicitly.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Community versus paid-plan network requirements ↗ · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The vendor’s Render blueprint deploys FusionAuth and PostgreSQL into the customer’s Render account. The repository is a moving source, not an immutable image lockfile; fork/review it and select production capacity. EKS/AKS/GKE have separate production guides.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Deployment artifact ↗ (Moving repository default branch; reviewed 2026-11-18) · EKS deployment ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The application minimum is 512 MB RAM with 10–50 GB disk for application/log needs; database, operating system and optional search are additional. CPU depends on login rate and password hashing. Current releases bundle Java 25 and recommend tested PostgreSQL versions. Multiple app replicas and HA database/search require separate sizing.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

FusionAuth uses its proprietary Customer Licence Agreement, including the no-cost Community plan. Paid plan/MAU terms are separate; SCIM and the documented paid air-gap licence require Enterprise. Free Community is not an open-source software licence.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Self-hosting plan comparison ↗ · SCIM Enterprise entitlement ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Define monthly active users, peak logins/token operations, password-hash settings, identity/audit retention, database/search HA and selected paid features. One hundred internal users need not equal billable MAU, and 1 TB needs a database/log retention split. Include licences, backups, egress and operations.

Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput · Source ↗ · Current AWS Linux EC2 rates; workload/topology still required ↗ · Storage performance and charging inputs ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

FusionAuth 1.71.0 was released November 17, 2026. It includes security changes and rejects authorized redirect URLs containing fragments; test SAML and redirect configurations during upgrade. The DigitalOcean package remains 1.53.3 in the reviewed catalog.

FusionAuth Self-Hosted: selected customer-operated edition · Source ↗ · Separate DigitalOcean package version ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Scope & considerations

This is self-hosted FusionAuth, not FusionAuth Cloud. The AWS Marketplace guide sells hosted Cloud service; EKS remains a separately documented customer-hosted path. DigitalOcean’s 1-Click package is 1.53.3, distinct from upstream 1.71.0. SCIM and paid air-gap/FIPS options have Enterprise conditions; Render uses a customer-owned application/database blueprint.

Category fit

Identity & access management
Provides customer-operated authentication, authorization, user management and federation for applications.

Compare within Identity & access management

  • authentikIdentity provider for centralized authentication and access policies across connected applications.
    • AWS
    Customer-operated · Open Source / Open Core
  • HashiCorp Boundary EnterpriseCommercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Infisical Self-HostedSelf-hosted secrets-management platform with application and machine-identity access workflows.
    • AWS
    • Google Cloud
    • Vultr
    Customer-operated · Open Source / Open Core
  • Keycloak Self-HostedIdentity and access management for application sign-on, federation and authorization.
    • AWS
    • Azure
    Customer-operated · Open Source / Open Core
  • NetBird Self-Hosted Community EditionOpen-source zero-trust networking control plane self-hosted on a customer cloud VM.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • DigitalOcean
    • Hetzner
    Customer-operated · Open Source / Open Core
  • OpenBaoFoundation-governed secrets, key and certificate management with a customer-operated server.
    • Linode
    Customer-operated · Open Source / Open Core
  • OpenVPN Access ServerSelf-hosted business VPN and network-access server deployed in the customer's cloud account.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Teleport Enterprise Self-HostedCommercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only

Showing 8 of 10 other listings in Identity & access management. These products address related workflows; read their category-fit notes before comparing scope. See all of Identity & access management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • FusionAuth on Amazon EKS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      FusionAuth documents provisioning the cluster, database and full application in customer AWS infrastructure.

    • FusionAuth on Azure AKS ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      FusionAuth documents the full application on a customer AKS cluster and Azure database resources.

    • FusionAuth on Google GKE ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      FusionAuth documents the full application on customer GKE and Google Cloud database resources.

    • FusionAuth in customer DigitalOcean Kubernetes ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor and provider document a full FusionAuth 1-Click Kubernetes application. The provider catalog packages 1.53.3, older than the reviewed upstream release; validate upgrades and production database/HA design.

    • FusionAuth and PostgreSQL in customer Render ↗ · Render

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      FusionAuth provides a Render blueprint deploying the full application and PostgreSQL in the customer’s account/project. Production needs paid resource capacity and a deliberate database/backup design.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory