Distributed compute

Consent-first distributed compute

Start a verifiable compute project across willing peers, or contribute bounded idle resources to one. Explicit consent, resource caps, and verification built in.

Open in browser Download desktop

Browser · macOS · Windows · Linux · ChromeOS

What it does

Compute coordinates work across machines whose owners opted in. Project owners define the workload and verification; contributors set hard limits on CPU, memory, and time. Nothing runs on a machine without its owner’s standing consent.

Verifiable projectsWorkloads carry verification so results can be checked.

Bounded contributionContributors cap CPU, memory, and hours.

Explicit consentEvery contributor opts in per project and can leave at any time.

Peer coordinationScheduling and results move over the VIMS peer network.

Status visibilityOwners and contributors see progress and node health.

Identity-boundParticipation is signed by the contributor’s key.

How it works

Define a project or pick one to support
Set verification or resource limits
Run and watch progress

FAQ

Can a project access my files?

No. Contributions run in a bounded sandbox with only the declared inputs.

Is there payment?

Projects may attach x402 rewards; participation itself is free.

Can I use VIMS Compute in a browser and in VIMS Desktop?

Yes. Open it at its subdomain, or use the same surface inside the VIMS Desktop client — same key, same data.

How does VIMS Compute connect to the rest of VIMS?

It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.

VIMS AppsApp catalog VIMS KeysIdentity vault VIMS MCPModel Context Protocol VIMS DesktopLocal AI workspace