PRIVACY BY DESIGN

Your code never leaves your machine

ReadyBase analyzes your codebase locally, on your own hardware, using your own git history. No code is uploaded. No server sees your source. No third party is in the loop.

Local-first

All analysis runs on the repo on disk. The binary reads your files; it doesn't send them anywhere.

Single binary

One static, CGO-free executable. No runtime, no background service phoning home, no dependencies to audit.

Inspectable output

Everything ReadyBase generates lands in your repo as plain files you can read, diff, and commit, or remove.

What stays on your machine

DataLeaves your machine?
Your source codeNever
Git history & authorshipNever
Readiness scores & reportsNever (stored in your repo)
Dependency graph & blast radiusNever
License validationAnonymous license check only

Common questions

Does ReadyBase send my code to an AI model?

No. ReadyBase computes context locally and hands it to whatever AI assistant you already use. Your relationship with that assistant is unchanged, ReadyBase just makes it smarter about your repo.

What gets written to my repo?

Guidance files (CLAUDE.md, AGENTS.md), guard rules, and a local intelligence index. All plain text, all yours. Remove them anytime with readybase uninstall.

Can I run it fully offline?

Yes, the analysis needs no network. The only outbound call is an anonymous license check, and the core scanning works without it.

Is it safe for proprietary / regulated codebases?

That's exactly who local-first is for. Nothing about your code, structure, or contributors is transmitted, so there's no third-party data-processing agreement to negotiate.