Long-running agents deserve better inference.
vs

Morph vs General Compute

Morph builds fast specialist models for the edit step of coding agents. General Compute serves open chat models with decode on ASICs.

By The Subconscious Team · Updated

Morph vs General Compute: key differences

Morph merges frontier-model edits into full files at 10,500+ tokens per second with a 7B model on custom CUDA kernels, and adds repository search, context compression and fine-tuning. morph-v3-fast costs $0.80 in and $1.20 out per million tokens. General Compute splits each request between NVIDIA GPUs for prefill and ASICs from Cerebras, SambaNova and others for decode. In its own benchmark it measured over 1,000 tokens per second on GPT-OSS 120B. Its catalog runs from DeepSeek V3.2 at $0.25 in and $0.38 out to MiniMax M2.7 at $0.28 in and $1.20 out.

The two can work together. General Compute can run the main model in an agent loop where decode speed sets the wait, and Morph can handle the apply and search steps. Morph offers self-hosting on Enterprise, while General Compute offers dedicated racks and tokens-per-second SLAs under contract.

What Morph and General Compute do

Morph

Morph builds small, very fast specialist models that sit beside a big coding model inside an agent. Its flagship is Fast Apply. The frontier model writes only the changed lines with // ... existing code ... markers, and Morph merges them into the full file at 10,500+ tokens per second with up to 98% accuracy. It is the same idea behind Cursor's instant apply, offered as an OpenAI-compatible API.

Example models: morph-v3-fast, morph-v3-large

Full Morph profile

General Compute

General Compute is a San Francisco inference cloud built on alternative chips. It splits each request across hardware, with NVIDIA GPUs handling prefill and ASICs from Cerebras, SambaNova, Positron AI and d-Matrix handling decode. In its own open benchmark on GPT-OSS 120B it measured 1,025 to 1,234 output tokens per second against 100 to 121 on an unnamed GPU cloud, and up to 16.2x faster end to end. Founders Finn Puklowski and Jason Goodison raised a $15M seed led by FUSE, an up to $400M debt facility from Upper90 and, on October 27, 2026, a $100M Series A co-led by Blackbird and Abstract.

Example models: MiniMax M2.7, DeepSeek V3.2, GPT-OSS 120B

Full General Compute profile

Should you choose Morph or General Compute?

Morph

Choose Morph for

  • Applying model edits to large files
  • Agentic repository search
  • Self-hosting on Enterprise

General Compute

Choose General Compute for

  • Fast decode for the main agent model
  • Low prices on DeepSeek V3.2
  • Reserved ASIC capacity under contract

Morph vs General Compute at a glance

AttributeMorphGeneral Compute
Model accessSpecialist modelsOpen weights
Flagship modelsmorph-v3-fast, morph-v3-largeMiniMax M2.7, DeepSeek V3.2, GPT-OSS 120B
Speed10,500+ tok/s Fast Apply1,000+ tok/s on GPT-OSS 120B (vendor)
Price$0.80 in, $1.20 out (morph-v3-fast)$0.21–$0.28 in, $0.38–$1.20 out per 1M
CustomizationFine-tuning offeredCustom LoRA and fine-tuned checkpoints
DeploymentOpenAI-compatible API; self-hosted on EnterpriseServerless API, dedicated racks, bare metal
Long contextUnknown192K (MiniMax M2.7)

Frequently asked questions

What is the difference between Morph and General Compute?

Morph builds fast specialist models for the edit step of coding agents. General Compute serves open chat models with decode on ASICs.

When should I choose Morph over General Compute?

Applying model edits to large files; Agentic repository search; Self-hosting on Enterprise.

When should I choose General Compute over Morph?

Fast decode for the main agent model; Low prices on DeepSeek V3.2; Reserved ASIC capacity under contract.

Is Morph or General Compute cheaper?

Morph: $0.80 in, $1.20 out (morph-v3-fast). General Compute: $0.21–$0.28 in, $0.38–$1.20 out per 1M. The cheaper choice depends on the model and workload.

Related comparisons

Running long-horizon agents?

If your agents run past 200K tokens, compare both against Subconscious. Our inference stack treats a long-horizon trace as the primary workload, so speed, cost, and accuracy hold up deep into the trace.