Everything that happened. One place.

Digests

Every week, Relake reads your repository and writes a plain-language digest of what actually happened — the merges, the open work, and the risks worth knowing. Summaries are rebuilt from real commits, PRs and deployments, so the context reads like your team wrote it herself.

Last digest: "Qutlin has seen significant progress in the last 7 days."

Releases

Every release comes with the code behind it. Relake tracks what reached production, who shipped it and what changed — so a release is never just a version number, it is the full story of the work that made it.

Current: "Production v1.4.2 deployed 2 days ago."

Always in sync

The project context never goes stale. Webhooks keep Relake connected to every push, review and merge, so the digests, releases and knowledge you see are always the living state of the repository — never a snapshot from last week.

Webhooks: every push, review and merge reflected within minutes.

Context that lives in your code

Relake turns every push, review and release into durable project context — so the answers your team needs are already written down.

Your AIYour voice your people

Relake adapts to your teamIt writes like you knows your people and thinks ahead

tone“direct, no fluff, like a sharp c…
branch_naming“feat/*, fix/*”
pr_titles“fix(billing): …” + linked issue
sprint_methods“story points, fibonacci”
prefers“tables over bullet points”
timezone“PST, don't schedule before 10am”

Writes like you

Your tone, your naming, your process — no generic AI prose.

Who's who

SOSana Osei · Billingshipped #481
TNTheo Novak · Paymentson #483
MCMaya Chen · Frontendpushed e94c7f
LPLena Park · Designapproved #476
RORafa Ortega · PlatformTurbopack on
SPSasha Petrov · Infraoffline · PST

Knows your people

Who owns what, who's on it and who's around.

Suggested next

1
Review #483 — 3DS2 checkout flowwaiting on you
2
EU rounding in prod — first batchwatch
3
Onboarding docs — coverage 91%gap closing

Thinks ahead

Pending reviews, fresh risk and closing gaps, surfaced early.

Questions teams ask us

Setup & security

Access

commitsread
pull requestsread
releasesread
write accessrevoked

Is my code safe with Relake?

Yes. Relake connects with read-only access, keeps your data scoped to your repo and never uses your code to train models.

  • OAuth scopes are limited to what the integration actually needs
  • Your repository is never shared outside your workspace
  • You can disconnect and purge all context at any time

Setup

connect GitHubdone
pick repositorydone
first digest~5 min

How long does setup take?

About 5 minutes — the same time it takes to install any GitHub app.

  • Connect with GitHub OAuth and pick your repository
  • Relake backfills history automatically on first connect
  • Your first digest lands within minutes, not days

How it works

Knows

merged diffslive
docs + ADRslive
team patternslive

What does Relake actually know about my project?

Everything your repository has said out loud: commits, PRs, releases, docs and the conventions your team follows.

  • Merged diffs, review threads and deployment history
  • Living docs and ADRs derived from real changes
  • Team patterns — naming, process, tone and timezone

Live

push · main2m ago
review #4835m ago
merge #48112m ago

How fresh is the context?

Live. Webhooks push every change into context within minutes — there are no exports or cron jobs.

  • Every push, review and merge is reflected immediately
  • Digests and notes are rebuilt from the current state of the repo
  • Stale docs get flagged before they mislead anyone

Pricing & team

Plans

Personal$0 forever
Teamfrom $12/mo
free startno card

Is Relake really free?

Yes — the free plan is free forever for personal projects, with paid plans when your team needs more.

  • Free plan covers unlimited personal projects
  • Team plans add shared knowledge and Slack delivery
  • No credit card required to get started

Channels

Slackconnected
GitHubconnected
VS Codeconnected

Can the whole team use it?

That's the point — one shared context, so every teammate lands on the same page without the meetings.

  • Everyone sees the same digests, insights and docs
  • Ask it in Slack, GitHub or the app — same answers
  • Context survives people leaving and joining

Start building your project memory.

Stop reconstructing the past.