CELAUT For final users

Service users

Run it.

Pay for what it used. Nothing else.

Launch a service on a node, get the result, pay for the compute it consumed. There's no account to create, no subscription to cancel, and no company sitting between you and the machine that did the work.

  • No account nothing to sign up for, nothing to be locked out of
  • Per execution you pay for the computational resources actually used
  • Isolated services run sealed, and see nothing they were not given

Tap any underlined word for a plain-language explanation. Turn them off any time with the button in the corner.

The idea

Ask the network, not a company.

You want something done — a model run, a sequence analysed, a bot traded, a file processed. Today that means picking a provider and opening an account with them.

Nodes answer directly.

Celaut has no central service registry. Services are distributed across nodes peer-to-peer, and nodes declare their supported interfaces and accepted payment methods on contact — so nothing has to be agreed with anyone in advance.

You deal with the machine that does the work.

Your node negotiates the execution cost with a peer and the work happens. There is no platform in the middle taking a cut, setting the rules, or able to remove you from a network you never joined.

No signup. No subscription. No middleman.

Benefit 01

How do you know what actually ran?

With a hosted service you can’t. The operator can’t prove the system hasn’t changed — so when a tool gets popular, nothing stops its performance quietly dropping to save costs.

Here, the service is its specification.

A service specifies its entire environment — architecture, filesystem, entrypoint, config. Change any of it and it is a different service, not a silent update to the one you were using.

So the result is reproducible.

Given the same inputs, a service always produces the same outputs, regardless of which node executes it or when. That’s what makes a reputation record from months ago still worth something today.

Determinism is the guarantee. Not a promise — the design.

Benefit 02

Your request is nobody else’s business.

When you send a workload somewhere, the honest question is who else gets to see it on the way through.

Every execution is isolated.

The node runs the service as an isolated instance — its own virtual machine. By default a service is cut off from external networks entirely, able to talk only to its parent, its children and the node running it.

And the developer isn’t on the other end.

Service developers cannot control, modify or extract data from a service, because they don’t control the nodes that distribute and run it. Any wider network access has to be declared in the specification, in the open, before you ever run it.

Isolated by default. Access is requested, never assumed.

Benefit 03

You pay before it runs. Full stop.

Users launch services on nodes and pay up front for a promise of resources. That’s the entire commercial relationship.

Nothing accrues while you’re idle.

There is no seat, no tier and no monthly floor. Payment is taken beforehand in exchange for resources to be consumed; proof of payment gates access. The node’s guarantee is its reputation, not a bill at the end.

Priced by a market, not a pricing page.

Nodes set their own costs and compete on them, and services have a marginal cost of zero — the cost of running one falls on the node — so many start free to build reputation. Payment systems sit outside the core architecture, so which ledger settles it is not fixed either.

Pay per execution. Leave whenever. Nothing to cancel.

What you actually get

No infrastructure to manage

The nodes handle it. There is no cloud provider to choose, no machine to keep alive, and nothing to leave running between uses.

No configuration

The service specification already covers how the container is built, the architecture it needs, its network requirements and its interface. None of that is yours to work out.

The developer has no reach

Service developers can't control, modify or extract data from a service — they don't control the nodes that distribute and run it.

It can’t change under you

A service is deterministic: the same inputs produce the same outputs, whenever and wherever it runs. Nobody can quietly throttle it to save costs.

Judged by reputation, not ranking

Reputation lives as records on a ledger, and each participant weighs the sources it trusts. There is no editorial front page deciding what you see.

Nothing to be removed from

Discovery is peer-to-peer with no central registry, so there is no account to suspend and no listing to pull.

From “I need this done” to a result

  1. Find the service

    Search by the problem you want solved. Nodes discover services peer-to-peer, and registries like Unstoppable Skills map problems to the services that cover them.

  2. Request an execution

    Your node talks directly to a peer that can run it. Interfaces and accepted payment methods are declared on contact, so nothing has to be agreed in advance.

  3. It runs, sealed

    The node executes the service as an isolated instance — its own virtual machine — with no access beyond what the specification asked for.

  4. Pay up front

    A node is paid beforehand for a promise of resources, with proof of payment gating access. Reputation is the guarantee. No subscription, no minimum, no standing bill.

Against the two options you have today

Take a trading bot as the example. Right now you either hand your portfolio to a web service, or you find the source and run it yourself. Each choice buys you one thing and costs you another.

Use a web service

GainsYou run no infrastructure and configure nothing.

CostsYou can't attribute reputation to it, because the operator can't prove the system hasn't changed — and can't assure you your request data isn't misused.

Run the source yourself

GainsIt's deterministic, and the developer has no control over your request data.

CostsYou need hardware capable of running it, and you have to deal with the configuration — which is usually where people give up and go back to option one.

Use a Celaut service

GainsNo infrastructure, no configuration, and the developer still can't control, modify or extract data from the service.

CostsYou pay per execution, and you depend on the network having a node willing to run it at a price you accept.

The other people in the network

Someone wrote the service and someone's machine runs it. Both roles are open to you too.

Node maintainers

They provide the hardware that executes what you request, in exchange for payment — without needing to know what the service does.

Have spare hardware? →

Service developers

They write services that any compatible node can run, and hand them to the network rather than hosting them.

For developers →

The paradigm

Nodes, services, specification, and the reputation and payment systems that let parties who don't trust each other still cooperate.

Read the paper →

Start from the problem you have.

Unstoppable Skills is a fully on-chain, serverless registry where the problems themselves are the protagonists. Search for a skill and find the services that cover it, real comparative benchmarks, discussion, and reputation-based ranking.

↑ Top