Passwords
An encrypted team vault on your own instance
Deploy Psono with managed Postgres, email, and a public HTTPS URL. Server keys are generated for this instance. You pay for compute — not per seat.
TemplatesPsono
What you get
A private Psono, packaged to ship
End-to-end encrypted secrets on your instance — Postgres, email, unique server keys, and the public URL are wired at deploy.
Encrypted secrets
Passwords and files are stored encrypted. Sharing and the admin portal stay on this instance.
First admin by registration
Create the first account on the web client. That registration is the admin. Keys are already generated.
One hostname, three paths
The web client is at /, the admin portal at /portal, and the API at /server.
Email included
The Email add-on is part of the template so activation mail can send.
Managed Postgres
The server database lives in CloudNativePG. You do not add a database yourself.
Keys that stay put
The six server keys are generated once per deploy and do not change for the life of the instance.
See Psono in action
Deploy in seconds
One click. Postgres, email, and keys pre-wired.
Pick the Psono template. StackBlaze creates the app, Postgres, and email, generates the server keys, and gives you a hostname.
This stack
Web
Psono server
PostgreSQL
managed database · TCP:5432
platform SMTP when the pipeline has mail
- Stack
- Psono + PostgreSQL + Email
- First login
- Register the first admin on the web client
- Paths
- / client, /portal admin, /server API
After you deploy
- 1
Open the public URL
The hostname is on the app page after deploy. The web client is at the root.
- 2
Register the admin
Create the first account. Use an email address that can receive the activation message.
- 3
Open the portal when you need it
Administration is at /portal on the same hostname. Large file storage is a separate fileserver and is not part of this template.
Running Psono on StackBlaze
How the instance is wired
Psono, Postgres, and email ship together. Server keys are unique to this deploy. The public hostname serves the client, the portal, and the API.
Postgres holds the server data
Accounts and encrypted payloads live in the attached database. Restart the app and the vault is still there.
Keys are generated once
PSONO_SECRET_KEY and the related keys are created at deploy and persisted. Do not rotate them casually — clients depend on them.
Three paths, one hostname
Users open /. Admins open /portal. The API is /server. A custom domain replaces the hostname for all three.
Fileserver is separate
This template does not include the optional file repository. Large-file storage needs its own deployment.
Compare
Psono on StackBlaze vs a hosted password manager
| Feature | Psono on StackBlaze | Hosted password manager |
|---|---|---|
| Data location | Encrypted secrets live on your StackBlaze instance. | Secrets live in vendor-operated infrastructure. |
| Install model | One-click template. First admin registers on the public URL. | Create a vendor account and use their shared platform. |
| Keys | Server keys are unique to this instance and stay with it. | The vendor holds the platform keys. |
| Operations | You control updates, scale, backups, and the instance lifecycle. | The vendor operates the platform and the limits. |
| Billing | Compute, storage, and bandwidth. No per-seat fee. | Usually priced per seat or per plan. |
This template is Psono plus Postgres and email. Server keys are generated per deploy. The first admin registers on the web client.
FAQ
Common questions
Open the public URL and register. That first account is the admin. Activation mail uses the Email add-on. Administration is at /portal.
Ready to deploy Psono?
One click. Dependencies pre-wired. No infrastructure to manage.