LO
estimated operating bill

What does Loom
cost to run?

Async video messaging with recording, hosting and transcription.

MODELED RANGE€1.2m–€5.2m/momodeled
build time3–6 years
initial team200–650 people
categoryVideo
statuseditorial estimate
visit product ↗
estimated infrastructure receipt

monthly recurring run cost

€1.2m–€5.2m/mo
video transcoding€552k–€2.4m
video storage and CDN€348k–€1.5m
speech transcription€204k–€884k
baseline hosting, monitoring and backups€96.0k–€416k
the modeled take

Loom is modeled from its public product surface, documented architecture where available, current pricing, and the operational demands implied by its major features. The range is an editorial estimate—not a leaked invoice or a claim from Loom.

The largest cost pressure comes from video transcoding, video storage and cdn, speech transcription. Build-time assumes a production product with authentication, billing, observability, security, responsive clients and the core workflow represented honestly—not a visual clone.

Infrastructure can vary dramatically with negotiated contracts, caching, region, reliability targets and customer behavior. Use the itemized receipt and assumptions to challenge the estimate. Founders can submit a correction or verify their real range without publishing sensitive vendor contracts.

from prototype to public scale

How the bill grows.

Same product class, different usage. This is directional—not a pricing quote.

stageusage assumptionmonthly estimate
lean / early product1k–10k users€18.0k–€130k
growing product50k–250k users€144k–€1.1m
modeled current classpublic-scale model€1.2m–€5.2m
assumptions

Where this could be wrong.

  1. Modeled at global asynchronous-video scale
  2. Storage retention policies materially change the range
evidence desk

Public sources used.

01Loom productopen ↗02Loom engineeringopen ↗
know the real bill?

Make this estimate better.

Founders can verify a range or correct an assumption without exposing confidential vendor contracts.

Submit a correction