Repository scope
Pick the teams and repos to start with. Agree how often they’re audited and how many fixes you need.
ENTERPRISE · PLAN A PILOT
AI tools write code faster than your team can review it. Aster reads each repo for leaked keys, open database rules, packages with known holes and risky code. Try it on one repo, then agree access, AI providers and retention with us.
WHAT GETS AGREED
Aster should fit how your team already reviews code. These four go into the pilot plan, in writing, before anyone connects a repo.
Pick the teams and repos to start with. Agree how often they’re audited and how many fixes you need.
Decide who connects GitHub and who approves each fix. Aster never merges on its own. Seats and single sign-on (SSO) are part of this conversation, not a dashboard switch today.
Audits send no code to an AI model. For fixes, agree which AI providers your team may use. Each fix shows the model and files before anything is sent.
Set how long reports are kept, what success looks like, and how invoicing and support work.
HOW A PILOT RUNS
Start with the repos that matter most and the success criteria you set. Aster checks keys, database rules, packages and risky code. It doesn’t yet check webhooks, admin access or rate limits.
Tell us your team size, your stack and who reviews code today. We’ll suggest where to start.
Pick one team and a few repos. Agree how many audits and fixes the pilot needs.
Who connects GitHub, who approves fixes, which AI providers are allowed, how long reports are kept. All written down.
Read-only audits on the agreed repos. Each fix stays a draft until someone on your team approves it. Re-audits show what changed.
Check the results against your success criteria. Then decide on seats, invoicing and support.
LET’S MAKE IT CONCRETE
Tell us your team size, your stack and the repos you’d start with. We’ll suggest a pilot plan.
1 free audit every month. See what it finds in your own code, in plain English, before you talk to us.