Docs
Desktop app · Zero-knowledge · Beta opens September 1, 2026

Point it at your repo. Get a verified map, module by module.

Sphoton reads your codebase and database schema, drafts what each module does — with file:line evidence — and has you confirm every fact.

Sphoton module detail — Journey Ribbon with overview card, fidelity score and entities

One module in Sphoton. Every fact on this screen was AI-drafted, human-approved.

Before you go deeper

Three things worth knowing.

AI drafts. You ratify.

shipped

Every finding arrives as an assertion: a claim, a confidence score, evidence one click away. Nothing becomes knowledge until a human says so.

It runs on your machine.

zero-knowledge

No upload, no mirror, no server-side index. Content is encrypted under a per-workspace key before it leaves — the server stores ciphertext it can't read.

And it stays true.

drift-flagged

Import a schema change that touches a certified module and it flips to Stale until re-verified — along with everything derived from it.

One question, then we start

Which one are you?

The walk is the same either way — but we'll be honest about the shape Sphoton serves best.

Arrow keys move the walk · click anywhere to advance
Why this exists

Three people you already employ.

01 Mike · the new hire 02 Bob · the one who's leaving 03 Alice · the one who explains
Act one
Mike
Software Engineer III · day 4

Hired for skill. Stopped by the one thing the repo doesn't contain.

payments-monolith6 tabs open
Payments — architecture overviewstale
last updated 11 months ago · author has left the company
Half of this is still true. Which half?
Mike if I change the tax rate, does anything in invoices change?09:14
3 hours
#dev-help not sure — ask Bob, he'd know12:31

Full salary, every week, while he rebuilds a picture three people in the room already have.

To do
PAY-131 · refund note
PAY-140 · retry job
In progress
PAY-118 · locale rounding
Mike · week 6
Done
merged · 2 tests · 1 review
What Bob knowsnot in the repo
Handover · session 1 of 3
90:00recording

Covers what he remembers to say — not what he knows.

100%
Bob
"change that and the cache and pricing move too"
82%
senior
"it touches the cache, and something in pricing"
61%
dev
"clear the cache after, I think"
44%
Mike
"there's a cache somewhere"
INC-2841production
Locale change double-charged 1,900 invoices.
change shipped3 days quietcustomer calls9 days to find it2 hours to fix
Mon Alice — does Notifications read from Ledger or Billing?Raj
Tue quick one — what writes to the tax table?Mike
Thu is the cache safe to clear during publish?Sara
Fri sorry, same question as Raj — Notifications or Billing?Dan
0 min
a day, answering questions she has already answered
— a week— a yearof your most expensive engineer
agent sessiontoday · 14:02
context window · re-explaining five modules0% used
Every session starts at zero.
the approach is built on a module that changed last sprintWrong from the first line.
Dev→QA→bug: missed module→back to BA→Dev again→QA again→release

Nobody made a mistake. One fact this team already owned wasn't where it was needed.

MikeBobAlice
one problem

The first ten minutes

Watch the loop run. Then it's yours.

  1. 01Name a module
  2. 02Find its tables
  3. 03Read the code
  4. 04Ratify the facts
  5. 05Keep it true
Name a module.

A module is a piece of your system a human would name out loud — not a folder.

Nothing is uploaded in this walkthrough — or in the real app.
It proposes the tables that anchor Translation.

Ranked by confidence, ambiguous calls flagged, not hidden. You can include or exclude any of them — the module is yours.

It reads your code. Locally.

An agentic loop with read-only, sandboxed tools. Watch what's missing from this log: an upload step.

It proposes. You ratify.

Every claim carries a confidence score and evidence. One of these five is wrong — that's the point.

Fidelity — five dimensions
0 of 5 resolved
A module that stays true.

Accepted knowledge rolls up into the working views — and the score stays honest about what the code never said.

Translation

Certified
74fidelity
4tables
5facets
2signatures
ScreensFacetsEntry pointsDiagramMapped files

Knowledge at altitude

As much as you need. Never more.

Who's reading
Token budget
Overview

One paragraph, three vital signs

~180 tok
Translation turns source strings into locale-ready copy for 14 markets — ingest, resolve, publish, and the cache that keeps it fast. Fidelity 74 · 4 tables · 5 facets. Enough to orient anyone in ten seconds.
Facets

Five named aspects, with relationships

~1.2k tok
Named aspects and how they relate. A facet that can't point to concrete evidence is rejected at write time.
Ingest & glossaryFallback resolutionLocale publishCache invalidationGap tracking
Detail

A recursive tree under each facet

~9k tok
Drillable as deep as the module genuinely goes — every diagram rendered from stored facts, never drawn by the model.
Locale publish ├─ LocalePublisher.Publish(localeId) Publish/LocalePublisher.cs:64 │ ├─ writes through PrecomputeCache human-confirmed │ └─ invalidates the CDN edge key human-confirmed ├─ diagram · publish sequence rendered from facts └─ gap · rollback path absent in code flagged, not guessed
Sphoton facets graph — radial semantic-zoom view of a module's facets with relationship edges

The same module, one level deeper: facets and labelled relationships, deterministically rendered.

One app, four dimensions

Everything orbits the knowledge.

Zero-knowledge by construction, not policy

Every guarantee, then its limit.

The encryption core was milestone one, never retrofitted. Each card shows what we guarantee — then turns over on its own to show what we won't claim.

We're closed source today with no published audit, so don't take "no decrypt path" on faith — verify what you can: watch the traffic; analysis calls go only to api.anthropic.com, and your key sits in your OS keychain. 500+ backend tests stay green behind the crypto core. We'd rather you know precisely what you're trusting.

Why we exist
Clarity over inference.
Mission

Capture and immortalize the verified understanding of every system.

Vision

A world where system knowledge never walks out the door.

From the founder

Why I'm building this.

TG
Tanmaysinh Gharia
founder · building Sphoton

"I can understand anything accurately, in real depth — I just can't remember all of it. Neither can the AI. That is the whole problem: the understanding is real, and then it is gone, or quietly out of date.

So the persistence of that understanding, its accuracy, and its freshness — that is exactly what this application manages. Not AI-inferred; human-validated, evidence-backed, and refreshed when the code moves.

If that's your world, the beta is for you: tell me what breaks. I read every reply."

LinkedIn →
Beta opens September 1, 2026

Free to know your own codebase.

Every tier is BYOK — your own Anthropic key, your direct bill, no token markup. Nothing is billable today; there is no checkout, and that's honest.

Explorer
$0/ forever

One repo, the full living-knowledge engine. Not a trial.

  • One repository
  • Analysis, verification, layered modules
  • Drift flagging
Pro
$15/ mo

The full toolkit for one serious builder.

  • Unlimited repositories
  • Blueprint & Traverse
  • Personal Knowledge Gateway beta
Recommended
Team
$30/ seat / mo

Shared living knowledge under shared-key cryptography — the shape most product teams need.

  • Roles: owner / senior / dev / viewer
  • Live co-editing locks
  • Certification: two signatures
  • Team Gateway beta
Enterprise
Custom

Self-hosted Gateway, enterprise controls, guided rollout.

  • Self-hosted Gateway
  • Prototype days → pilot UAT → org-wide
  • Enterprise controls

Stop re-explaining your system.

You're on the list — invite en route.

No download, no card, no demo call — the waitlist is the whole funnel, on purpose. Founding users keep these prices for life.

© 2026 Sphoton