Repository insights

Know what changed. Without reading the code.

Unolia links GitHub and GitLab repositories to their client projects and turns pushes into a story anyone can read: the commit, its author, the build result and the packages it changed.

a1f3c92 main

Fix checkout rounding

ML Marc Lefebvre · 14:12

Build and tests

run #212

running… passed · 1 min 40

reading the diff… 2 packages changed

laravel/framework 11.44 12.0 major

guzzlehttp/guzzle 7.8 7.9 minor

release notes attached

loopline.app

Loopline · production

waiting deployed in 42s

From push to production, one readable story

What are Repository Insights in Unolia?

Repository Insights links your GitHub and GitLab repositories to client projects, each repository finding its project automatically. Commits arrive with their author matched to your team, CI runs arrive with their verdict, and every commit carries a diff of the packages it changed across composer, npm and pnpm, with release notes readable in place and known vulnerabilities flagged. Version history and license detection join on higher plans.

The feed

What changed, who changed it, did it pass.

The next time a client site misbehaves, the first stop is not a terminal. It is the project page, where the afternoon commit, its build verdict and its package bumps are already lined up in plain rows.

Commits signed by the teammate, not a username.
Every build run lands with its verdict.
Each commit carries its dependency changes.

studio-meridien/loopline main

ML Fix checkout rounding a1f3c92 · Marc Lefebvre · 14:12 2 deps CI ✓

NR Update the mail templates 9d21e07 · Nadia Roche · Tue CI ✓

SB Bump the build tooling b82f440 · Sofia Brandt · Mon CI ✗

Signed by teammates, not usernames

How it works

From push to plain language

Connect GitHub or GitLab

Repositories find their client project on their own, and the history starts filling in.

Let the story build

Commits, build runs and dependency diffs arrive as the team pushes. Nobody files anything.

Read it, whoever you are

Support reads the story in plain rows. Developers deep-link into the code when it matters.

The diff

Every commit confesses its packages.

A push that bumps a framework a whole major should not look like every other push. The diff names each changed package, grades the jump, flags known vulnerabilities and hands you the release notes without leaving the page.

Commit a1f3c92 · dependencies composer · npm

laravel/framework 11.44 12.0 · release notes readable here major

guzzlehttp/guzzle 7.8 7.9 minor

vite 5.2 5.3 · npm minor

Composer, npm and pnpm in the same diff

Authors · studio-meridien/loopline this month

ML Marc Lefebvre mlefebvre42 on GitHub 14 commits

NR Nadia Roche nadia-r on GitHub 9 commits

SB Sofia Brandt sofiabuilds on GitHub 6 commits

The same people as your team page

Real names

Written by Marc, not by mlefebvre42.

Unolia matches commit authors to the people on your team. Project managers read names they know, clients hear answers instead of usernames, and when a change needs explaining you know exactly who to ask.

AI agents

When a deploy breaks, your AI already knows the timeline.

Connect an AI agent to Unolia and it reads a deploy the way you do: the commit, the packages it bumped, the build verdict and what shipped when. Its first guess starts from what changed, not from a blank page.

Discover AI Agents →

AI agent · Loopline the 14:12 deploy

Could anything in this afternoon’s deploy touch the checkout totals?

14:12 · a1f3c92 deployed · build passed

laravel/framework 11.44 → 12.0 · a major

Release notes: money rounding behavior changed

Yes: the framework major changed how amounts are rounded. Test checkout before the client does.

Answered from the timeline, in seconds

In real life

The moments this changes

The afternoon it broke

The client calls at 15:40. The project page shows one commit at 14:12, a green build and a major framework bump. You know where to look before you have opened a single file.

The PM who answered

A client asks whether the fix shipped. The project manager reads the commit, the green build and the deploy, and answers in the same minute. No developer was interrupted.

The sneaky major

A routine-looking push carried a whole major version. The diff flagged it amber, the release notes were read in place, and the breaking change was tested before any client saw it.

How this grows with your plan

See pricing →

Developer

Repositories, commits, build runs and dependency diffs.

Freelancer

Security audits across every dependency.

Startup

Version history and license detection.

Business

Agency scale: 50 seats, custom roles and synced access around the code.

Related feature pages

Website Operations One console across providers, with per-person buttons, kept logs and AI-analyzed deployments. Security and Maintenance Continuous checks across DNS, email, dependencies and uptime, with fixes and the proof on the record. Agency Activity Log Everything that happens across client projects, signed by whoever did it and filtered in one click.

Know what changed before you debug the client site.

Join the waitlist and give every client site a history the whole agency can read.

Join the waitlist