Infisical Self-Hosted

Self-hosted secrets-management platform with application and machine-identity access workflows.

9 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 →

Infisical v0.167.13 delegated-token authorization hardening

Infisical now enforces delegated OAuth-token scopes ahead of role-only administration checks and denies approval, rejection and bypass operations.

Scope: Delegated OAuth tokens and workspace listing; no complete affected-version range was published.

Scope-narrowed delegated tokens and automation using administration or workspace-list operations are affected; some calls may newly return 403.

Action: Upgrade to v0.167.13 or later and retest least-privilege delegated automation.

Primary source · v0.167.13 release · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Official AWS ECS/Fargate and Google GKE deployment guides, or a Vultr Docker Compose guide; configure PostgreSQL, Redis, TLS and encryption keys.

  2. Operated by

    Your team

    Customer owns the AWS account, Google project or Vultr instance and manages application identity, encryption keys, database recovery and upgrades. Providers operate selected managed infrastructure services.

Deployment boundaries by provider

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

Install methodOfficial AWS ECS/Fargate and Google GKE deployment guides, or a Vultr Docker Compose guide; configure PostgreSQL, Redis, TLS and encryption keys.
InfrastructureServers / containers
Persistent application containers with PostgreSQL, Redis and cloud networking/secrets services. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.
Licensing modelOpen Source / Open Core
The repository licenses code outside ee directories under MIT, enterprise directories under their own license and incorporated third-party components under their original terms. Paid enterprise entitlements must be checked separately.
LicenseMIT core outside enterprise directories; enterprise features and third-party components have separate terms.

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.

7 of 12 fields researched (58%) · 6 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The detailed SSO guide explicitly includes free Google/GitHub login on self-hosted instances. SAML and OIDC require a self-hosted Enterprise licence, with organization email-domain verification and provider configuration. The Enterprise guide explains licence activation; Cloud Pro prices do not establish a self-hosted quote or SCIM entitlement.

Explicit self-hosted protocol/edition boundary; resolves the earlier Cloud-matrix-only question · Source ↗ · Published v0.167.13 SSO guide ↗ · Self-hosted Enterprise licence activation ↗ · Reviewed 2026-11-20

Edition-dependent · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

The pricing page advertises Enterprise SCIM, but explicitly separates self-hosted pricing from Cloud. This pass did not establish the exact self-hosted license and provisioning entitlement; obtain the deployment-specific matrix.

Self-hosted commercial scope unresolved; Cloud tier names are not a substitute · Source ↗ · Reviewed 2026-11-14

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

v0.167.13 denies delegated OAuth-token approval, rejection and bypass operations, enforces scope checks ahead of role-only administration checks and adds an organization-permission check to workspace listing. Retest delegated automation.

Infisical delegated OAuth tokens; the vendor did not publish a complete affected-version range · Source ↗ · v0.167.13 release ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

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

The official self-hosting guide documents Compose with PostgreSQL and Redis. Configure the required encryption/authentication secrets, persistence and HTTPS; commercial features require their own license entitlement.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

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

The small-deployment guide specifies at least two application instances, each 2 CPU cores/4 GB RAM, plus PostgreSQL at 2 vCPU/8 GB/100 GB disk and Redis at 2 vCPU/4 GB/30 GB SSD. Redis is a persistent required datastore, not a disposable cache. These component baselines need additional replication/storage planning for your throughput, audit retention and HA targets.

Current self-hosted application, PostgreSQL and Redis resource guidance; not a total operating-cost estimate · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The pricing FAQ explicitly says self-hosted pricing differs from Infisical Cloud and directs buyers to contact the vendor. Public Cloud per-identity prices must not be used as a self-hosted quote.

Vendor self-hosted pricing policy; no infrastructure or labor estimate · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

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

Infisical v0.167.13 was published November 19, 2026. It tightens delegated OAuth-token authorization and may cause formerly accepted scope-narrowed administration calls to return 403.

Upstream Infisical self-hosted release; cloud packages and commercial editions may differ · Source ↗ · Prior reviewed release context ↗ · Authorization change ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (5 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
Compliance attestations
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

Review used upstream 0.167.10. Vendor AWS/GCP examples contain older version placeholders; pin a current compatible image/chart and use the complete installation steps, not the abbreviated infrastructure snippets alone. Preserve encryption keys independently of database backups. Configure telemetry, mail and external secret/infrastructure connections for the intended boundary. Infisical Cloud and agent-only integrations are separate. Infisical v0.167.13 tightens delegated OAuth-token authorization: scope-narrowed tokens no longer pass role-only administration checks, approval/rejection/bypass operations are denied, and workspace listing checks organization permission. Previously accepted delegated-token calls may return 403; retest automation with least-privilege scopes.

Community & maintenance

Upstream has sustained participation from multiple substantive contributors and frequent maintained releases, including 0.167.10 on the review date. This is a maintained community/commercial project, not a configuration-only Terraform provider.

Category fit

Identity & access management
Centralizes application secrets and related access/configuration workflows. Certificate, privileged-access and enterprise features depend on the licensed edition and selected components.

Compare within Identity & access management

  • authentikIdentity provider for centralized authentication and access policies across connected applications.
    • AWS
    Customer-operated · Open Source / Open Core
  • FusionAuth Self-HostedProprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Render
    Customer-operated · Commercial Only
  • 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
  • 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.

    • Vendor ECS/Fargate installation in the customer AWS account ↗ · AWS

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

      Includes application task definition and service creation, RDS PostgreSQL, ElastiCache, load balancing, IAM/secrets and upgrade steps. The optional Terraform/CloudFormation summaries are incomplete examples. Use current pinned application versions and review networking, database transport and credentials.

    • Vendor GKE installation in the customer Google Cloud project ↗ · Google Cloud

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

      Provisions GKE, Cloud SQL and Memorystore and installs the application Helm release in the operator project. Review supported chart/image versions, VPC access, TLS, key backup and database migrations. This is an application deployment, distinct from connecting Infisical to Google secrets APIs.

    • Vultr application deployment with Docker Compose ↗ · Vultr

      Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

      Provider instructions install the application, PostgreSQL, Redis and TLS proxy on an operator-controlled Ubuntu server. Customer manages OS, application updates and data/key recovery; generic cloud integrations are not additional hosting evidence.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory