# SSO is not a line item.

A note. 2026-08-15.
The Friday problem, written out. Send this before the questions.
HTML twin: https://signetauth.com/friday

The deal is about to close. Then the buyer says they need SSO.

On a rented identity plane that sentence becomes a quote, and a new SKU. The login you already shipped is fine. The connection is the new line.

We do not sell the connection. We sell the plane.

Team is $299/mo flat, with unlimited users and unlimited SSO connections. Adding the prospect's identity provider is a configuration change, not a purchase order. Effective 2026-08-07. Hobby is $0 on a work email. One instance per company. No SLA. Business is $999/mo. Scale is $15,000/yr when you want the same build on your own metal. Enterprise is quoted.

Point the stock better-auth client at the instance, path /api/auth. There is no Signet SDK. Every user, session and secret is a row in PostgreSQL you can inspect. Nothing phones home. Leaving is pg_dump. The questions sit on /faq.

Two things we will not dress up. No third-party compliance certification is held or claimed. SAML SSO is proven against a conformance identity provider, not yet against the commercial ones. The OAuth provider surface ships its core flow only. Those sentences also live on /security and /product.

This is one dated note, not a stream. If we write another, that page will say so.

## Deeper
- https://signetauth.com/faq.md : the Friday questions
- https://signetauth.com/buy.json : SKUs, entity, subprocessors, the not-claimed ledger, the exit
- https://signetauth.com/AGENTS.md : playbook for agents