Surfil
// solutions

Same spine. Three ways in.

Surfil installs the same way for everyone - what differs is where you start. Choose by team size, by the problem you're solving, or by your role, and get the order of operations plus the first receipt to expect.

surfil · your control plane
▤ Saved / mo
$412
⛨ Blocked
27
≋ Memory
94%
Savings trendsigned
Trend, last 12 points
rcpt_8f2aepoch 7 · offlineVALID
!AWS key in payloadacme/apiblocked
By team size

Solo, team, or platform org

Each is a sequence, not a bundle: what to turn on first, second, third - and the signed artifact that tells you it's working.

By problem

Start from the thing that hurts

Four common problems and the chain of products that removes each one - ending in a signature you can verify.

By persona

Start from your role

Four roles, four jobs-to-be-done - each with what you turn on first and its own call to action.

What never changes

Every path gets the same guarantees

Where you start changes the rollout, never the invariants.

Zero-trace

Source stays on each developer's device - solo or five hundred seats, no exceptions to it.

One layer

One interception point per machine. Scaling up never means stacking a second proxy on top.

Signed proof

The solo dev's receipt and the platform org's evidence bundle verify with the same offline command.

Flat cost curve

Devices do the heavy work, so the per-user cost doesn't bend upward as the fleet grows.

Not sure which way in is yours? Start on Starter as if you were solo - the spine is the same, so nothing is thrown away when the team, the problem, or the role grows into more.

Turn on the first stage today

The install is reversible byte-for-byte, and the first signed receipt arrives after one normal week of traffic.