Compute you control

Today, serious compute means a cloud account and a landlord. The pieces on this page are Tixim’s answer: make strangers’ hardware safe to use and strangers’ workloads safe to host — then nobody needs the landlord.

The baseline never changes: everything in Tixim is just an instance with the right service, and it runs anywhere — a laptop, a homelab, a rented box. tix.computer Horizon is the managed home for the instances you’d rather not babysit: high availability and privacy by default, registered on Sui like every other endpoint — and with nothing about it you couldn’t run yourself. Convenience, not lock-in.

tix.build: your idle hardware, safely Building

The guild system is what makes lending hardware sane. As a guild compute member your machine:

• builds only from releases signed by the maintainer’s dWallet — never from unreviewed pushes;
• runs every job inside the same sandbox stack the platform uses for its own agents — rootless containers, Landlock-enforced closures, filtered egress by default, with user-submitted builds moving to MicroVM isolation, and to trusted compute where it’s available;
• is judged only on reproducibility: deliver the same bytes as the other guilds’ machines, independently. There is nothing to “trust” about your box, and nothing your box must trust about the job;
• earns budget shares, commission, and epoch emissions for the work.

Honest hardware failure is survivable — the fault model penalizes bets, not delegators, and only patterns of divergence or outright double-signing cost real stake. Idle machines become the network’s build farm, without anyone accepting the classic “run arbitrary code from the internet” deal.

Distribution without a gatekeeper Building

Certified builds land in the decentralized Nix cache — NARs on Walrus, the index on Sui, standard signatures for stock Nix clients. A package built by guilds is fetchable by anyone, forever, without a cache operator to please or lose. And because packages are signed end to end, serving them is as safe as lending build cycles: an ISP can put an old machine on a shelf, start a cache instance, and subnet discovery turns it into the neighborhood’s package mirror — Walrus holds the root copy, iroh finds the nearest one. Horizon

The horizon: a confidential cluster of user instances Horizon

The goal this all points at: user-controlled instances of HyperEnclave — an open, cross-platform trusted execution environment — forming a global cluster that belongs to its users:

• Anyone can contribute an instance. Your machine hosts other people’s workloads inside enclaves it cannot read; their machines host yours the same way.
• Admission by trust circle, not allowlist. An instance joins the cluster when a personal trust circle of guilds has verified it — the same t-of-n human-rooted mechanism that already guards keys and certifies builds, extended to vouching for machines.
• Run and autoscale on demand. Need ten instances for a heavy workflow tonight and zero tomorrow? Spin them up from the pool, pay per use in TIX, wind them down. Capacity follows your workflows instead of your provisioning spreadsheet.
• Experiences feed back. Every scaled run posts its experiences — so the cluster does not just execute the network’s experts, it continuously improves them.

None of this exists yet — that is why it wears the Horizon badge. But every prerequisite is the same machinery described on these pages: guilds put stake behind claims, trust circles root trust in people, reproducibility makes hardware interchangeable, and the network gives it all identity, storage, and payment rails that no single company can switch off.

The singularity worth wanting is not one datacenter that thinks. It is a million machines their owners understand, composed into something no one controls and everyone can use.