For the week the quote lands

Before you sign the renewal.

A one-page brief for the engineering leader holding a quote that grew faster than the company did. Most of this works whoever you end up signing with.

Why the number movedBefore the callIf the fix is structural

Why the number moved.

Your user count went up. That is the whole mechanism. When your users live in a database you do not control, leaving is a migration project nobody has headroom for, and the price knows it. The quote is not really priced against your usage. It is priced against your cost of leaving.

Two stepped lines rising together across three renewals: what you are quoted, and what leaving would cost. An arrow from the lower line to the upper marks the mechanism, because the quote is set from the cost of leaving. renewal 1 renewal 2 renewal 3 what you are quoted what leaving would cost
The arrow is the whole mechanism: the quote is set from the cost of leaving, so the two climb together. Neither line is measured; both are the shape of the thing. Lower the cost of leaving and the other line has nothing to climb.

Four things to do before the call.

None of these require you to switch anything. They change what the call is about.

Price the alternative first“We’re evaluating options” is worth nothing; procurement hears it weekly. What moves a number is a dated migration plan with a named destination, including one you hope not to use.
Ask for terms, not just a discountA discount rents you a year and you have the same call again. Ask for three things in writing: no auto-escalator, true-down rights if usage falls, and an export clause covering your user store, in a standard format, on request, at no cost.
Ask the export question in writingSend this to your account manager and keep the answer. If it takes a ticket, a paid plan tier, or a week, you have just measured your switching cost, and that number is what next year’s quote is built on.The questionIf we terminate, do we receive our users, with their password hashes, in a standard format, on request, with no support ticket, no fee and no legal review?
Read what is actually meteredMost auth bills are a per-user meter plus a handful of enterprise features gated to the top tier. You negotiate a bundle badly and a line item well.

If you decide the fix is structural.

A discount does not change the mechanism. Owning the user store does. Signet is a customer identity and auth engine: one Rust binary against your own PostgreSQL. People, service accounts and AI agents all sign in through it, all live in that database, and all are switched off the same way. Credentials never leave it and nothing phones home.

Coming inBring your existing users with their password hashes. Signet reads bcrypt, Argon2, PBKDF2 and scrypt, verifies against the hash you already have on first sign-in, and upgrades it afterwards. Nobody resets a password. signet import --dry-run tells you what would land before anything is written.
Going outThe exit is pg_dump. Hosted, we hand you the dump when you ask: no ticket, no fee, no call, and within two business days. We aim at same day and usually hit it; two is the number we will put in a contract, because your team and ours are not always in the same timezone. Ask us the export question above. We would rather you asked it of everyone.
What it costs
$299/mo flat
Hobby is $0, one instance each. Then $299/mo on Team: one production instance, unlimited users and unlimited SSO connections. $999/mo on Business adds a staging instance and an SLA. On your own hardware the same binary ships under a Scale licence at $15,000/yr, and a fixed-price $15,000 migration sprint is how the move actually happens. No per-user tier, no overage line, no usage meter: your bill does not move when you win a customer.
What we do not haveNo SOC 2 report. Type I targeted 2027; the date is set when the first enterprise deal requires it, and readiness work is priced into that deal. If your procurement hard-requires a report this cycle, we are not your vendor this cycle, and you should hear that from us rather than from a questionnaire in week six. The rest of what we do not claim, each row with its honest date, is on the security page.

Prices effective 2026-08-07. The full ladder is on the pricing page.