The design-system governance instrument

Close design debt,
repo by repo.

Solarus audits every repository against your design system and opens small, reviewable fix PRs. Nothing merges itself — and no score moves until a re-audit confirms it.

FIG. 01  —  Fix PRs · Pilot Org · Example workspace LIVE · KP v1.0.4
Pilot Org
GitHub synced · 18m ago
Command Repositories Audits 1 running Fix PRs 2 Knowledge Pack Governance 4
KNOWLEDGE PACK
v1.0.4 · drift detected
Pull requests

Fix PRs

Pilot Org · Team GitHub sync · 18m ago KP v1.0.4 · drift Last completed audit · scan #318
Update Knowledge Pack Run audit
customer-app/Button.tsxMEDIUM
Finding · line 42

Hard-coded color bypasses the token scale.

Draft PR #184main ← solarus/audit-318/Button.tsx
−color: '#2b2a26'
+color: 'var(--color-text-primary)'
FoundDraft PRMergeRe-audit
Awaiting your review
Never auto-merged · open until a human decides
design-system/Badge.tsxMEDIUM
Finding · line 17

Hard-coded background bypasses the token scale.

Draft PR #190 · merged by a humanmain ← solarus/audit-318/Badge.tsx
−background: '#f1efe6'
+background: 'var(--color-bg-subtle)'
FoundDraft PRMergeRe-audit
Merged · pending re-audit
Not closed yet · the next scan confirms it
marketing-site/Card.tsxMEDIUM
Finding · line 88

Hard-coded border color bypasses the token scale.

Draft PR #176 · merged by a humanmain ← solarus/audit-312/Card.tsx
−borderColor: '#d9d6cb'
+borderColor: 'var(--color-border-muted)'
FoundDraft PRMergeRe-audit
Verified closed
Confirmed by scan #318 · no longer reported
customer-app/Toolbar.tsxLOW
Finding · line 23

Off-scale spacing: 13px sits between two steps of the spacing scale.

No PR opened. An owner can request the fix; Solarus then drafts it on solarus/audit-318/Toolbar.tsx.
FoundDraft PRMergeRe-audit
Fix available on request
Reported · waiting for an owner to ask
marketing-site/PricingToggle.tsxCANDIDATE
Candidate · line 5

Hand-built toggle resembles the existing Switch component.

Judgment call, not a mechanical fix. No PR is drafted; it stays a candidate until your team confirms it.
FoundDraft PRMergeRe-audit
Your team decides
No automatic fix · enabled per org
How a finding closes
  1. Found at an exact file and line, during an audit.
  2. Draft PR — one small change on solarus/audit-<scan>/<file>.
  3. Human merge — a person reviews and decides. Never auto-merged.
  4. Re-audit — the next scan confirms the finding is gone. Only then: closed.
Merged is not closed. Verified is.
The governance loop

One closed loop, run on your terms.

Solarus distils your design system, measures every repo against it, proposes safe fixes, waits for a human to confirm, and learns from what you approve. The loop only closes where a person signs off.

01
Ingest
Your design system → a Knowledge Pack
Tokens, components, rules and import paths, extracted from a repo or a Figma file into the pack every audit runs against.
02
Audit
Measured against the pack
Each finding is classified — safe-fix, manual, blocked or unsupported — and linked to the exact file and rule that produced it.
03
Fix
Small, reviewable fix PRs
One file cluster per PR, on request, each linked to its findings. Opened on a branch — never pushed to main.
04
Human
Confirm
A person signs off
Nothing merges itself. The score does not move until a re-audit confirms the fix actually disappeared from the code.
05
Learn
Decisions feed the pack
Hand-rolled repeats an owner confirms can become new-component Draft PRs for the pack, enabled per org. Applied only with your approval.
The orange ring is always the human checkpoint — the one step Solarus will never take on its own.

Audits that don't lie

The score never moves on a promise.

A merged fix is not a win until a re-audit proves the finding is gone. Until then it counts as open — by design. You always read the truth, dated, not an optimistic forecast.

  • Merged ≠ fixed
    Example: 11 findings were closed by a merged PR. They still count as open until scan #319 confirms they disappeared.
  • Every finding is traceable
    Finding → evidence → PR → re-audit. One line you can follow, end to end, without opening GitHub.
  • Freshness is per repo
    A score is only as recent as that repo's last completed audit. Source drift is named, not hidden.
