Lite is free. Pro adds this and the rest of the quality layer.
A SaaS appwith real accounts.
Login looks done when the form works. Adams helps you hold the build to the parts you cannot see: who can read whose data.
Lite and Pro
// the problem
What goes wrong
Works for you is not works for themIt is easy to build a page that shows the current user their data and forget to check that nobody else can request it by changing an id.
Scope creeps with every account featureReset, invite, roles, billing. Each is small, and together they swallow the week while the product itself waits.
// what adams does
What Adams does
Asks before it builds authPro: a few questions settle sign in method, roles and what a user owns before a line of auth code is written.
Reviews access with fresh eyesPro: a separate security agent checks the scope you pick, such as authorization, and ranks what it finds.
Keeps keys out of the repoLite: service keys and session secrets are caught before they are committed.
// worked example
An example
Checking who can read what
Illustrative session.
~/project~/your-project · example
/adams:secure
Scope: input and access control
P1: orders can be read by id with no owner check
P2: password reset link never expires
Fix these findings? Yes (recommended)
// faq
Questions
Does Adams build the login for me?
Your AI does. Adams asks the decisions first, holds the work to the plan and checks it afterwards.
Which auth provider should I use?
That depends on your stack and your users. Adams asks and recommends, and you decide.
Is access control checking free?
No. The secure check is Pro. Lite covers secrets and git.
// related