Surfil
// customers

Early product. Honest page.

We're not going to render a wall of logos we don't have. Here's who Surfil is built for, the proof model that replaces testimonials, and what working with us early actually gets you.

surfil verify rcpt_8f2a
Signed savings receiptVALID
receiptrcpt_8f2a
typeprefix-cache + prune
saved48,200 tokens
measuredbefore / after
signatureed25519:… (epoch 7)
verifiedoffline · no account
Run surfil verify on any receipt - the signature is the proof.
What you can already verify

Four facts that don't need customers to vouch for them

Each one is architectural - checkable from the product itself, today.

byte-exact
never busts your prompt cache
Ed25519
every paid output signed
0
lines of source leave the device
byte-exact
clean uninstall, verified
Who it's for

Built for four situations

If one of these is yours, Surfil was designed around it.

Solo developers

You run two or more agents, the token bill creeps monthly, and you'd like one number - measured on your repos - that says what's recoverable.

See the fit →

Small product teams

Mixed agents across the team, no shared cost view, and a security-minded lead who wants tool-calls simulated before anything is enforced.

See the fit →

Platform & DevEx teams

You standardize tooling for many developers and need one install, one interception layer, and cost that stays flat per user.

See the fit →

Regulated organizations

Agents are blocked until someone can prove what leaves the box. Zero-trace plus offline-verifiable evidence is the unblock path.

See the fit →
The proof model

What we show instead of logos

Social proof asks you to trust other people's judgment. Signed proof asks you to run one command.

A logo says someone bought it

A signed receipt says the product did what it claims - measured on real traffic, verifiable by anyone, offline, with no account.

A quote says someone liked it

The offline verifier says the math checks out. surfil verify runs against a public key; this website is not in the loop.

A star count says it's popular

A byte-exact uninstall says trying it is free of risk: every agent config restored exactly, zero residue, verified.

Early teams

What being early is worth

The trade is explicit: you get outsized influence and attention; we get the measured, publishable results this page will eventually hold.

Direct line to the builders

Early teams talk to the people writing the runtime, not a success layer. Feedback lands in the build order, visibly.

Your constraints shape the gates

Products ship in a gated sequence. What early teams need moves gates - that's the leverage of being early.

First published case studies

When you're ready to publish, your case study is measured and signed - the first real names on the /cases page.

Put your name here first

Install Surfil, measure a week of real traffic, and if the receipts earn it - publish the first real case study on this page.