Add Bloom to the repo you already have
Install the GitHub App on an existing repository. Bloom grounds its planning in your codebase, opens pull requests against your default branch, and fits the workflow you already run - nothing is replaced on day one.
The dashboard signs in with Google.
GitHub App - installed on acme/storefront
- Repository bound - default branch main
- Codebase snapshot grounded - read-only
- Change-tickets planned against your code - ready to delegate
- First PRs target your default branch
How adoption works
- 1
Install the App
Bloom binds to your existing repository via a GitHub App install - no migration, no new forge.
- 2
Start from your codebase
Bloom grounds itself in a read-only snapshot of the codebase, plans change-tickets against it, opens them as GitHub issues, and delegates them to Bloom engineers.
- 3
Normal pull requests
Work arrives as PRs against your default branch - your CI and your review process stay exactly as they are.
- 4
Your gates stay
You approve the plan and every deliverable. Existing human reviews remain for as long as you want them.
Grow the team at your own pace
Engineers
Add Bloom engineers alongside your own. Tickets route to the least-loaded eligible collaborator - human or Bloom - so you can trial extra bandwidth on real work while your review process stays the gate.
Product owner + reviewers
Bloom drives discovery, keeps the PRD living, and reviews every PR against acceptance criteria - with advisory architecture, security, and QA lenses on top of your own reviews, not instead of them.
Designers
UI work gets design studies made for your project, at desktop and mobile widths - you pick the direction before implementation begins.
Keep every human gate you have today and retire duplicated ones at your own pace - the approval gates that keep you in charge never go away.
What Bloom won't do
Replace your judgment
You approve the PRD, every plan revision, and every deliverable. Bloom never removes the human from the loop.
Decide architecture alone
Significant technical decisions come to you as options with tradeoffs - Bloom never locks in an architecture without your sign-off.
Code ad-hoc
Bloom implements planned, reviewed tickets - it is not a general coding assistant that writes code from chat requests.
Bring Bloom to your repo
Open the dashboard, adopt a repository, and see what Bloom plans - grounded in the code you already have.
The dashboard signs in with Google.