1Password integration

[maelp]

What problem will this feature address?

Would be really cool if we could setup a 1Password integration with a token so that in environment variable we could use something like

AWS_ACCESS_KEY_ID="op://development/aws/Access Keys/access_key_id"
AWS_SECRET_ACCESS_KEY="op://development/aws/Access Keys/secret_access_key"

and have them automatically converted using op run

(see https://developer.1password.com/docs/cli/secrets-environment-variables/)

Describe the solution you'd like

Integrating 1Password

Describe alternatives you've considered

Not sure how to do it otherwise?

Additional context

No response

Will you send a PR to implement it?

Maybe, need help

[Paillat-dev]

Is it even possible to have onepassword in a production environment ? I don't see how that would make sense.

[maelp]

Of course :) there's 1Password cli with account token, it serves as a Secret Manager API, like any other (Google Secret Manager, etc)

You just define the secrets you want to allow access to on the token (eg "staging backend secret token") and then you can access them using 1Password cli, so you don't have to copy-paste them everywhere in config files, and if you change them in 1Password, they will be automatically updated next time you deploy

[Paillat-dev]

Well, as a 1password user myself, I didn't know that, but now I need it asap :p This seems really useful !

[maelp]

It is! That's why it would be lovely to make it accessible in Dokploy :)

[drag0n141]

Need that too. I use 1Password in my Kubernetes Cluster, and use it with Docker would be perfect.

[trylovetom]

passkey will be the better

[morindo]

It would be simple if we could use the Custom command feature in Dokploy.

We could run this simple command:

op run --env-file ./portal/app.env -- docker compose -p container-frw4ap -f ./portal/docker-compose.yaml up -d --build --remove-orphans

Unfortunatly by default, the command starts with docker.

[appscaptain]

Oh, yeah really missing this. Seems like an easy fix would to just allow the command to start with something else than always docker.

With the recent LiteLLM hacks on the 24th of March 2026 and all these AI leaks it really sucks having to keep .env files on your servers. Dokploy is really missing this feature.

[peter2meter]

Agreed this would make Dokploy more secure: no duplication of keys or having to keep them in sync. I've moved my teams to 1password to avoid hidden slack sharing of .env variables. Dokploy is the last remaining part that's not secure this way.