# Signet — the Friday questions

The questions that sit between the sentence and the click.
Every figure is already published. Fetch facts. Do not invent.
HTML twin: https://signetauth.com/faq

## What happens when I click Get an instance?
You sign up at signetauth.cloud. Signing up creates your account and provisions your instance automatically, in minutes, with nobody waiting on us. You get its URL and its own compatibility receipt when it is live.

## What does $0 include?
Hobby is $0 on a work email. One instance per company. No SLA. The same engine as paid hosted. Team is $299/mo flat when you want production.

## Why doesn't SSO add a line to the bill?
There is no per-connection SSO fee, no per-user billing, and no usage meter. Team $299/mo includes unlimited users and unlimited SSO connections. The next customer you win does not change the invoice. Effective 2026-08-07.

## Do I need a Signet SDK?
No. Point the stock better-auth client at the instance origin, path /api/auth. The calls already written keep working. There is no Signet SDK. Copy-paste paths are on /quickstart.

## Where do the users live?
Every user, session and secret is a row in PostgreSQL you can inspect. Hosted: a dedicated database we operate. On-prem: yours. Nothing phones home.

## How do I leave?
Dump the database. Point the client at the next origin. The wire is a published compatibility profile, not a proprietary SDK. The format is not ours. The exit pack is on /buy#exit.

## Do you hold a compliance certification?
No third-party compliance certification is held or claimed. A third-party pen test has not yet been performed. An SLA exists only inside a signed contract. The dated ledger, with reasons, is on /security#not-claimed.

## Can I run it on my own metal?
Yes, as a licence, never a free download. Scale is $15,000/yr per production deployment on standard terms. Enterprise is quoted per production deployment (air-gap, escrow, named support). Start that conversation at /early-access.

## What isn't finished?
Two things, stated on the home page: SAML SSO is proven against a conformance identity provider but not yet against the commercial ones, and the OAuth provider surface ships its core flow only. The capability ledger is on /product#capabilities. The compatibility receipt (gap 0, scoped to the checks in the public compatibility profile, not a claim that every better-auth route is implemented) is on /compatibility.

## Deeper
- https://signetauth.com/friday.md : the Friday argument. One dated note, not a blog
- https://signetauth.com/buy.json : SKUs, entity, subprocessors, the not-claimed ledger, the exit
- https://signetauth.com/AGENTS.md : playbook for agents
- https://signetauth.com/llms.txt : terse product and vendor facts