Acme — production
Client vault
- Items
- 48 items
- Members
- 1 member
AES-256-GCM
Solo Professional plan · one person
A DevOps vault for one.
The machine secrets, credential checks and project tools that teams use, set up for one person. Keep each client’s credentials apart, hand secrets to your pipelines and find out when a stored credential stops working.
pulsvault.com/console/vaults
Vaults
New vaultGlobex — staging
Client vault
- Items
- 31 items
- Members
- 1 member
AES-256-GCM
Initech — infra
Client vault
- Items
- 22 items
- Members
- 1 member
AES-256-GCM
Personal
PrimaryPrivate vault
- Items
- 64 items
- Members
- 1 member
AES-256-GCM
- Who it is for
- One person
- Price
- Storage
- Free trial
You are the engineer and the security team
Working alone does not make the risk smaller. These are the three things the Solo Professional plan is built to cover.
Keep clients apart
One vault per engagement, each with its own key, and a namespace per environment for the secrets your pipelines read.
Hear about a broken key first
Set up a check for a stored credential and PulsVault tries it on a schedule, then alerts you when it stops authenticating.
Run it like a small team does
Projects with ticket keys, a Security Calendar and earlier versions of your secrets — set up for one person.
DevOps secrets
Secrets for your pipelines, without the .env file
The machine plane runs beside your vaults. It is its own boundary: secrets are encrypted at rest and decrypted by PulsVault’s servers when an authorised key reads them, which is what lets a pipeline use them.
Terminal
# See which variables a namespace would inject — names only, nothing runs
pulsvault run -n acme/production/api --dry-run
# Start your app with those secrets in its environment
pulsvault run -n acme/production/api -- npm startA namespace per environment
Keep production, staging and shared secrets apart and address each one by path, the way your code already thinks about them.
A key for each pipeline
Give every pipeline its own machine key and limit it to the paths it needs. Revoke one key without touching the others.
- Secret reads per minute, one key
- Secret reads per minute, all keys
CLI, GitHub Actions and GitLab CI
Read secrets with the pulsvault CLI or the CI integrations, so values reach a job without a .env file in your repository.
See what read what
Each machine key’s reads and writes are recorded, so you can tell which key touched which path and when.
- Machine activity kept
Credential validation
Find out when a stored credential stops working
A secret store tells you what you saved. A check you set up tries a credential on a schedule and tells you when it stops authenticating. Checks are yours to configure, and they reach services that are open to the public internet.
pulsvault validate … && ./deploy.sh acts on them. Checks you set up
Choose a stored credential, a probe and a schedule. PulsVault tries the credential and records whether it still authenticates.
- Fastest schedule
- Results kept
An alert when one fails
Send a failing check to Slack or email, and see which channel received each notification, so a revoked credential is not first found in production.
A fresh check after a new version
Writing a new version of a secret can queue a check straight away, so a bad value shows up before the next scheduled run.
Reuse the latest result in CI
A pipeline can read the most recent result of a check instead of probing again, so a busy deploy day does not add traffic to your provider.
Undo a bad change to a secret
Overwriting the wrong value should not be a bad afternoon. Earlier versions stay, and a restore shows what it will change before it changes anything.
Earlier versions stay
Every write adds a version of the secret, and earlier ones stay available up to your plan’s limit.
- Versions kept per secret
Compare, preview, then restore
Compare a path at two points in time, review exactly what a restore would change, and apply it only when you are happy with it.
Projects and tasks, next to the secrets
Keep the work about a credential beside the credential. Tasks are created by you and carry a ticket key; nothing is raised or resolved on its own.
Example tickets, shown for illustration.
Projects with ticket keys
Group work under a project and every task gets a key such as ACME-7, so you can refer to it in a commit or a message.
Tasks that point at the thing itself
Attach a task to a vault, an item or a note and choose what is to be done to it: update it, rotate it or archive it.
A board for your own work
Statuses, priorities and due dates for what you do alone. Assigning work to other people starts on the Team plan.
Security Calendar
The dates that can hurt you, on one timeline
Keys expire, access lapses and devices stop being trusted without a sound. The Security Calendar gathers those dates, counts what is due in the next 7, 30 and 90 days and marks what is close. It comes with the Solo Professional plan and above.
Deadlines in one view
Expiring keys and credentials, policy end dates and device deadlines on one calendar, grouped by how soon they fall.
Your own dates alongside
Add your own events and see your task deadlines next to the generated ones, so a renewal and a delivery date sit together.
What starts when there are two of you
Solo Professional is built for one person. Working with other people is what the Team plan adds, and everything you have stored comes with you.
Other people in your projects
Project members, and tasks you can assign to someone else.
Approvals before a change
A task can wait for sign-off before its action is applied.
Grants on a namespace
Give a person or a team read access to part of your secrets.
Roles you design
Custom roles for the people you add.
Reports across the team
An audit export and the organization’s Security Center.
Where Solo Professional sits
Each plan keeps what the one before it has.
| Capability | Premium | Solo Professional | Team |
|---|---|---|---|
| DevOps secrets and the CLI | |||
| Credential validation | |||
| Fastest validation schedule | |||
| Validation results kept | |||
| Versions kept per secret | |||
| Secret reads per minute, all keys | |||
| Projects, tasks and the Security Calendar | |||
| Assigning tasks to other people | |||
| Project members | |||
| Namespace grants | |||
| Custom roles | |||
| Storage (per seat on Team) |