+FOR MODEL OPERATORS

Share the model.
Choose the circle.

Offer inference to peers you trust. You decide which model is available, which identities can connect, and where access ends.

Your modelOperator-controlled
Pinned identity
Authorized peer
Explicit trust boundary
+PERMISSIONED BY DESIGN

Trust is configured.
Access is intentional.

Cairn’s current peer network is permissioned. Operators select the models they offer and verify the identities of peers they allow.

Signed identities support authentication. They don’t prove that a provider runs a model in a confidential environment.

Explore the security modelRepository access required
+THE OPERATOR WORKFLOW

Three choices.
A clear boundary.

Configuration and control stay local.
The website is just your starting point.

01

Pick what to offer.

Select an existing model and configure the provider endpoint. Cairn ships without bundled models.

02

Pin who you trust.

Verify the peer’s signed identity and explicitly configure which identities are allowed to use your model.

03

Review before you run.

Validate configuration in the local operator console, inspect a route receipt, and start your router or peer separately.

THE LOCAL OPERATOR CONSOLE

A place to check
your next move.

Validate configurations, save local drafts, inspect routing, and export eligible free configurations.

The console runs separately at 127.0.0.1:8788. It does not start providers, sign wallets, or send payments.

Console setup for invited testers
operatorILLUSTRATION
ConfigurationValidated
Model aliaslocal-chat
AccessPinned peers
ROUTE RECEIPTYour choices, made visible.
Local drafts · Free configuration export
ON THE HORIZON

Toward direct payments for inference.

Quotes, capped authorization, metering, settlement, and refunds are being tested in isolation. Public-chain payments and wallet signing remain disabled.

See the beta status
+YOUR MACHINE. YOUR DIRECTION.

A better route starts here.

Explore the possibilities. Keep the decisions on your machine.

Try the routing demo