Skip to content
Source-available · BSL 1.1

The leaderboard for your engineering team.

Kreds turns merged pull requests, reviews and closed issues into a live leaderboard. Weighted so that helping someone ship beats shipping alone.

Get startedView on GitHub
Self-host itSponsor the projectkreds.sh
kreds ledger --tail
  • +25PR #128 mergedapi
  • +15Review on PR #131web
  • +10PR #127 approvedweb
  • +505-day streak

Every award is a row you can click through to the pull request.

How it works

Four steps, then it runs itself.

No bot to configure, no standup ritual to add, nothing for your team to remember. Kreds reads what GitHub already knows.

  1. 01

    Sign in with GitHub

    One click. Kreds asks for your handle and which organizations you belong to. It never asks for your code.

  2. 02

    Connect your team and repos

    An admin installs the Kreds GitHub App once and picks which repositories count. Everything else stays invisible.

  3. 03

    Earn Kreds from real contributions

    Merges, reviews, approvals, closed issues and streaks. Awarded automatically as the webhooks arrive.

  4. 04

    Compete on the leaderboard

    Weekly, monthly and all-time. Open it on a Friday and see who actually carried the week.

Features

Built for the way engineers actually work.

Every feature exists to answer one question: who is moving this team forward? Anything that did not help answer it did not get built.

GitHub login

OAuth for identity, a GitHub App for activity. Two grants, deliberately separate — no member ever hands over code access.

Real-time tracking

Webhooks, not polling. A merge shows up in the feed before you have closed the tab.

Leaderboards

Weekly, monthly and all-time, with rank movement so you can see who is climbing, not just who is ahead.

Achievements

First Merge, Review Machine, Top Reviewer, Weekly #1. Define your own on paid plans.

Streaks

Consecutive days with a scoring action. Bonus awarded once per streak — weekends don't break it.

Challenges

Time-boxed team goals. “No pull request waits more than 24 hours” beats nagging in standup.

Team insights

Where reviews pile up, who is carrying them, and which repositories nobody is looking at.

Self-hosting

Docker Compose, your infrastructure, your GitHub credentials. No license key, no phone-home.

API and integrations

REST API, outgoing webhooks and exports. Slack, Discord, Linear and Jira on paid plans.

The board

Reviews are worth more than merges. On purpose.

A review is 15 Kreds and a merge is 25, so two reviews beat shipping alone. That single ratio is the whole opinion of the product.

kreds board --all-time
weeklymonthlyall-time
RankMemberKredsPRsReviewsWeek
01–mariel-dev2,1803864+285
02–tomas-r1,7453152+310
03–shu-codes1,4802741+190
04▲2ana-builds<you>1,0151928+240
05▼1dan-ships970346+150
06▲1lu-park6801218+140

dan-ships has the second-most merged pull requests on this team and sits fifth — six reviews. The board rewards helping, not shipping alone.

kreds feed --followlive
  • +25mariel-dev merged api#4124m
  • +15you reviewed web#18822m
  • +50shu-codes hit a 5-day streak1h
  • +10tomas-r got approved on infra#882h
  • +15ana-builds reviewed api#4373h
Pricing

Generous where it counts.

Self-hosting is free at any size, always. The hosted plans exist so you don't have to run it — and the Community tier is a real product, not a trial with a countdown.

Community

$0forever

Everything a small team needs to make contribution visible.

Get started
  • Up to 20 members
  • 1 team
  • Unlimited repositories
  • GitHub integration
  • PR merged, review and issue tracking
  • Weekly, monthly and all-time leaderboards
  • Activity feed
  • Kreds and streaks
  • Basic achievements
  • Up to 3 custom achievements
  • 1 active challenge
  • Basic reward configuration
  • 30 days of analytics
Most teams

Team

$2.99per member / month

For teams that want the whole thing, priced per person.

Start free trial

Everything in Community, plus:

  • Unlimited members
  • Unlimited achievements
  • Unlimited challenges
  • Advanced Kreds rules
  • Seasons
  • Full analytics history
  • Slack and Discord integrations
  • Linear and Jira integrations
  • API access
  • Webhooks
  • Exports
  • Multiple squads and groups
  • Better admin controls

Growing

$79per month, flat

Same as Team, flat rate. Cheaper from 27 people up.

Choose Growing

Everything in Team, plus:

  • Up to 50 members
  • Flat pricing, no per-seat math
  • Everything in Team
  • Predictable invoice as you hire

Enterprise

Custom

For 50+ engineers and the paperwork that comes with them.

Talk to us

Everything in Growing, plus:

  • 50+ members
  • SSO and SAML
  • SCIM provisioning
  • Audit logs
  • Advanced permissions
  • Dedicated support and SLA
  • Private cloud or on-premise
  • Security and compliance review

Team is per-seat, Growing is flat. Past 27 members Growing is the cheaper of the two — we would rather tell you than let you work it out on the invoice.

Free forever for open source

If your project is public and non-commercial, the Team tier is yours at no cost. Permanently — not a discount that expires.

Claim it →
Self-hosting

Run it yourself. Free, at any size.

