For GitHub org admins
What Stett asks for, keeps and shows.
Read this before you install: what the GitHub App asks for, what Stett keeps, who sees what, how to set a seat ceiling and how to remove Stett.
Stett shows engineering managers how their team reviews code, and gives every engineer a guided review. It runs on top of GitHub: your repositories and workflows stay where they are.
Signs you in with GitHub, then opens the install.
- GitHub App permissions
- 6 of 8 read only
- Source code
- No clones, no whole files
- Where the data lives
- United States
- Uninstalling
- Deletes the mirror
Not an org admin? Send them this.
Only an org owner can install the GitHub App. Copy this note, or open it in your email.
Subject: Can you install Stett on our GitHub org?
I'd like to try Stett on our org for 14 days. It shows where our pull requests wait and gives each of us a guided review. It needs an org owner to install its GitHub App. Six of its eight permissions are read only. The two that write act only when one of us starts something. Everything it asks for and keeps is here: https://www.stett.dev/for-admins. No card for the trial.
What the GitHub App asks for
Stett's GitHub App reads your org's repositories so the team pages and the review tools work. Two permissions can write, and only for actions a person starts.
| Permission | Level | Access | Why |
|---|---|---|---|
| Metadata | Repository | Read | Repository names and visibility. GitHub gives every App this one. |
| Contents | Repository | Read and write | Read files and diffs for review and code questions. Write lets agent runs you start push fixes for failed checks or merge conflicts to the pull request branch. |
| Pull requests | Repository | Read and write | Read to mirror pull requests, reviews, comments and timelines. Write only to post a comment when an agent run someone started from Stett finishes. |
| Issues | Repository | Read | To mirror issues and their comments. |
| Discussions | Repository | Read | To show discussions and their AI briefings. |
| Commit statuses | Repository | Read | To show whether a pull request's statuses pass. |
| Checks | Repository | Read | To show check runs on a pull request. |
| Members | Organization | Read | To confirm who belongs to the org, so people join the right workspace. |
Events it listens for
To keep mirrored data current.
- pull requests
- reviews
- review comments and threads
- commits
- pushes
- issues and sub-issues
- issue comments
- discussions and their comments
- releases
What people grant as themselves
People who sign in also grant Stett five OAuth scopes as themselves: repo, notifications, read:org, read:user and user:email. Stett writes to GitHub as a person only when they press a button, such as submitting a review or merging.
Two things you may need to do
Most orgs need only the first.
Install the GitHub App on your org.
Only an org owner can. You choose all repositories or a list of them.If your org restricts third-party access, approve Stett's OAuth app too.
Without it, members can read in Stett but cannot comment or review from it. On GitHub, open your org's Settings, then Third-party access, and approve Stett.
What Stett stores
A mirror of the work on your pull requests, issues and discussions. Never the repository itself.
Kept
- Pull request, issue and discussion metadata: titles, descriptions, comments, reviews, labels, reviewers, commit messages, file lists and timelines.
- The diffs of the pull requests it mirrors.
- Raw webhook payloads from GitHub, deleted after 30 days.
Never kept
- Whole source files.
- Repository clones. Agent runs you start use a checkout of the selected repository to make fixes, then it is gone.
- The files Ask reads for an answer, though an answer can quote parts of them.
The database is in Virginia, United States. The privacy policy names every company that processes your data and where it runs.
What goes to AI
Only the text a feature needs, sent to Anthropic, or to OpenAI if Anthropic is down. Three kinds of request, each with its own limits.
AI features
Send the text they need to Anthropic. Some retry with OpenAI if Anthropic is down, and reuse cached results where available. Team includes 250 AI operations per seat a day, pooled across the org.
Ask
The assistant reads files and pull request data from GitHub on demand. We keep questions and answers for 90 days; you can delete a thread at any time.
Agent runs you start
To fix failed checks or merge conflicts, the run checks out the pull request branch on Anthropic's servers, pushes a fix to that branch and comments on the pull request when it is done. It gets a short-lived token for that one repository and can finish after you leave the page.
Who sees what
Stett never shows anyone a repository GitHub would not show them. Public repositories are open to every member. Private ones are checked against GitHub for each person.
Managers
Managers see the team pages for the whole org: Insights, People, Reviewers, AI and Queue. A manager is the org's owner in Stett, anyone the owner makes a Stett admin, or anyone GitHub lists as an admin of the org.
Members
Members see only their own work and numbers: the pull requests they wrote or were asked to review, and their own figures next to the team median. Never anyone else's numbers.
Bots and review apps never count as people. Stett tells them apart by the account type GitHub reports.
Trial, seats and the ceiling
You pay for the people who joined, never more than a ceiling you set.
Installing the App starts a 14-day Team trial for the org.
No card to start.People in the org join on their own when they sign in to Stett, up to a seat ceiling.
You set the ceiling when you subscribe, in Settings on your org's card. Change it there later with Change seat ceiling.When someone would go over the ceiling, they wait.
The owner gets an email with a link to raise it.To take someone out, use Remove on the People card in your org's settings.
Their seat drops at the next renewal.
Removing Stett
One uninstall on GitHub. Stett stops at once and deletes what it mirrored.
On GitHub, open your org's Settings, then GitHub Apps. Next to Stett choose Configure, then Uninstall.
What happens next
- Stett stops receiving data from your org at once.
- It deletes the installation and every repository, pull request and issue it mirrored under it, and turns Stett off for the org.
- Uninstalling does not cancel a paid subscription. Cancel it from Settings in Stett with Manage billing, which opens the Stripe billing portal.
- To delete people's accounts and everything else Stett holds, email team@stett.dev. We delete within 30 days and confirm by email.
Security questionnaires
No SOC 2 report yet.
Stett does not have a SOC 2 report yet. This page and the privacy policy say what it asks for, keeps and shares. For security questionnaires, email team@stett.dev.
More detail
The long form, and a person to write to.