Access & accounts
How to get in, what a plan gives you, and how tokens, seats and billing fit together.
Invite-only
Lock Master is invite-only. You can't just sign up and start — access is granted by approval. The flow is short:
- Sign in with Google.
- Fill the short request form (what you're building).
- Wait for approval — you'll get an email when you're in.
Until you're approved you can't reach the panel or download the CLI. That's by design.
Requesting access
Sign in at the panel with Google. If your account isn't approved yet, you land on a page that asks what you're shipping. Submit it and we review it by hand. Approval creates your account's first license and emails you.
Signing in
Sign-in is Google only. Your identity is your Google email; there's no separate password to manage. Once approved, signing in takes you straight to your account.
Plans
Your license sits on a plan, which sets your monthly tokens and how many seats you get:
| Plan | Price | Seats | Monthly tokens |
|---|---|---|---|
| Small dev | €11.99/mo | 1 | 250 |
| Team | €29.99/mo | 3 | 800 |
| Enterprise | Custom | Custom | Custom |
You activate a plan from billing in your account. An approved-but-unactivated license can't download the CLI until a plan is active.
Tokens
Pricing is flat: one build costs one token, regardless of the size of your JAR or how many techniques you enable. No per-megabyte metering, no surprises.
- Any successful obfuscation of any plugin — small or large — is 1 token.
- Reference libraries don't cost tokens. The library jars you declare are used only to resolve the class hierarchy; they're never obfuscated and never charged.
- Jobs are capped at 350 MB (your JAR plus its libraries). Anything larger is rejected up front, before a token is spent.
There are two kinds of token:
- Monthly tokens — granted by your plan, reset each billing cycle. Use-it-or-lose-it: they don't roll over.
- Token packs — one-off top-ups (+100 for €9.99). These never expire and are only spent after your monthly tokens run out.
An empty/no-op config is rejected before a job is created, so you never waste tokens on a run that does nothing.
Seats & API keys
A seat is a slot with its own API key — that key is what the CLI uses to authenticate. Give each machine or CI runner its own seat key rather than sharing one:
- Create keys under Seats & keys in your account.
- Keys are shown once — copy on creation. If you lose one, rotate it.
- Rotating a key revokes the old one immediately; removing a seat does too.
- Your plan sets the maximum number of active seats.
Billing
Payments run through Stripe. From billing you can activate a plan, buy token packs, or open the Stripe portal to change or cancel your subscription. If you cancel, you keep access until the end of the paid period.