The repo explains itself
ShipsuitAI generates a guide to your codebase and commits it — new hires inherit it from git, and so does their assistant, on day one.
The suite
Everything the platform does, grouped the way it actually works: standardise how the team works, enforce it before code ships, and account for what it cost.
Every capability, at a glance
A generated codebase guide every new hire inherits from git.
One committed settings block, on every developer's machine.
Reviewers and strategists, defined centrally, served to everyone.
One rule change reaches every repo on its next run.
Nothing commits or pushes without your explicit approval.
One verdict, before a human ever opens the diff.
Sessions, commits and lines shipped — per developer.
What AI actually cost, per developer and per repo.
Revoke one person's access without touching anyone else.
Every admin action, recorded — and it outlives its subject.
Your source code never leaves the machine.
The same senior engineer, sitting with everyone.
ShipsuitAI generates a guide to your codebase and commits it — new hires inherit it from git, and so does their assistant, on day one.
A single committed settings block puts the same workflow on every machine. Nobody configures anything themselves.
Your review agents are defined centrally and served per run. Update one, and every developer gets the update.
Engineering rules are versioned and served fresh on every run — no pull request to twenty codebases.
Enforcement, not advice.
Nothing commits or pushes without approval, no database commands run, and prompts are nudged toward your rules before work starts.
Quality gates plus a house-rules review resolve to one verdict — unfinished work never reaches a reviewer's queue.
Know what it costs, who has it, and what changed.
Sessions, commits, lines shipped and the accepted-edit rate — per person, using the assistant's own reported activity.
What your AI assistant actually cost, per developer and repository — the assistant's own numbers, not estimates.
Seats, roles and per-developer credentials, revoked individually — plus account-level suspend and resume.
Every administrative action, recorded append-only. The record survives even the deletion of the thing it describes.