Fully Managed Infisical
as a Service

Deploy Infisical as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Infisical is an open-source secrets management platform. It stores API keys, database credentials and certificates in one encrypted place, with per-environment access control and a record of every read. It replaces scattered .env files and per-cloud secret stores, combining the convenience of a hosted secrets service with the control of software you own.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

Infisical

Infisical

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Infisical Preview Image

ABOUT THE SOFTWARE

What is Infisical

Infisical is an open-source platform for storing and distributing secrets. API keys, database credentials, tokens and certificates live in one encrypted store, organised by project and environment, and reach applications through a command line tool, an operator or an SDK instead of a file.

The project is published by Infisical Inc., a company based in San Francisco that went through Y Combinator's W23 batch and announced a 16 million dollar Series A led by Elad Gil in June 2025. The core is licensed under MIT at the repository root, with a separate licence covering the enterprise directory inside the codebase. That split matters in practice, because a handful of features that look available in the interface only work with a licence key from the vendor.

It is written mainly in TypeScript, with Go used for the command line tool and the Kubernetes operator. Running it needs two dependencies, PostgreSQL for storage and Redis for caching and scheduled jobs, and the application refuses to start without a Redis connection string. There are SDKs for nine languages and more than one hundred integrations into build, deployment and cloud tooling. Hugging Face and Airbyte have both published accounts of running it.

FEATURES

What Infisical does

These are capabilities of the software itself, not of our platform. Some of them sit behind the upstream project's enterprise licence and stay switched off until you hold a key from the vendor. The FAQ below names exactly which ones.

Secrets management

Store API keys, database credentials and tokens in projects, environments and folders. Reference one secret from another so a shared value is defined once and inherited everywhere it is needed.

Machine identities

Workloads authenticate using Kubernetes, AWS, Azure, GCP or OIDC identity rather than a token you have to distribute. Each identity gets its own permissions, time to live and IP restrictions.

Command line injection

The command line tool injects secrets straight into a running process. Nothing is written to a .env file on the developer's laptop, which removes the most common way credentials end up in a repository.

Kubernetes operator

An operator and a CSI driver push secrets into cluster workloads and resync on a fixed interval. There is also a provider for the External Secrets Operator if that is already in your cluster.

Secret scanning

Scans files, directories and git history for more than 140 secret types. Run it against a repository before a migration to find what has already leaked, then rotate those values first.

Private certificate authority

Issue and manage X.509 certificates from an internal or an external certificate authority, with ACME and EST enrolment, revocation lists, and an inventory of what is live and what is expiring.

SSH certificates

Sign short-lived SSH certificates instead of distributing long-lived public keys. Access expires on its own schedule rather than depending on somebody remembering to remove a key from a server.

Key management and integrations

A key management service with customer-managed keys and external key backends, a Terraform provider, SDKs for nine languages, and more than one hundred integrations into build and deployment tooling.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to Infisical the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Infisical

IBM completed its acquisition of HashiCorp in February 2025. Vault's source code had already moved to the Business Source Licence in August 2023, and HCP Vault Secrets reached end of sale in June 2025. Teams that had standardised on it went looking for somewhere else to keep their secrets.

Most of them find Infisical quickly, and then discover that running a secrets store is not the same shape of job as running a wiki. The application is one of three moving parts. PostgreSQL holds the data, Redis handles caching and scheduled work, and all three need patching, backup and a restore path that somebody has actually tested. Each one is a place where an upgrade can go wrong at the worst possible time.

The specific failure mode that catches people is the encryption key. Infisical encrypts every secret with a key that lives outside the database, in the environment. If that key is lost, a database backup restores ciphertext and nothing else. There is no recovery path, no support ticket that fixes it, and no vendor who can decrypt it for you. Teams that back up the database nightly and never think about the key are one host rebuild away from losing every credential they own.


REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Infisical on DANIAN

Three shapes we see repeatedly. The pattern underneath is the same one every time: credentials that used to live in a shared file, a chat thread or a password manager get a boundary, an identity and a record of who read them.

12-PERSON SAAS ENGINEERING TEAM

Retiring a shared password manager vault for pipeline credentials

Runs one instance in the region closest to its cluster, with four environments and a separate machine identity per build runner. The Kubernetes operator feeds the staging and production clusters. Developers pull values through the command line tool, so no .env file exists on a laptop.

6-PERSON AGENCY MANAGING CLIENT STACKS

One project per client, so an offboarding is one revocation

Nine client projects on a single instance, each with its own environments and pipeline identity. Client credentials never share a boundary. When a contractor rolls off, the identity is revoked once instead of chasing checked-in secrets across nine separate repositories.

4-PERSON DATA PLATFORM TEAM

Moving model provider keys off a shared spreadsheet

Instance in an Asian region close to the training cluster. Provider API keys are injected into jobs through the command line tool rather than baked into images. The Terraform provider keeps the same values out of state files during infrastructure runs.

COMPARISON

Four ways to run Infisical

There are four honest paths to a working secrets store. The costs below are monthly and include the time each path takes from someone on your team, priced at freelance sysadmin rates. Infisical's open-source core does not charge per seat, which is what makes the last row flat.

Path1 user5 users10 usersYour time each month
Doppler Proprietary hosted secrets manager. No self-host option.Free free tier covers up to 3 users$105 $21 per user$210 $21 per userNone this is what you pay for
Self-host on a VPS Production-class 2 vCPU / 4 GB VPS at about $24, plus backup storage and monitoring.$44 infrastructure, plus 60 to 240 euro of your time the same at 1, 5 or 10 users; seats are not the cost driver here1 to 2 hours plus 5 to 10 hours to build it
Home server Synology DS923+ at about 650 euro over 36 months, electricity, business line, off-site backup target.210 to 667 euro effective hardware amortised, power, uplink, off-site backup and your time2 to 4 hours and you are the on-call rota
DANIAN managed Infisical One instance, any number of users, in the region you pick.9 EUR9 EUR9 EURNone

