FABRIC LIVE · OWNER CONTROLLED

Your machines.
Acting as one.

Rampage turns the computers and edge devices you already own into a private compute fabric, qualifies local AI automatically, serves it through OpenAI, Anthropic, or OpenRouter-style clients, proves useful capacity with signed execution receipts, visibly assists an opted-in paired Windows worker, and makes broken pairing recoverable in two clicks.

Download Rampage for Windows See how it works

Unsigned Windows x64 release candidate · SHA-256 hashes published

GPUleased

CPUready

CASresume · repair

AIpropose

3AI API surfaces

47.7M/ssigned live hash proof

QUICdirect private mesh

0AI authority grants

STOPlocal + epoch fenced

THE FABRIC ARENA

See your compute.
Command it without surrendering it.

A spatial live view for intuition. A keyboard and screen-reader-friendly Ops Grid for precision. Both are projections of the same evidence-backed state.

Rampage Fabric Arena showing a command rig, live CPU and memory telemetry, policy status, and evidence controls — Native packaged desktop · system-tray lifecycle · local discovery · policy explanation · evidence trail

THE SHIFT

The hardware is already there.
The missing piece was trust.

Pool useful work

Move complete jobs to the right machine. Split independent evaluation, search, preprocessing, and rendering into atomic shard sets.

Lease exact resources

CPU, VRAM, RAM, storage, runtime, thermal, and power capacity become scoped capabilities—not permanent ambient permission.

Move sealed artifacts

Donated drives become encrypted content-addressed capacity with restart-resumable frames, signed possession challenges, and bounded autonomous repair.

Demand receipts

Every accepted job returns a signed result. Every transition lands in a recoverable, hash-chained evidence ledger.

NATIVE FROM FIRST CLICK

Download it.
Build your fabric.

Rampage is a real desktop application, not a dashboard wrapped around a pile of manual daemons. The shell owns its governed sidecars, local discovery, tray lifecycle, startup behavior, STOP path, and clean shutdown.

WINDOWS X64 · 0.3.1 RECOVERY CANDIDATE

MSI + NSIS

The installer creates the desktop launcher, bundles the governed services, qualifies a pinned local AI runtime, and hands ongoing control to the role-aware system tray.

Signed sustained-compute receipts
Optional paired-owner Remote Assist
Unsigned until Authenticode credentials exist

LINUX X64 · FRESH RUNNER GATE

Debian + AppImage

The same Tauri shell and Rust/Python sidecars are assembled on Ubuntu 24.04, staged with SHA-256 checksums, and bound to the exact source revision in a distribution manifest.

No cross-compiled portability claim
Native GTK/WebKit build environment
Stable signing remains channel-specific

MACOS ARM64 · FRESH M1 GATE

App + DMG

Apple Silicon candidates are built natively on macOS 15. Stable publication additionally requires a real Developer ID, notarization, Gatekeeper acceptance, and a stapled ticket.

Native sidecars and generated icon set
Unsigned candidates stay candidates
Stable credentials fail closed

01InstallLaunch from the desktop shortcut.

02CreateChoose “Create my fabric” on the owner PC.

03FindThe laptop waits nearby. Nothing is copied, typed, or configured.

04ApproveThe main PC detects the laptop. Approve that device once; enrollment and contribution are automatic.

Rampage laptop onboarding with Join your fabric selected and a single Find my fabric action — No terminal · no account · no IP address · no invitation to copy

Rampage owner grid with a paired Studio Laptop selected and explicit View desktop and Control desktop actions — One visible session per worker · 30-second signed lease · pinned paired owner · worker toggle + STOP revoke

Rampage Recovery Center with Fix Rampage, enrolled machines, stale-device Forget, and factory reset — Repair in place · pair again · revoke stale identity · typed bounded factory reset

This Remote Assist image is a source-current showcase with labeled demonstration topology, not a physical two-machine receipt. Windows capture/input, lease, digest, replay-fence, and UI contracts are tested separately. Rampage cannot cross UAC, the lock screen, the secure desktop, or higher-integrity applications.

