
# Identity & access management on Render

Compare documented Identity & access management deployments on Render, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/render/identity-access-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Render workspace, project and services; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://render.com/docs/deploys (checked 2026-11-20).
- Network: Private services with separately exposed public endpoints
- Identity and access: Workspace membership and deployment credentials
- Installation guidance: Deploy application services and databases using a Blueprint or Docker/source build; configure persistent disks, secrets and recovery.
- Guidance source: https://render.com/docs/deploys
- Guidance reviewed: 2026-11-12


### Private networking

Services in the same region can use Render private networking. Free web services can send but cannot receive private-network requests. Review the actual paid service and endpoint requirements.
Source: https://render.com/docs/private-network (reviewed 2026-11-14).

The listings below have evidence for Render. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## FusionAuth Self-Hosted

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

- Listing: https://launchinyourcloud.com/directory/fusionauth-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: FusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.
- Licensing model: commercial-only
- Installation: Vendor Kubernetes/Helm guides, DigitalOcean Kubernetes 1-Click package, or Render application/PostgreSQL blueprint; versions and production topology differ
- Architecture: FusionAuth application instances with a customer database and optional search, deployed on cloud Kubernetes or as a customer Render web service and PostgreSQL database.
- Operations: 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.
- Product website: https://fusionauth.io/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

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.

FusionAuth is proprietary under its Customer License Agreement, including the no-cost Community plan; paid plan capabilities require corresponding entitlements.

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.


### Category fit

- identity-access-management: Provides customer-operated authentication, authorization, user management and federation for applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/eks (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/aks (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/gke (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean (checked 2026-11-18). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/marketplaces/render (checked 2026-11-18). 


### Cloud deployment evidence

- FusionAuth on Amazon EKS (aws): https://fusionauth.io/docs/deploy/production/kubernetes/eks
  FusionAuth documents provisioning the cluster, database and full application in customer AWS infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth on Azure AKS (azure): https://fusionauth.io/docs/deploy/production/kubernetes/aks
  FusionAuth documents the full application on a customer AKS cluster and Azure database resources.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth on Google GKE (gcp): https://fusionauth.io/docs/deploy/production/kubernetes/gke
  FusionAuth documents the full application on customer GKE and Google Cloud database resources.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth in customer DigitalOcean Kubernetes (digitalocean): https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean
  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.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth and PostgreSQL in customer Render (render): https://fusionauth.io/docs/deploy/production/marketplaces/render
  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.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- FusionAuth on Kubernetes: https://fusionauth.io/docs/deploy/production/kubernetes/

- FusionAuth on Amazon EKS: https://fusionauth.io/docs/deploy/production/kubernetes/eks

- FusionAuth on Azure AKS: https://fusionauth.io/docs/deploy/production/kubernetes/aks

- FusionAuth on Google GKE: https://fusionauth.io/docs/deploy/production/kubernetes/gke

- FusionAuth license: https://fusionauth.io/license

- FusionAuth in customer DigitalOcean Kubernetes: https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean

- FusionAuth and PostgreSQL in customer Render: https://fusionauth.io/docs/deploy/production/marketplaces/render

### Licensing sources

- https://fusionauth.io/license

- https://fusionauth.io/docs/concepts/plans-and-limits/plans-features

### Infrastructure sources

- https://fusionauth.io/docs/deploy/production/kubernetes/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Edition-dependent. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/ (reviewed 2026-11-18). Supporting source: AWS offer is hosted FusionAuth Cloud — https://fusionauth.io/docs/deploy/production/marketplaces/aws. Supporting source: Vendor DigitalOcean package guide — https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean. Offer fusionauth: FusionAuth; Kubernetes 1-Click application; package 1.53.3; https://marketplace.digitalocean.com/apps/fusionauth.

- Cloud commitment eligibility: Sources checked — unresolved. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/marketplaces/aws (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/authentication/sessions/single-sign-on (reviewed 2026-11-18).

- SCIM provisioning: Edition-dependent. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/users/provision/scim (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://trust.fusionauth.io/?format=html (reviewed 2026-11-18). Supporting source: Licence and assurance FAQ — https://fusionauth.io/license-faq. Supporting source: FIPS mode versus certification — https://fusionauth.io/docs/security/compliance/. Supporting source: Named auditor and original announcement — https://fusionauth.io/blog/fusionauth-iso27001-2025.

- Security controls: Documented. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/security/compliance/ (reviewed 2026-11-18). Supporting source: SCIM access control — https://fusionauth.io/docs/users/provision/scim. Supporting source: Application SSO/session behavior — https://fusionauth.io/docs/authentication/sessions/single-sign-on.

- Air-gapped operation: Edition-dependent. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/install/air-gapping (reviewed 2026-11-18). Supporting source: Community versus paid-plan network requirements — https://fusionauth.io/docs/deploy/production/system-requirements.

- Deployment artifact / IaC: Documented. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/marketplaces/render (reviewed 2026-11-18). Deployment artifact: https://github.com/FusionAuth/fusionauth-render-blueprint. Artifact reference: Moving repository default branch; reviewed 2026-11-18. Supporting source: EKS deployment — https://fusionauth.io/docs/deploy/production/kubernetes/eks.

- Minimum footprint / sizing: Documented. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/system-requirements (reviewed 2026-11-18).

- License pricing: Documented. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/license (reviewed 2026-11-18). Supporting source: Self-hosting plan comparison — https://fusionauth.io/pricing?hosting=self-hosting&step=plan. Supporting source: SCIM Enterprise entitlement — https://fusionauth.io/docs/users/provision/scim.

- Operating cost estimate: Sources checked — unresolved. 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. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://fusionauth.io/docs/deploy/production/system-requirements (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. 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. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/release-notes (reviewed 2026-11-18). Supporting source: Separate DigitalOcean package version — https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- FusionAuth 1.71.0 security and redirect configuration review (security-advisory): 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. Conditions: 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. Source: https://fusionauth.io/docs/release-notes; reviewed 2026-11-18.



