Step 1: Create your account
Go to console.ironbee.ai and sign up with Google, GitHub, or your work email. The first time you sign in, Name your account, for example after your company, and click Continue. See Sign in and team access.Step 2: Connect your repositories
When you create a new account, the console opens Set up IronBee. It has three steps: Connect, Pick repositories and First review. The first one, Connect your repositories, offers three cards: GitHub, GitLab and Bitbucket.1
Connect
GitHub: click Install on GitHub. GitHub opens in a new window, where you pick the organization or account and the repositories IronBee can see. The step reads Finish on GitHub and moves on by itself once the App is installed.

- If the window doesn’t open, or you’d rather stay in one tab, click Continue in this tab instead. GitHub brings you back to this step.
- If you can’t install apps in your organization, pick the organization anyway. GitHub sends a request to its owners, and the step shows Request sent to your organization owners. It moves on by itself when one of them approves. Meanwhile, Copy link copies the install link to send to an owner, and Open GitHub lets you install on an account you own instead.


2
Pick repositories
GitHub: every repository you shared with the App is already an IronBee project. Under Pick repositories to connect, the ticks set which of them also have code review on. Click Connect N repositories. Missing a repository? Click Change access on GitHub, share it with the App, then click Refresh.GitLab and Bitbucket: a group or a workspace makes no repository a project until you pick. Choose All repositories, which includes the ones added later, or Only selected repositories, and tick them. Each repository you pick is connected as a project and gets everything IronBee does for a repository, reviews included. Click Connect N repositories. Missing a repository? Click Sync now.



3
First review
Under Pick a pull request for your first review, or Pick a merge request for your first review on GitLab, pick an open one and click Review #N. Drafts are marked Draft, skipped.

The step follows the review: Queued, Starting the reviewer, Reading the changes, Posting the review on GitHub (or on GitLab, on Bitbucket). You can Close it at any time; the review keeps going and shows up on the pull request. When Your first review is ready, click Open the review to read it in the console, or View on GitHub (View on GitLab, View on Bitbucket).No open pull request yet? Click Finish setup. IronBee reviews the next one on its own.





Step 3: Add verification
Code review needs only the GitHub App, the GitLab connection or the Bitbucket connection. To also verify your changes, owners and admins open Settings > Getting started. It offers six ways in, and you can connect more than one.

- GitHub Action
- GitLab component
- Bitbucket Pipe
- Vercel
- Netlify
- CLI
Verify every push and pull request with the IronBee Action.
- On the GitHub card, click Add the Action. If the App isn’t installed yet, click Connect GitHub and install it first.
- In the IronBee Action step, pick:
- the Repository
- Where it runs: On IronBee or On your GitHub runner
- On a finding: Report it or Fix it too
- Fill in how your app starts, and add the repository secrets the console lists:
IRONBEE_API_KEY, plusANTHROPIC_API_KEYorCLAUDE_CODE_OAUTH_TOKENwhen your answers need one. Then click Create the file on GitHub. - Committing the file is a push, and that push starts your first verification run.
Step 4: See your results
Open Projects in the console. A GitHub repository is listed as soon as the App covers it, a GitLab or Bitbucket repository once you pick it, a Vercel project or Netlify site once you enable it, and a CLI project when its first data arrives. Click a project to open its Code review tab, then its Verifications tab:- While a run is in progress, you can watch it live.
- Afterwards, its detail page shows the recording, the actions, the network requests and the result.
Running in CI without the GitHub Action, the GitLab component or the Bitbucket Pipe?
Running in CI without the GitHub Action, the GitLab component or the Bitbucket Pipe?
Use the account API key instead of See Authentication for when to use each credential.
ironbee login. Owners and admins find it in the console under Settings > Account. Supply it through the environment:What’s next?
How integrations work
Projects, verification types, environments and where results land.
Key concepts
The terms used across the console and the docs.
Environments and secrets
Give runs the credentials to sign in to your app.
CLI configuration
Verify patterns, retry limits and devtools settings.