CommonCompute
Log inGet started
Log in
Get startedExplore workloads
Roadmap

What we're building, what's next, what we're not doing.

We try to keep the roadmap honest — including the "not doing" column, because saying no publicly is the trust signal we'd want from a tool we're evaluating. Source of truth is ROADMAP.md on GitHub. Last updated 2026-09-12.

Not on the list

Recently shipped

Moved out of the columns below because they exist now.

  • First-party SDKs for Python and TypeScript. pip install commoncompute and npm install @commoncompute/sdk — same resource-oriented surface in both, plus a commoncompute CLI and an MCP server (commoncompute-mcp) so coding agents like Claude Code and Cursor can drive the network directly.
  • Signed and notarized provider releases. Provider builds use Developer ID, notarization, stapling, Sparkle signatures, and a public update feed. Each new workload still needs its own release and physical validation.
  • Public changelog and provider-version visibility. Shipped behavior stays searchable, while current catalog discovery remains the authority for what can be ordered now.
Shipping now

Now

Currently in release validation. These are not production promises until they appear in the live catalog.

  • Narrow open-model catalog. Validate and release qwen3-4b chat and LoRA fine-tuning plus qwen2-vl-2b visual question answering/document understanding. Promotion requires pinned model supply, packaged notices, provider compatibility, physical cold/warm/cancellation tests, and live capacity; code or catalog entries alone do not make a lane available.
  • Framework integrations. LangChain, LlamaIndex, and Vercel AI release candidates follow the same live catalog and fail closed on held models. Their packages publish only after the matching API surface is live and cold-install smoke tests pass.
  • Exact-SHA production promotion. Worker, site, migration, catalog, and provider releases are being consolidated behind reproducible tests and post-deploy identity checks.
Up next

Next

Started or planned for the following release.

  • Portable computer vision. Evaluate object detection, classification, segmentation, OCR, and image embeddings using redistributable open runtimes and models. No candidate is orderable until its license chain, artifact digest, output contract, benchmark, and abuse controls pass review.
  • Speech generation. Add text-to-speech through an open, redistributable model/runtime path, with documented voice rights, provenance, safety, and output-format controls.
  • Music and video generation. Prototype separately because model licenses, training-data terms, moderation, provenance, storage, and hardware economics differ substantially. These remain roadmap work, not hidden catalog lanes.
  • Provider release adoption gate. Measure active version distribution and keep new work off stale clients before enabling a new workload.
Thinking about

Later

Things we want to do but aren't sized yet. Order is roughest here.

  • Multi-Mac fleet view for organisations. When one user runs Common Compute on 30 Macs across the office, give them one screen.
  • Common Compute Nodes. Generalize the provider contract around explicit runtime and hardware capabilities. Apple-silicon Macs remain the first host; Linux CPU/GPU support is a separate future backend and is never inferred from macOS MLX compatibility.
  • Reserved capacity. Offer scheduled or dedicated supply only after real provider availability, utilization, and paid-run evidence supports the commitment.
  • Per-task carbon receipts. Heartbeat already carries chip + thermal + duration — render the kWh and gCO₂eq alongside the price.
Not on the list

What we're not doing

These come up often enough to be worth saying out loud.

  • Arbitrary code or arbitrary model execution. The product is a closed, versioned workload/model catalog; unsupported identifiers are rejected before persistence, reservation, or dispatch.
  • Apple-system-framework workloads without the required rights and review. Retained implementation or reverse-engineering research is not a commercial offer. The live catalog stays independent of those paths.
  • A consumer compute marketplace. Providers contribute Macs they own; we don't intermediate hardware purchases or financing.