Windows 10 remains an explicit real-machine gate: the dedicated self-hosted workflow must prove the operating-system caption, installer, desktop launcher, tray lifecycle, sidecars, restart behavior, STOP, and uninstall. A Windows Server build is useful candidate evidence; it is not relabeled as Windows 10 proof.

RAMPAGE EDGE

Useful compute.
No pretending.

Phones and tablets do not become network VRAM. They become native, owner-controlled contributors for small work that is safe to interrupt and retry—freeing expensive machines for the workloads only they can run.

OWNER INTENTForeground onlyLeaving the app clears donation and the screen-awake state.

POWER FLOOR40% or chargingLow-power mode pauses contribution automatically.

THERMAL FLOOR35% headroomMissing or pressured telemetry denies the next pulse.

AUTHORITY WINDOW20-second offersFresh signed, one-shot, epoch-fenced leases still decide every claim.

Native signal→Signed offer→Governor lease→Signed receipt

Exact source allowlist: CPU hashing and independent evaluation shards. No model server, shell, protected storage, public marketplace, background daemon, console package, or policy-widening authority.

Inspect the mobile trust contract Read the qualified build evidence

Rampage Edge mobile interface showing foreground status, battery and thermal telemetry, signed receipt count, lease pulse, STOP, and hard capability boundary — Labeled browser showcase state of the real interface · native packages supply Kotlin or Swift telemetry

DESIGN GRAPH

Intelligence above.
Authority below.

Rampage has a narrow waist: the signed capability lease. Everything smart can improve above it. Everything powerful can diversify below it. Neither side can wish policy away.

ULTIMATE AUTHORITYHuman ownerArena · Grid · CLI · SDK

PROPOSALS ONLYIntelligence planeDBOS · Pydantic AI · memory

typed intent

CONTROLControllerschedule · recover · reconcile

→

TRUST KERNELGovernorpolicy · signatures · durable fencing

→

NARROW WAISTCapability leaseexact · scoped · expiring · one-shot

authenticated QUIC

NODE 01Command rigGPU · CPU · Ollama

NODE 02Spare PCshards · cache · storage

EDGE CLASSSmall devicebounded foreground work

DATA PLANEEncrypted artifact fabricresume · repair · receipt

EVIDENCE SPINEHash-chained ledgerleases · receipts · recovery

OUT-OF-BANDIndependent STOPno model · network · controller

COMPUTE STRATEGY

Automatic first.
Four clear outcomes.

Rampage assigns technical roles from signed device, runtime, link, power, thermal, and workload facts. People choose the outcome, not a settings maze.

RECOMMENDED01

Automatic

Measure every device and path, then continuously choose the safest high-value role.

CAPACITY02

Biggest AI

Fit the largest qualified model; use cross-node layouts only when an engine-specific campaign passes.

INTERACTIVE03

Fastest AI

Reject slow peers and optimize whole-model, replica, prefix, speculative, or split-phase lanes by proof.

CONCURRENCY04

More Work

Spread independent users, agents, builds, renders, evaluations, and batch work.

FOREGROUND FIRST05

Protect This PC

Evacuate background work and preserve the game, call, or production session.

Weights + KV cache→Signed runtime offers→Compatibility groups→Topology gate→Read-only plan

Rampage desktop showing the universal AI gateway, compute strategy, five-machine fabric grid, and a healthy autonomous self-scan — The real desktop: one strategy deck, an exact universal API surface, and an evidence-driven self-scan that acts inside the owner envelope without per-change approval.

The planner stays read-only. The separate whole-model lane serves OpenAI, Anthropic Messages, and OpenRouter-style text requests through an exact one-shot lease, authenticated QUIC, local Ollama, and a signed transcript receipt. Cross-host tensor and pipeline launch remain fenced.

ONEPOOL

Not fake global RAM.
Useful aggregation.

1Whole jobBest capable node

2Shard setIndependent useful work

3ReplicasThroughput or evidence

4Data localityMove less, prove more

5Certified shardingOnly when topology wins

Every contributor advertises an operation-exact signed capability contract. Old PCs can run complete jobs, shards, replicas, builds, renders, transcodes, simulations, cache, and storage when a shipped adapter proves it. A phone is not a pretend data-center GPU: today the native source allows only CPU hashing and independent evaluation shards when foreground, thermal, battery, identity, and restart policy all agree. Every additional adapter must earn its own proof.

