Compare Encore, AWS Secrets Manager, Google Secret Manager, Infisical, OpenBao, 1Password and SOPS as replacements for Doppler, by where the secrets live, how apps receive them and what local development looks like.

Doppler is a hosted secrets manager that teams adopt to get rid of .env files: projects and environments in a dashboard, doppler run -- npm start to inject values locally, and integrations that sync secrets into AWS, GCP, Vercel or GitHub Actions.
It gets harder to justify when the production values end up synced into AWS Secrets Manager anyway, so the same secret is managed in two places, or when security asks why credentials for your own cloud account are stored with another vendor.
The alternatives below are sorted by where the secrets live. For a broader comparison see best secrets management tools.
Encore brings infrastructure from code to TypeScript and Go backends, and secrets are part of that code: you declare secret("StripeKey") where it is used, and the compiler checks that every declared secret has a value before the app runs or deploys. Values are set per environment type with encore secret set or in the dashboard and stored encrypted. When you deploy to your own AWS or GCP account, Encore provisions a secrets manager in that account (AWS Secrets Manager on AWS), replicates the values to it, and gives each service access only to the secrets it uses. Per the secrets docs, encore run syncs local values to each developer's machine, and .secrets.local.cue overrides them on one machine.
The difference from Doppler is that there is no separate project tree to keep in sync with the code. The list of secrets is whatever the code declares, so a removed secret disappears from the checks and a new one fails the build until someone sets it.
Run in your terminal to get started locally.
// notify/email.ts
import { api } from "encore.dev/api";
import { secret } from "encore.dev/config";
const postmarkToken = secret("PostmarkToken");
export const sendWelcome = api(
{ expose: false },
async (p: { to: string }): Promise<void> => {
await fetch("https://api.postmarkapp.com/email", {
method: "POST",
headers: {
"X-Postmark-Server-Token": postmarkToken(),
"Content-Type": "application/json",
},
body: JSON.stringify({ From: "hello@example.com", To: p.to, Subject: "Welcome", TextBody: "Hi!" }),
});
},
);
Production values are not stored in the repository, so a coding agent working in the codebase cannot read or leak those values. A local override in .secrets.local.cue is readable if it is present. An agent that adds a new integration declares the secret in the same change for someone with access to fill in. Encore secrets cover the application's own credentials; they are not a general-purpose vault for people or for systems outside the app.
Best fit: TypeScript or Go backends that want the list of secrets defined by the code and the values stored in their own AWS or GCP account.
If Doppler is mostly syncing into AWS today, AWS Secrets Manager is the destination without the middle step. IAM controls which role reads which secret, CloudTrail audits every read, and rotation functions change RDS passwords on a schedule. ECS injects values as environment variables at container start, which means rotated values need a new deployment, as covered in environment variables vs a secrets manager. What it lacks is Doppler's developer experience: there is no doppler run equivalent for local development, so teams add their own scripts or keep separate development keys.
Best fit: AWS-only teams that want secrets under the same IAM and audit as the rest of the account.
The GCP equivalent: versioned secrets per project, IAM bindings per secret, audit logs, and Cloud Run can expose a secret as an environment variable or a mounted file, as shown in Google Secret Manager on Cloud Run. Like AWS, local development is left to you.
Best fit: GCP teams that want secrets in the same project and IAM model as their services.
InfisicalInfisical is the closest match to Doppler's workflow: projects and environments in a dashboard, a CLI that injects values (infisical run -- npm run dev), secret versioning, rotation and a Kubernetes operator. The core is open source and can be self-hosted, which answers the "secrets live with a vendor" objection if you run it in your own account, at the cost of operating it.
Best fit: teams that like Doppler's dashboard and CLI but want an open source core or self-hosting.
OpenBaoOpenBao is the Linux Foundation fork of HashiCorp Vault's last open source release, started after HashiCorp moved its products to the Business Source License in August 2023, and it stays under MPL 2.0 with a largely compatible API. It does far more than Doppler, including dynamic database credentials, PKI and encryption as a service, and it needs a platform team to run with high availability, unsealing and backups.
Best fit: platform teams that need dynamic credentials across clouds and want an open source Vault.
Teams that already keep human credentials in 1Password can use service accounts and op run to inject values into processes, which keeps one tool for people and machines. SOPS goes the other way: it encrypts values in YAML, JSON or env files with age, PGP or a cloud KMS key, so encrypted secrets live in Git next to the code and there is no server at all, which suits GitOps setups with Flux or Argo CD.
Best fit: 1Password for teams standardized on it; SOPS for GitOps repositories that want no secrets service.
If Doppler mostly syncs into one cloud, move the source of truth to that cloud's manager and solve local development separately. If you want Doppler's workflow with self-hosting, Infisical is the closest. If you need dynamic credentials, OpenBao. If the secrets belong to a TypeScript or Go backend, Encore declares them in code and stores the values in your own AWS or GCP account, with local values synced for every developer.
For a backend on one cloud, that cloud's manager, AWS Secrets Manager or Google Secret Manager, keeps secrets in your own account under IAM. Encore declares secrets in code and stores production values in a secrets manager in your AWS or GCP account. Infisical is the closest product to Doppler, with a hosted or self-hosted dashboard. OpenBao suits platform teams that need dynamic credentials, 1Password fits teams that already use it, and SOPS keeps encrypted secrets in Git.
The common reasons are that production secrets live with a third-party SaaS rather than in the team's own cloud account, that values end up synced to AWS or GCP anyway, and that per-seat pricing grows with the team. Teams that already run on one cloud often consolidate on that cloud's secrets manager or on a tool that writes to it.
Deploy to your cloud on AWS and Google Cloud
without managing infrastructure
Encore lets developers and agents define application infrastructure directly in code, then automatically provisions it from local development to production in your AWS or GCP account.