RUTLI Become a Founding Node

A line, and what stays on each side of it.

Sharing capacity never means sharing your machine. The private plane holds what is yours; the network plane holds sealed work you agreed to run. The line between them is the whole design.

The private plane. Yours.

  • Your files, your records, your books
  • Your local knowledge and your agents' memory
  • Your home and business telemetry, audio, video
  • Your credentials
  • Anything that needs local inference

The network plane. Shared by your policy.

  • Sandboxed workloads, signed and verified
  • No access to the host's files
  • Limited to the resources you set
  • Interrupted at once by anything of yours
  • Attested where the hardware allows

Sovereignty at three scales: a person's machine, an organisation's building, a region's capacity. The same line runs through all three.

Six rules the node keeps.

A workload is a sealed box

Every network job runs in a sandbox sized by you: memory, GPU share, time, network. It cannot see the host's files, your other processes, or your LAN.

PLANNED

Signed, or it does not run

Workload artefacts are signed by their publisher and verified by your node before a byte executes. Unsigned work is refused.

PLANNED

Your task wins, at once

A local task preempts network work immediately. The job is interrupted and later resumed elsewhere; you never wait for it.

PLANNED

Keys, never addresses

A node is its key. Nothing on the network is trusted by where it connects from, and nothing needs a port opened on your router.

PLANNED

Attested where the hardware allows

Where a machine can prove what it runs, the network uses it; where it cannot, the workload class is limited accordingly.

RESEARCH

Encrypted end to end

Node to node, node to control plane, always. The control plane sees scheduling, never your data.

PLANNED

What is not solved yet, said plainly.

Isolation on Linux is containers and, where present, virtual machines. On Windows and macOS the first releases will say exactly what the sandbox is and is not, and will limit the workload classes those machines accept until it is as strong. Fraud, spoofed capability, and verification of completed work are engineering problems the network takes on in order, and each one is labelled here as it is done.

PLANNED RESEARCH