Join the MESH

Participation Tracks

Track 01

Developer

Build AI-native applications and agents using the MESH API. Instant key delivery for verified organisations.

  • RESTful, webhook-driven API
  • SDK for TypeScript; Python coming soon
  • 16 workload types across image, video, 3D and audio
  • Runs on hardware you already own, no per-GPU cloud bill
  • Async job API with webhooks on completion
Track 02

Device owner

Run AI on the machines you already own. Open a browser tab and the device joins your own group.

  • No installation required, browser-native
  • Supports NVIDIA, AMD, Apple Silicon and Intel Arc
  • Invite a second device with a link; VRAM pools
  • Models too big for one machine split across the group
  • The desktop app keeps a machine available in the background
Add your devices
Track 03

Organisation

Deploy MESH for your team. Custom SLAs, dedicated node pools, usage dashboards.

  • Org-admin RBAC with member management
  • Reserved capacity pools
  • Custom SLA tiers with priority routing
  • Usage analytics and audit log
  • Enterprise billing and invoicing
Track 04

Protocol contributor

Help build the protocol, add new model types, or extend the SDK.

  • Full protocol documentation available
  • IWorkloadHandler interface: add any model
  • TypeScript and Python test suites
  • Contributor programme coming soon
View docs

Questions, answered

Is my data private when using MESH?

Job inputs are encrypted in transit and only ever reach devices in your own group. Nothing is persistently stored on them: the browser cache holds model weights only, never job payloads.

How is result quality guaranteed?

Results are validated by consensus. The same job is run on multiple devices and outputs are compared by hash; jobs that fail consensus are re-run automatically.

What happens if a node goes offline mid-job?

The scheduler detects a stale lease within 15 seconds and re-assigns the work unit to another device in your group. Most users never notice.

Can I run MESH on a server, not a browser?

Yes. The node SDK supports onnxruntime-node for server-side execution, and the desktop app keeps a machine available in the background. The browser remains the primary path.

Whose hardware runs my job?

Only devices in your own group: this browser, your desktop app, your phone, and anyone you invited with your link. If none of them are online, the job does not start.

What is the minimum hardware?

Any WebGPU-capable GPU with 4 GB+ VRAM running Chrome 113+ or Edge 113+. Lighter devices handle lighter workloads; more VRAM in the group unlocks more job types.