The leaderboard for your engineering team.

Yes. Kreds Core is licensed under AGPLv3, which is an OSI-approved open source license. Not source-available, not open-core with the interesting parts removed. The repository is the whole product.

Yes. AGPLv3 permits commercial use, and your company can self-host it at any size without asking anyone. You can also charge money for services around it, including hosting it for other people.

Yes, subject to AGPLv3. The one obligation the license adds is this: if people interact with your modified version over a network, they have to be offered the corresponding source of that modified version. Run it unmodified and nothing changes. Modify it for your own team and nothing changes either, because your team is not a third party being served over a network.

No. The Official Kreds Network is separate, proprietary infrastructure: the Official KRED ledger and its fixed supply, the Central Bank, global settlement, network identity and the risk systems. A shared economy needs one authoritative ledger, and anti-abuse rules stop working when they are published. Everything that does not require a shared network is open.

No. A self-hosted instance is independent by default. It runs its own economy, its own currency, its own supply, its own treasury and its own monetary policy, with no dependency on kreds.sh and no automatic participation in the Official Network.

That is what the Kreds Network protocol is for. Joining can bring Official KRED, network identity, official settlement and participation in the global economy, and it requires meeting the Network's integrity requirements. Joining preserves history rather than resetting balances.

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.

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.

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.

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.

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.

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.

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.

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.