Self-hosting is a first-class path, not a grudging concession. The whole product is in the box — no feature is held back to push you onto the hosted plan.

Docker, and that's it

Postgres and Redis are in the compose file. One command up, one command to upgrade.

Your GitHub credentials

Your own OAuth App and GitHub App. Events go from GitHub to your server and stop there.

Anywhere you like

A laptop, a $5 VPS, your own Kubernetes. No license key, no seat check, no phone-home.

Documentation included

The real guide, not a teaser: App setup, upgrades, backups, proxies, and the errors we actually see.

bash
# clone, configure, run
$ git clone https://github.com/zitdevs/kreds.git
$ cd kreds
$ cp .env.example .env
$ docker compose up -d

# http://localhost:3000
Read the self-hosting guideDeploy it yourself

One caveat we would rather say up front: GitHub has to reach your webhook endpoint, so a public HTTPS URL is required. For local development, a tunnel does the job.

Licensing

Source-available. We won't call it open source.

Kreds is licensed under the Business Source License 1.1 — the same one Sentry, Cal.com and CockroachDB use. It does not meet the OSI definition, and pretending otherwise would be the first dishonest thing on this page.

You can

  • View, fork and study the source
  • Self-host it — laptop, VPS, your own cloud
  • Use it inside your company, at any size, in production
  • Modify it for your own needs
  • Contribute changes back

You can’t

  • Resell it as a competing hosted product
  • Monetize a hosted version without permission

The line is whether you are serving your own organization or selling to third parties. Running Kreds for a client as part of consulting work is fine. Launching “managed Kreds hosting” is not.

It becomes Apache 2.0 on a fixed date

Every released version converts to the Apache License 2.0 four years after release. That is written into the license itself, not promised in a blog post we could walk back. Kreds only ever gets more permissive.

v0.1.0Apache 2.0 · 2030-08-21

Why not MIT?

Because a permissive license lets a cloud provider host Kreds, sell it, and put nothing back — and there is no version of that story where the Community tier stays free. The BSL draws exactly one line and leaves everything else intact.

Read the LICENSELicensing FAQCommercial license
Community

Source-available, still community-first.

A restricted license is not an excuse for a closed process. Issues, roadmap and reasoning are public, and open-source teams get the paid tier for free.

Contributions welcome

Bug reports, docs fixes, new achievement ideas, integrations. No CLA — we only ask that what you send is yours to send.

Read the contributing guide →

Start somewhere small

Issues labelled good first issue are scoped small on purpose, with the context you need already written down.

Browse good first issues →

Built in the open

Roadmap, design decisions and the trade-offs behind them all live in Discussions. Disagree in public — that is the point.

Join the discussion →

Docs, not a teaser

Self-hosting, scoring rules and licensing are documented properly, including the parts that are annoying.

Read the docs →
FAQ

The questions people actually ask.

Including the awkward ones. If something here is still unclear, open a discussion and we will answer it in public.

Is Kreds open source?

No, and we will not claim otherwise. Kreds is source-available under the Business Source License 1.1. The source is public, you can run it, modify it and contribute to it — but the license restricts one thing (offering it as a competing hosted service), and that restriction is what puts it outside the OSI definition. Each version becomes Apache 2.0 four years after release.

Can I self-host Kreds?

Yes, free, at any team size, forever. Docker Compose with Postgres and Redis is in the repository, and the whole product is in the box — nothing is held back to push you onto a paid plan. You bring your own GitHub App credentials, so your events never leave your infrastructure.

Can I use it inside my company?

Yes. Internal use is expressly granted, including in production and at any headcount, and including running it for several teams inside the same organization. Running it for a client as part of consulting work you do for them is fine too.

Can I create a hosted competitor with it?

No — that is the single thing the license forbids. You cannot offer Kreds to third parties on a hosted or embedded basis in order to compete with our paid version, and you cannot sell managed Kreds hosting without a commercial agreement. If that is what you want to build, email us; the conversation is welcome rather than a trap.

Is Kreds free for open-source projects?

Yes. If your project is public and non-commercial, the hosted Team tier is free permanently — not a discount that expires. Open an issue with a link to your organization and we will enable it.

What integrations are planned?

Slack and Discord first, so a weekly recap lands where your team already talks. Linear and Jira after that, so issue work counts alongside GitHub activity. Both are on the paid tiers. The roadmap lives in GitHub Discussions and it moves based on what people actually ask for.

Does Kreds read our source code?

No. The GitHub App asks for read access to metadata, pull requests and issues — never file contents. It receives pull_request, pull_request_review and issues webhooks, which carry titles, authors and states. That is everything Kreds needs to score.

Will a redelivered webhook award Kreds twice?

No. Every award is keyed on the event type, the GitHub node id and the recipient, with a unique index behind it, so a replayed delivery collides and is dropped. GitHub redelivers more often than people expect, so this was built in from the first commit rather than patched in after someone noticed a doubled score.

What happens if an admin changes the Kreds values?

Past awards keep the amount they were granted with. Rule changes only affect future awards, so a leaderboard never silently rewrites itself when someone edits a setting. Each award in the ledger shows the value it was granted with.