Skip to main content
A secret in Infisical is only useful once it reaches the process that reads it. There are three types of integrations for delivering secrets, each with its own setup process:
  • Frameworks: your application fetches its secrets from Infisical with the Infisical SDK or CLI
  • Infrastructure: the platform that runs your workload fetches the secrets and hands them to your application
  • Secret Syncs: Infisical copies secrets into a third-party store, such as AWS Secrets Manager or GitHub
Search all integrations to find the one for your use case:

​
Frameworks

A framework integration puts the Infisical SDK or CLI inside your application. The application authenticates with a machine identity, fetches its secrets at startup, and holds them in memory. No secrets land on disk, and any secrets that get rotated will reach the application the next time it starts. Pick a framework integration when you control the application code and want the shortest path between Infisical and your process.

​
Infrastructure

An infrastructure integration moves the fetch one layer out, into whatever runs your workload. That layer authenticates with a machine identity, fetches the secrets, and hands them to your application in a form it already reads, such as environment variables, a file on disk, or the platform’s own secret object. Pick an infrastructure integration when the application code carries no Infisical client, or when you can’t change that code at all.

​
Secret Syncs

A Secret Sync copies secrets from an Infisical project into a third-party store such as AWS Secrets Manager, GitHub, or Vercel. The sync runs over an App Connection, and any changes you make to secrets in Infisical will automatically propagate to the integration. Pick a Secret Sync when your platform reads from its own secret store, or when you’re migrating to Infisical and the old store has to stay populated in the meantime.