vs
Runware vs Inception
Runware is built for cheap image, video, audio and 3D generation. Inception is built for fast text generation with diffusion LLMs.
By The Subconscious Team · Updated
Runware vs Inception: key differences
Runware puts 300+ priced media models behind one request schema, with images from fractions of a cent and video billed per second, like Seedance 2.5 at about $0.10 a second at 480p. LLM hosting is a side line. Inception serves only its Mercury text models. Mercury 2.5 is a reasoning model with tool use and 260K context at $0.20 in and $0.75 out. Inception reports over 1,100 tokens per second; Artificial Analysis measures about 640.
The two cover different work. Runware fits apps generating images or short video at volume. Inception fits text workloads where speed matters, like autocomplete, voice agents and real-time chat. A consumer app could use both.
What Runware and Inception do
Runware
Runware sells what it calls the lowest-cost API for media generation, and it claims more than 1M developers. One endpoint covers image, video, audio, 3D and text. Every request is a task with the same shape, so switching from a Kling video to a Seedream image mostly means changing the model ID. The published rate sheet lists 300+ priced models, with images from fractions of a cent to a few cents each and video billed per second, like Seedance 2.5 at about $0.10 a second at 480p.
Example models: Seedance 2.5, Qwen-Image-3.0
Full Runware profile
Inception
Inception builds diffusion large language models (dLLMs). Every other LLM on this list generates text one token at a time; Inception's Mercury models start from a rough draft of a whole block and refine it over a few passes, producing many tokens in parallel. That ties speed less to output length and lets the models run fast on ordinary NVIDIA GPUs rather than custom chips. The company was founded by professors from Stanford, UCLA and Cornell behind core work on diffusion, Flash Attention and DPO, and is led by Stanford's Stefano Ermon. It raised a $50M seed in November 2025 led by Menlo Ventures, with Mayfield, M12, NVentures, Snowflake and Databricks, plus Andrew Ng and Andrej Karpathy as angels.
Example models: Mercury 2.5, Mercury 2
Full Inception profileShould you choose Runware or Inception?
Runware vs Inception at a glance
| Attribute | Runware |  Inception |
|---|---|---|
| Model access | Hosted media models | Closed weights (Mercury dLLMs) |
| Flagship models | Seedance 2.5, Qwen-Image-3.0 | Mercury 2.5, Mercury 2 |
| Speed | Unknown | 1,100+ tok/s (vendor); ~640 measured |
| Price | Images from fractions of a cent | $0.20 in, $0.75 out (Mercury 2.5) |
| Customization | Fine-tuned diffusion checkpoints | Fine-tuning on request |
| Deployment | Unified API, serverless GPUs, bare metal | Serverless API, Bedrock, Azure, private |
| Long context | Not applicable | 260K |
Frequently asked questions
What is the difference between Runware and Inception?
Runware is built for cheap image, video, audio and 3D generation. Inception is built for fast text generation with diffusion LLMs.
When should I choose Runware over Inception?
High-volume image and video generation; One schema across media modalities; Fine-tuned diffusion checkpoints at scale.
When should I choose Inception over Runware?
Very fast text output; Voice agents and code autocomplete; Cheap reasoning with tool use.
Is Runware or Inception cheaper?
Runware: Images from fractions of a cent. Inception: $0.20 in, $0.75 out (Mercury 2.5). The cheaper choice depends on the model and workload.
Which has more context, Runware or Inception?
Runware: Not applicable. Inception: 260K.
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.