Interlinked.

For platform teams

Every step is a door.

GitHub grew an economy on top of itself by selling three things at every step of the pipeline: an event, an identity, and somewhere to put the answer. Everything from a faster runner to an AI reviewer is a variation on those three. We are building the same doors, in the same order, on a platform that holds whole folders instead of text files.

Talk to us about an integrationRead the docsNothing is built on this yet. Every row below says which are open.
✓The same pipeline, side by side, top to bottom7 stages

The proven shape

GitHub

The same doors, our shape

Interlinked

git pushLIVE

A commit lands on a branch. Text, and small.

01The act
saveLIVE

A version lands on a project. A whole folder, and it can be 200GB.

WebhookLIVE

Fires on push, pull_request, and about forty more. Signed, retried, replayable.

X-Hub-Signature-256
02The signal
Signed eventNEXT

Fires on every save, publish, retract and membership change. Identifiers only, never content.

X-Interlinked-Signature
Installation tokenLIVE

You act as your app on one repository, never as a human whose password you hold. One hour.

POST /app/installations/:id/access_tokens
03The identity
App tokenNEXT

You act as your app on one project, never as a human. Ed25519, public JWKS, four hours.

POST /token/app
REST and GraphQLLIVE

The diff, the tree, the blobs, the members. Rate limited per installation.

GET /repos/:o/:r/compare/:base...:head
04The read
The read APINEXT

What changed between two versions, the tree at one, and the bytes of any file at any revision.

GET /v1/projects/:id/changed?from=&to=
Your computeLIVE

Your machines, your model, your margin. Nothing of ours runs here and nothing needs to.

05The work
Your computeLIVE

Identical, and deliberately so. The platform's job is to open the door, not to sell you the room.

Checks, statuses, commentsLIVE

Your verdict lands next to the code. A human reads it once, then it scrolls away.

POST /repos/:o/:r/check-runs
06The answer
Statuses, notes and edgesNEXT

Your verdict lands ON the file, keyed to its id so it survives rename and move. Every agent that searches the machine reads it again, automatically.

POST /v1/projects/:id/notes
Required checksLIVE

A failing check blocks the merge. The repository decides which of yours are required.

07The gate
Required statusesNEXT

A failing status blocks the save, refused inside the push hook before a byte is written.

Stage 06, and the reason to bother

On GitHub your answer is a comment somebody reads once. Here it is context every agent reads again, on every search, forever.

Notes and edges are keyed to a file's id, not its path, so they survive rename and move. They cascade from a folder to everything inside it. And they ride along automatically on the searches an agent is already running, deduplicated and terse. That is a different economics for an integration: your output stops being a notification and starts being a fact about the project.

Who builds on doors like these
Build computeCode reviewSecurityAsset pipelinesMedia reviewComplianceAgent context
and 23 more · 112 companies surveyed · 14 surfaces

Worked traces

Three shapes of company, and the doors each one opens.

Named for the category, not claimed as customers. Nobody has built on this yet, which is the whole reason this page exists.

Build compute

the Blacksmith shape

You replace the slow half of somebody's pipeline and hand the artifacts back.

Hear the save, read what changed, run it on your own metal, write the artifacts back as a new version and post the status the gate reads.

01020304050607

Review and analysis

the CodeRabbit shape

You read what changed and leave the verdict where it will be read again.

Hear the save, pull the diff at that revision, form an opinion, and attach it to the files it is about. On our side that opinion keeps working after you leave the page.

01020304050607

Asset and media pipelines

no GitHub equivalent

The category that cannot exist on a host that only holds text.

Validate a 4GB build, transcode a plate, check a CAD assembly, flag a licence on a texture. The folder is the unit here, which is why this lane opens for us and not for them.

01020304050607

Why bother with a second host

Same doors. Different building.

It is a folder, not a file tree of text

Fragment-deduplicated versions of 200GB of assets, with range reads and no full-history clone. That opens categories a text host structurally cannot serve: game and DCC pipelines, media review, CAD and PLM, digital asset management, legal matter folders. Eight of the thirty categories we counted have no GitHub equivalent at all.

Your output compounds instead of scrolling away

The write-back slot is the notes and edges layer, which is already what every agent on the machine reads on every search it runs. An integration's verdict is not a notification here, it is a durable fact about the file, surviving rename and move because it is keyed to the file's id.

One price, and no seat tax on your users

$5.99 a month, storage and transfer, any team size, the space owner pays. Nobody has to buy a seat to install your thing, and the local tool the integration sits next to is free forever. Your addressable base is not gated behind our upsell.

The surfaces

Everything you can reach, and what is open today.

Twelve surfaces, reduced from a survey of a hundred and twelve companies across thirty categories. Six of them cover about eighty five percent of what anyone actually needs.

POST /token/appAn app token scoped to one install. Never a human's credential.NEXT
Webhook deliverySigned, retried, and replayable after your outage.NEXT
GET /v1/installsEvery project you are installed on.NEXT
GET /v1/projects/:id/versionsThe version history, newest first.NEXT
GET /v1/projects/:id/changedWhich files moved between any two versions.NEXT
GET /v1/projects/:id/tree?at=The full tree at one revision.NEXT
File bytes at any revisionRange reads and whole-folder tar, straight from the store.LIVE
POST /v1/projects/:id/notesAttach a note or an edge to a file, folder or version.NEXT
POST .../versions/:rev/statuspending, pass or fail, with a URL. What the gate reads.NEXT
GET /v1/projects/:id/membersWho has access, at which of the five rungs.NEXT
Write a versionCommit as the app, attributed to the app in history.NEXT
Usage per installWhat your integration cost, so nobody is surprised.NEXT

LIVE means it answers today. NEXT means it is specified, scheduled, and has no unknowns left in it.

The ask

Tell us which door you would walk through first.

The surfaces above are specified and the order is set. What we do not have is the first integration telling us we got the shape wrong. If you build on source hosts and any of this looks close, we would rather hear it now than after it ships.

[email protected]What it costs