Progress updates for the people who pay for it
Turn your merged work into a branded page your clients, investors or leadership can actually read. No branch names, no commit hashes, no internal names — just what changed for them, kept up to date automatically.
Included on every plan • No credit card required
Written for the reader
Pick client, investor, executive or team. The summary is framed around outcomes and leaves out internal details.
Branded and private
Your title, logo and accent color. Add a password and share one link; changing it revokes old access.
Always current
Choose the last 30 days or a calendar month. Download any period as a PDF for an email or a board pack.
Clients don't read commit logs
Agencies, freelancers and founders spend hours every month turning engineering work into updates for people outside the team: what shipped, what's next, why it matters.
Pasting PR titles doesn't work. They're written for developers, full of jargon and internal names, and they miss the outcome the reader cares about.
A Gitmore portal reads the same merged work and writes it for the audience you choose, in their language, on a page with your logo and colors.
What a portal includes
Plain-language summary
What shipped, grouped by theme, written for a non-technical reader.
Work in progress
What's being worked on now, so updates don't only look backwards.
Any repositories
Combine several repositories, across GitHub, GitLab and Bitbucket, into one update.
11 languages
English, French, German, Spanish, Italian, Portuguese, Dutch, Polish, Japanese, Chinese and Arabic.
View counts
See how often each portal was opened in the last 30 days.
PDF export
A clean, printable version of any period.
How it works
Create a portal
Name it, choose repositories, an audience and a language, and add your branding.
Share the link
Optionally protected by a password. Visitors don't need a Gitmore account.
It keeps itself up to date
New merged work appears in the next summary automatically.
Frequently asked questions
No. Portals show a written summary of shipped work. Branch names, commit hashes and internal people names are left out.
Writing a summary uses one AI credit from the portal owner. Summaries are cached, so visitors reading the page don't use credits.
Yes. Passwords need at least 8 characters, repeated wrong attempts are locked out, and changing the password signs everyone out.
Yes. Portals are on every plan; summaries use your plan's AI credits.
Start free in two minutes
Connect GitHub, GitLab or Bitbucket. Your last 30 days are imported straight away.
Get Started Free