Once the understanding forms,

it never leaves the system.

Product knowledge layer

Sphoton turns
your codebase into a
certified knowledge map
of your software.

  1. 01

    Built module by module.

    src/billing/invoice.tstax.tscredit-note.ts
    Billing & Invoicesmodule · 3 files

    purposedatabehaviourboundariesimpact

  2. 02

    Certified by your engineers.

    Each module is signed by the engineer who owns it, at a named revision. When the code moves, it goes back to needs review.

    Paymentssigned by Alicerev 14

  3. 03

    Then knowledge consumed by

    Your teamin the appAI agentsover MCPpeople and agents.

The problem · four short films

What problems do we actually solve?

Each film follows one person for about ninety seconds. Watch them in order, or start with the one that sounds like your team.

Now showing

Four short films, about six minutes.

S1 starts in 5or choose a film
S1the new hirefilm in production
Security

We can't read your record. That is the design.

  • Argon2idkeys from your password
  • AES-256-GCMencryption on your device
  • RSA-4096a key per teammate
Your machineholds your password, your key and the readable record
Password
Argon2idpassword + salt
your key stays here
Billing & Invoices
  • Password
  • Key
  • Readable record
Sphoton's servershold sealed blocks, never a key
?no key on this side
  • Ciphertext
  • No key
  • No password

01You type your password. It never leaves this machine.

Your machine readableciphertext only Sphoton's servers

Your record is readable on your machine. What reaches Sphoton's servers is ciphertext.

Drag the seam. Anything that crosses it is sealed on your device first. Nothing crosses back unsealed.

  1. 01

    Your password never leaves your device.

    Keys are derived from it on your machine (Argon2id). We store nothing that yields them.

  2. 02

    Everything is encrypted before it is sent.

    AES-256-GCM, on your device. Our servers hold ciphertext only.

  3. 03

    Your code is read where it lives.

    The desktop app reads your repository locally. It is not uploaded to us.

  4. 04

    Your model keys, your model bill.

    Calls to your AI provider go out under your own key.

  5. 05

    The agent runs on your infrastructure.

    Commander is deployed by you, inside your network.

  6. 06

    Teammates get access by key, not by our permission.

    The workspace key is wrapped to each member's own public key (RSA-4096).

What we can see

Your email, who is in your workspace and their roles, counts and timestamps, your billing.

What that costs you

Lose your password and your recovery key together and nobody, including us, can open your record. Keep the recovery key somewhere safe.

Pricing

Pay for the roles you have.

Your own model keys. Sphoton never bills you for tokens.

two members or more

Team

Each seat is priced by its role, from Business reader to Admin. Commander joins as one more seat.

from$10per person · month
one developer, whole product

Lone wolf

You are the whole hierarchy. One price.

$200per month, flat
two members or more

Team

Priced per person, per month

Admin
$35
seats, keys, environments
1
Senior engineer
$30
certifies modules, signs off
1
Engineer
$25
builds against the certified map
4
QA
$20
confirms and verifies test cases
1
Rule author
$15
writes the business rules
0
Business reader
$10
reads the map, no code
1
one developer, whole product

Lone wolf

Every role is yours, priced as one

Admin
$35seats, keys, environments
Yours
Senior engineer
$30certifies modules, signs off
Yours
Engineer
$25builds against the certified map
Yours
QA
$20confirms and verifies test cases
Yours
Rule author
$15writes the business rules
Yours
Business reader
$10reads the map, no code
Yours
Onboarding

From the first call to live, in about six weeks.

Seven steps, each with a clear finish line. As a beta firm you get closer support, and we ask for your feedback.

0045 min

Discovery call

We learn your system and agree a pilot area.

Beta agreed, kickoff booked
01Days 1–5

Kickoff and setup

Scope, success criteria and owners agreed. Workspace, seats and keys set up.

Pilot team signed in
02Weeks 1–3

Delivery

Pilot modules mapped and certified by your engineer. Commander connected.

Pilot ready to test
03Week 3–4

Testing and training

Your team tests agreed scenarios. Every seat gets a short session.

Acceptance signed off
0460 min

Go / no-go

We check the criteria together and decide on evidence.

A written decision, same day
052 weeks

Hypercare

Every bug or request answered within 24 hours.

Five calm business days
06Ongoing

Onboarded

Reviews at 30, 60 and 90 days. Your feedback shapes the roadmap.

Value confirmed
Book the first call →Read the onboarding guide →Read the docs →
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."

Write to me →LinkedIn →
Shortcuts

Anything else you need?

SupportGet help with the betaWrite to us. A person replies, usually within a day.Talk to usBook a 30-minute callWe walk through Sphoton on your own code.SecurityHow your record stays yoursEncrypted on your machine. We hold ciphertext only.PricingSee the two plansTeam, priced by role. Lone wolf, one flat price.

tanmaysinh.gharia@sphoton.io

© 2026 Sphoton · sphoton.ioBack to top