Personal fleet
Use trusted-owner-ssh. Your laptop, desktop, server, NUC — all behind SSH trust you already manage.
env-sync gives you explicit control over how secrets are stored, transported, and who gets access. Pick the security model that fits your scenario.
| Dimension | dev-plaintext-http | trusted-owner-ssh | secure-peer |
|---|---|---|---|
| Storage | Plaintext | Plaintext (optional AGE) | AGE encrypted (mandatory) |
| Transport | HTTP | SCP / SSH | HTTPS + mTLS |
| Onboarding | Open — any peer on the network | Zero-touch if SSH access exists | Invitation + explicit approval |
| Authorization | None | Implicit via SSH trust | Explicit approved / revoked states |
| Best for | Local debugging only | All your own machines | Multiple owners sharing secrets |
Debug-only mode with no encryption at rest or in transit and no authentication. Use this exclusively for isolated local testing — never for real secrets.
env-sync mode set dev-plaintext-httpIdeal when every machine belongs to you. SSH provides encrypted transport and authentication automatically. Storage is plaintext by default because trust is already broad in this model; optional AGE encryption can be enabled for defense-in-depth.
env-sync mode set trusted-owner-sshDesigned for cross-owner collaboration. No shell access is shared between peers — mTLS handles authentication and AGE handles encryption at rest. Access requires an explicit invitation and approval step.
env-sync mode set secure-peerUse trusted-owner-ssh. Your laptop, desktop, server, NUC — all behind SSH trust you already manage.
Use secure-peer. Team members get secrets without SSH access to each other's machines.
Use dev-plaintext-http. Fast setup for throwaway testing — never store real credentials here.