Ajar.

THE SMALLEST ACCESS THAT WORKS

See what they could do
before you click Add.

Find the smallest GitHub role that lets someone help.

Simulate

Saved checks from two demo repositories. No live request is made in this mode.

Read-only. Nothing is changed on GitHub.

Saved demo data. No live request is made in this mode. AI reviews here are pre-computed examples, marked as such.

A LITTLE CONTEXT

A GitHub role is more
than its name.

1. Read the configuration. Ajar reads permissions, workflows, approvals and repository protections.

2. Follow what the role reaches. The house is the repository. Four doors illustrate access levels; the vault represents credentials used by workflows.

3. Choose the smallest step. See the role to grant now, the changes needed before more access, and the risk that remains.

Claude and GPT play on the seesaw while Gemini floats above. During a check they take separate illustrated routes: doors, window and roof. These are metaphors for the same permission result, not separate vulnerability tests. The characters are illustrated guides, not live AI agents. Permission calculations are rule-based. AI reviews of access requests are saved examples, clearly marked. Ajar never changes repository settings.

PRE-COMPUTED EXAMPLE

The request matters, too.

Look at the pattern in a request, never judge the person who wrote it.

Pre-computed example. These are saved Claude reviews. GPT and Gemini are not presented as having reviewed or agreed. No new AI call is made here. The maintainer decides.