Two things worth saying plainly. Doppler's free tier genuinely covers a team of three, so at that size the honest answer is that it costs nothing and works well. And the self-hosted paths give you physical control of the encryption key, which some teams need and will not trade away. What they do not give you is somebody else carrying the restore path.

BY INDUSTRY

Infisical for specific industries

Secrets management looks different depending on what those secrets reach. A payments team cares about key length and rotation overlap. An agency cares about tenant separation. The four below are the ones where the configuration choices are genuinely different, not just the wording.

A product team shipping to production several times a day carries one credential set per environment, plus a set for every pipeline. Short-lived credentials are the operational standard here, and NIST SP 800-57 key management guidance treats rotation interval as a property of the key, not of the calendar. We give each deployment pipeline its own machine identity rather than a shared token, so revoking a compromised runner does not take the other pipelines down with it. A typical shape is four environments, development through production, with a separate identity for the build runner in each. The access record shows which identity read which secret and when, which is what you need at three in the morning when a key turns up somewhere it should not be.

Payments engineering teams hold database credentials, provider API keys, and signing material that cannot sit in a repository or a shared vault file. Infisical supports FIPS 140-3 deployment, which requires the instance encryption key to be a 256-bit base64 value rather than the shorter default. We generate keys to that specification on request and record which mode an instance was built in, because retrofitting it later means re-encrypting everything. Secrets are held with AES-256-GCM and 96-bit nonces. A common workflow is rotating the production database credential on a fixed interval while the previous credential stays valid through a short overlap window, so connections drain instead of failing. That overlap is configurable per rotation and is the difference between a rotation and an outage.

An agency holds credentials that belong to other people. The operational standard is separation: one client must never be one misconfiguration away from another client's keys. Infisical projects give each client their own boundary, with environments underneath and a machine identity per client pipeline. We set the trusted proxy range on every instance we run, because the upstream default accepts any forwarded IP header and makes an IP allowlist trivially spoofable. A ten-client agency typically runs ten projects and thirty environments on one instance at the same flat price, since the open-source core does not charge per seat. Offboarding a contractor becomes one revocation rather than a hunt through ten client repositories for a checked-in .env file.

Model and data teams accumulate provider API keys faster than anyone else, and those keys are usually worth real money per call. Infisical publishes SDKs for nine languages and integrates with the tooling these teams already run, including a Kubernetes operator, a Terraform provider, and a command line tool that injects secrets into a process without writing them to disk. Hugging Face and Airbyte both run Infisical and have described the same pattern publicly: the command line tool removes local .env files, and the Kubernetes operator propagates changes into running workloads. The operator resyncs every sixty seconds by default. Notebooks and training jobs read the injected values at process start, so a rotation reaches them on the next run rather than mid-job.

FAQ

Frequently asked questions

Three groups of questions. The first covers how Infisical behaves in production and what we change from the defaults. The second covers getting your existing secrets in. The third covers billing, support and how the platform works underneath.

01

Technical and configuration

Infisical encrypts every secret with a key held outside the database. A database backup on its own restores ciphertext and nothing readable. We store the encryption key and the auth secret separately from the database, and we back both up on their own schedule. That separation is the whole reason a restore works.
Yes. It needs PostgreSQL for storage and Redis for caching and scheduled jobs. The application will not start without a Redis connection string. We provision, tune, patch, and back up both alongside your instance, and they are covered by the same flat price.
Single sign-on through SAML, OIDC, LDAP and SCIM, secret rotation, point-in-time recovery, dynamic secrets, approval workflows, and KMIP all live in the upstream project's enterprise directory. They stay switched off unless you hold a licence from the software vendor. Send us your licence key and we will wire it in.
No, and the interface does not make that obvious. On an unlicensed instance the rotation screen accepts your configuration and reports success, but nothing actually rotates. We flag this during onboarding so that nobody finds out during an incident. It is the single most common surprise with this application.
Secrets are held with AES-256-GCM using 96-bit nonces at rest, and TLS in transit. A layered key hierarchy sits underneath, with a root key that can be sealed by an external key management service or a hardware security module on instances that need it.
Yes. Machine identities support Kubernetes, AWS, Azure, GCP and OIDC authentication, so a workload proves who it is using the platform it already runs on. Static service tokens and API keys were deprecated upstream in favour of this, which removes the shared secret you would otherwise have to protect.
The operator resyncs every sixty seconds by default. Applications that read environment variables once at startup still need a restart to pick up a change. We tune the interval and set up the reload behaviour with you, because the right answer depends on how your workloads are written.
Yes. It scans files, directories and git history for more than 140 secret types. The scan size ceiling and the clone timeout are both configurable. We raise them when a repository is large enough to trip the defaults, which happens more often than you would expect on monorepos.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Yes. Infisical ships a migration path for Vault that carries key-value data across, alongside a one-time organisation-wide import. Kubernetes authentication shapes and policies are translated as part of the move rather than rebuilt by hand. It is the best-supported import path in the application.
Yes. The same migration tooling connects to Doppler and carries projects and configs across, including both root and branch configs, into matching Infisical projects and environments. You verify the mapping before anything is written.
Yes. Send us the hostname you want and we will tell you the exact records to add. We issue and renew the certificate. If your registrar is awkward, we will work through it with you on chat rather than leaving you to guess.

03

Billing, support and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Infisical for 7 days

No card. Cancel from the dashboard.