Pricing
We count services and people — the things that grow with you. Variables and environments are never counted: a cap on the number of secrets pushes you to pack several values into one variable, which breaks per-key rotation and auditing. Paid plans are priced individually — the service is young, and we are still calibrating the price against how it gets used.
Free
0 ₽forever
Enough to run a real product with a production environment, not a toy.
- Projects
- 3
- Services
- 10
- Members
- 5
- Audit retention
- 7 days
- ·encryption, rotation and auditing without limits
- ·SDK, CLI and the CI action
- ·community support
Team
popularPrice on request
A team with several products and a production environment that matters.
- Projects
- 10
- Services
- 25
- Members
- 10
- Audit retention
- 90 days
- ·everything in Free
- ·project roles and invitations
- ·webhooks and notifications
- ·email support
Business
Price on request
When production access needs approving and the audit trail needs showing.
- Projects
- unlimited
- Services
- unlimited
- Members
- unlimited
- Audit retention
- 1 year
- ·everything in Team
- ·approval flows and break-glass
- ·mobile approvals and alerts
- ·response-time SLA
What no plan limits, including the free one
Variables and secrets
Charging per item would punish the right habit — one key, one secret. Hitting a cap, you would pack five values into one variable as a JSON blob, losing per-key rotation, restricted visibility and per-key auditing.
Environments
A cap on environments pushes people to keep staging and production in one. The product exists precisely to stop that happening, so charging for it would be odd.
Encryption, rotation and auditing
Envelope encryption, four-phase rotation and the hash-chained log work the same on every plan. Security is not a premium option.
Pricing questions
- What counts as a service?
- An application or worker that fetches secrets under its own machine identity. A service deployed across three environments is one service, not three.
- What happens when I hit a limit?
- Existing services keep receiving their secrets — we never cut off access to something already running. You cannot create another project or service, or invite another member, until you move up a plan.
- Why price on request instead of a public price list?
- Because we do not have an honest price list yet: the service is young, and what it actually costs to serve twenty-five services versus three is something we are learning alongside our first teams. Inventing a neat number and then changing it is the worst of the options.
- Why not charge per user, as everyone does?
- Secrets are needed by services; people mostly read the audit trail. Per-seat pricing makes you economise on observers — and observers are exactly who should be watching the log.