UNIVERSAL, WITHOUT THE FICTION

One fabric.
Many useful lanes.

Rampage does not claim that a network turns every remote byte into local RAM or VRAM. It standardizes identity, admission, placement, recovery, evidence, and STOP—then lets operation-specific adapters move work at the boundary that actually scales.

SHIPPED LANE

Local AI

Discover installed Ollama models, select an exact worker, and serve bounded text through OpenAI, Anthropic Messages, or OpenRouter-style clients.

One-shot model-session lease
Authenticated QUIC streaming
Transcript-matched signed receipt

SHIPPED PRIMITIVE

Agent swarms

Scatter independent research, evaluation, preprocessing, and transformation work across eligible machines, then recover against an explicit success threshold.

Atomic shard admission
Independent retry and recovery
No worker gains controller authority

ADAPTER-GATED

Production

Place builds, renders, transcodes, simulations, and batch stages near the compute or data they need—only when a shipped adapter proves the exact operation.

Runtime digest and isolation contract
Data-local artifact movement
Candidate profiles grant no authority

FOREGROUND FIRST

Gaming

Keep the gaming PC responsive by moving eligible background AI, compilation, capture processing, conversion, cache, or server-simulation work elsewhere.

Thermal and responsiveness envelopes
Speed lane rejects slow peers
No fake remote-VRAM FPS claim

NATIVE SOURCE CANDIDATE

Phones + tablets

Contribute hashing and independent evaluation shards only while native battery, thermal, low-power, foreground, identity, and restart policy agree.

Kotlin + Swift platform telemetry
Immediate native stop on pressure or lifecycle loss
Unsigned CI candidates are not store releases

PROTECTED DATA

Donated storage

Turn owner-controlled drives into encrypted content-addressed capacity that resumes after interruption and proves possession before it counts.

Flushed 4 MiB resumable sessions
Two independent protected replicas
Bounded verification and repair

What “universal” means: one trust contract everywhere; operation-specific proof before execution; no capability inferred from a device label.

RECURSIVE INTELLIGENCE

Ambition, isolated from authority.

Rampage continuously scans routes, links, failures, denials, thermals, battery, idle capacity, capability gaps, and storage replication. It can propose mutations, challenge them, replay them, and autonomously earn a bounded canary without a per-change prompt. Anything outside the owner envelope is denied.

Record→Analyze→Mutate→Prove→Audit→Gate→Enshrine

AI DIRECT AUTHORITY

0 Separate token · no controller keys · no leases · no enrollment · no self-expanded envelope · no STOP bypass

NOT VAPORWARE

Every big claim has a smaller proof.

LEASE

Exact durable authority

The Governor signs only checked minimum resources. Workers persist consumed nonces and the highest authority epoch across restart.

SHARD

Atomic pooled work

A complete set is planned against one reservation book and admitted all-or-nothing, with explicit success thresholds.

MESH

Direct first. Owner relayed.

Signed peers use direct QUIC when possible. Hard NAT falls back only to the bundled owner relay, with a fresh Governor-signed allowlist and resource caps—never a silent public fleet.

CAS

Encrypted donated storage

Flushed 4 MiB sessions resume after restart, quarantine objective corruption, and repair protected data to two independent workers.

RECEIPT

Verifiable completion

Workers sign job results and full-content possession challenges; rotating proof budgets keep autonomous verification bounded.

STOP

Human-owned interruption

Native STOP latches immediately and reconciles to a hash-chained epoch—even if a crash interrupts propagation.

The relay proof turns off every direct IP transport on both test peers, leaving the owner service as the only possible route. The storage proof interrupts a two-frame transfer, resumes it after a gateway and CAS restart, then repairs one protected artifact across two independently keyed workers. The honest boundary: public-WAN, every-NAT, and physical disk-loss qualification still require separate campaigns.

RAMPAGE 0.3

Stop wasting the machines you already own.

Make them act as one. Make every unit of authority prove where it came from.

Get the Windows release Inspect every line Read the latest proof

Trusted-circle release · public source inspection · proprietary license · unsigned binaries