Example · scan #318
69/100
+11 vs #312 pending re-audit
Trajectory
58 · #312 69 now ≈74
100 − weighted open findings. Merged PRs don't move the score until a re-audit confirms. ≈74 projected if scan #319 confirms the 11 merged fixes.

Example workspace

What the instrument reports.

Numbers you can repeat to your team without opening GitHub. Each one is dated and scoped — a reading, not a boast.

Safe-fix coverage
27/ 51
Findings already covered by an open or merged fix PR on the latest scan.
scan #318 · 3 repos
Mechanical, one-click
12safe
Findings resolvable by a single deterministic token or palette swap.
classified on KP v1.0.4
Audit duration
8:06min
Full scan across 3 repositories and 284 files, end to end.
scan #318 · 284 files
Projected recovery
+5pts
Expected score gain once re-audit #319 confirms the 11 merged fixes.
69 → ≈74 · unconfirmed
Rolling PR review
74/ 100
Average quality of your team's own PRs, reviewed by Solarus over 30 days.
rolling 30d · process health
Auto-merged by Solarus
0ever
Every change is a pull request. None of them merged themselves.
by design · all time
The promise of safety

Every change is a pull request.
Nothing merges itself.

Solarus is autonomous in its measuring and proposing — and deliberately hands-off at the moment that matters. It never auto-merges, never pushes to a default branch, and holds any unclear Knowledge Pack change for your approval. Powerful automation, human control.

audit-fix · customer-app #184 main ← solarus/audit-318/…
42Button.tsx
−color: '#2b2a26'
+color: 'var(--color-text-primary)'
43padding: spacing.3
Example · 4 / 51 findings linked · awaiting your review
Never auto-merged
Example pack

Your design system becomes the Knowledge Pack.

Not a settings file — a structured, versioned model of your tokens, components, import paths and rules. It is the brain every audit runs against, and it stays truthful to a version until it is re-extracted.

  • 64
    Tokens, extracted and named. Colour, spacing, radius and type scales — colour and spacing findings are measured against them.
  • 29
    Components with variants. Canonical components Solarus can recognise — and, where enabled, flag hand-built look-alikes against.
  • 46
    Rules, lifted from your docs. The do's and don'ts your team already wrote in Markdown, kept in one place.
  • 11
    Import paths. Where each component is really imported from — read from your exports, not guessed.
Tokens · extracted · v1.0.4
spacing.scale4 · 8 · 12 · 16 · 24 · 32 · 48
radius.scale6 · 10 · 14 · 20 · full
type.scale.display64 / 48 / 36
v1.0.4
Extracted
7 files
Source drift
audit‑ready
Status

Pricing

Priced like an instrument, not a seat.

You pay for what Solarus watches — repos, PR reviews and governance — not per seat. Start free on one public repo; upgrade when you want continuous, private coverage.

Free
$0/mo
  • ~10 reviews / mo · 1 public repo
  • 1 Knowledge Pack + audit findings
  • No MCP or cross-repo scans
  • No private repos · no fix-PRs
A first look at what Solarus catches — no card required
Request access
Solo
$39/mo
  • Everything in Free, plus:
  • 1 public or private repo · 1 Pack
  • ~10 private PR reviews / mo
  • 1 MCP token for coding agents
  • Starts with a 14-day trial
For a solo dev with one private repo
Request access
StarterRecommended
$99/mo
  • Everything in Solo, plus:
  • Up to 3 repos
  • ~23 PR reviews / mo
  • Reviewable fix PRs, merged by you
  • Up to 3 MCP agent tokens
For a small team shipping continuously
Request access
Team
$499/mo
  • Everything in Starter, plus:
  • Up to 10 repos · cross-repo scans
  • ~69 PR reviews & findings / mo
  • Governance proposals · scaffolding
  • Up to 25 MCP agent tokens
Cross-repo governance for product teams
Request access
Enterprise Custom repo & token volume · enterprise identity · everything in Team · contracted SLA · custom contract · support options · custom onboarding
Contact sales

Token packs — 1M tokens $30 · 5M tokens $140 · 25M tokens $650 · ~43k tokens per review (est.)

Install the instrument

Know the true state of every repo.

Connect a GitHub organization, extract your design system into a Knowledge Pack, and let the first audit run. No score will move until a re-audit confirms it.

One org per GitHub organization · Solarus never auto-merges and never pushes to a default branch.