Every repository of your product, in a single project.
Front end, API, mobile, infra: link the GitHub repositories that make up your product and run them together, without changing how your code is organized.
Link in one click
In Settings › Repositories, search your GitHub repositories and add them to the project. Unlink them just as easily.
One ticket, several repositories
A change touches both the front end and the API? One ticket, linked to both repositories.
Filter by repository
Each team views the Kanban of its own repository without losing the big picture.
Your code stays untouched
Grepo reads your repositories and their pull requests. It never writes to your code.
Built for products spread across repositories
Few products fit in a single repository. Grepo starts from what you ship — the project — and attaches the repositories to it, rather than the other way around.
- Unlimited projects and repositories from the Pro plan
- An entire GitHub organization, future repositories included
- Language and default branch shown for each repository
A big picture you can trust
Open tickets per repository, pull requests, resources and team are all in one place. No more switching tools to find out where the product stands.
- Ticket count per repository
- A ticket’s pull requests shown on the ticket itself
- “No repository” tickets for decisions and documentation
Frequently asked questions
Another question? Read the FAQ or write to us.
Do I need a GitHub account?
Yes, to link repositories: Grepo connects to GitHub to list the ones you have access to. Tickets can also exist without a repository.
Does Grepo modify my repositories?
No. Grepo reads your repositories and their pull requests; it never writes to your code.
How many repositories per project?
Up to three on the Free plan, unlimited from Pro upward.
Explore more
All features →Try Grepo with your team.
The Free plan has no time limit. Move to Pro when your team grows.