Knowwhatdevelopers areshipping.
Without asking, without the status meeting. DevSummary reads your team's GitHub and sends a plain-English brief to Slack or email, daily or weekly.
See it in action — a 38-second walkthrough, with sound
You do two things. The rest is waiting.
Connect the repos, pick a day, close the tab. The next thing you do is read.
- Tue 2:14 PM · 2 min
Connect GitHub
Install the read-only app. Pick the repos that matter.
- It reads
- Commits, branches, diffs
- It can never
- Push, comment, review, merge
- Tue 2:16 PM · 1 min
Say what to watch, and when
Choose what a brief covers, when it runs, and where it lands.
- Scope
- Project · Team · Person · Repo
- Cadence
- Daily · Weekly · Monthly
- Delivery
- Slack · Email · Both
- Every Mon 9:00 AM
The brief lands
Plain English, skimmable in a minute. Forward it to whoever asked.
Payments went live this week
Customers can now pay, subscribe, and get refunds without leaving the app.
It reads on one side. It delivers on the other.
One read-only GitHub install on the source side. On the delivery side, pick the channel your team already lives in — Slack, email, or both.
Read-only access. Encrypted. Yours to delete.
- Read-only No push, no pull requests, no comments. Write access was never requested.
- AES-256-GCM Tokens encrypted at rest. Passwords hashed, never stored.
- Org-scoped Every call checked against your org and role. TLS in transit.
- Yours to delete Uninstall stops ingestion. Stored data goes within 30 days of a request.
What exactly do you send to an AI model?
Commit messages and diffs from the repositories you picked, capped at 60,000 characters per commit, sent to OpenAI under API terms that forbid training on it. We don't train on your code either. Detail in the privacy policy.
Starts at $9. No per-seat pricing.
One plan per organization, decided by how many repositories you connect and how many brief schedules you run. Invite your whole team, count nobody, and pay the same for an open-source repo as a private one. Every plan starts with a 14-day free trial, cancel any time, and annual billing saves two months.
For a founder and a contractor, or a first product.
$90/year, save 2 months
- 2 repositories connected
- 3 brief schedules, daily, weekly or monthly
- Unlimited developers, no per-seat fees
- Slack & email delivery
- 30 days of history at setup
For founders & small teams shipping every week.
$390/year, save 2 months
- 5 repositories connected
- 10 brief schedules, daily, weekly or monthly
- Unlimited developers, no per-seat fees
- Unlimited projects & teams
- Slack & email delivery
- 90 days of history at setup
For agencies & managers reporting on many projects.
$990/year, save 2 months
- Everything in Team
- 10 repositories connected
- 20 brief schedules
- Org-wide rollups across projects & teams
- Dedicated onboarding & Slack channel
For engineering orgs with dozens of repositories.
Custom terms
- Everything in Business
- Unlimited repositories & schedules
- Volume pricing & annual invoicing
- Custom retention policy
- Priority support
Questions people ask first.
What it reads, what it writes, and what it costs.
How do I turn GitHub commits into a plain-English report?
Connect a tool that reads the code changes themselves, not just the commit messages. Messages like “wip” or “misc fixes” describe nothing, so anything summarising messages alone produces noise. DevSummary reads each commit's diff, classifies it (feature, fix, refactor, docs), and writes an outcome in business language.
How do I report engineering progress to non-technical stakeholders?
Lead with outcomes, not activity. A stakeholder needs “customers can now pay, subscribe, and get refunds without leaving the app” — not a branch list or a commit count. Keep it to one screen, send it on a fixed day so nobody has to ask, and keep the technical detail one click away for whoever wants it.
Can automated git reports replace daily standups?
They replace the status half of a standup — the part where everyone recites what they did yesterday, which the commit history already records. They do not replace the coordination half: blockers, decisions, and who needs help. Most teams that automate reporting keep a shorter standup, not none.
What GitHub permissions does a reporting tool need?
Read-only is enough, and anything asking for more deserves a second look. The DevSummary GitHub App cannot push a commit, open a pull request, or leave a comment — write permission was never requested, so it cannot be granted later by accident.
Does DevSummary read my source code?
Yes — that is the point, and we would rather say so plainly. It reads the diff of each commit in the repositories you selected, because reading the code is the only way to explain what a change actually did. It reads; it never writes. What happens to that code afterwards is covered under data and AI below.
Do you train AI models on my code?
No. Commit messages and diffs go to OpenAI's API under terms that do not permit training on submitted data, and we do not train models of our own on your code either. Full detail is in the privacy policy.
Do you charge per developer?
No. There are no per-seat fees on any plan, so invite your whole company, including the stakeholders who only read the reports. Your plan is decided by repositories connected and schedules running, never by headcount.
Is there a free trial?
Yes. Every plan starts with 14 days free on your own repositories, with a 30-day historical backfill. A card is required up front; cancel before day 14 and you pay nothing.