Why Aperture

Editorial work at the speed of thought.

Aperture exists because editorial time is wasted in the gaps: scrubbing for moments, round-tripping feedback, copying files between tools, and waiting for renders. We own the whole loop — timeline, transcript, library, review, render — so the gaps are gone. This page is the honest argument for why that makes teams faster than anything else on the market.

Where the hours actually go — and where we delete them.

  • 1. Finding footage

    The old way: scrub proxies and hope. Aperture: moment search over every transcript in the library, ranked by relevance, one click from result to timeline. Finding becomes reading.

  • 2. Making the first cut

    The old way: hunt for the blade, ride the playhead, chase frames. Aperture: the transcript is the edit — select the words you don't want, press cut. Silence and filler removal is one operation, not an afternoon.

  • 3. Getting approval

    The old way: exports, file transfers, feedback in email, confusion about versions. Aperture: one guest link — expiry, password, watermark — comments pinned to the frame, threads resolved, sign-off recorded in the audit trail.

  • 4. Feeding every channel

    The old way: re-edit the same content per platform. Aperture: LLM-ranked highlights, a 9:16 reframe preset, styled captions, auto-duck music. One master, many winners.

  • 5. Waiting

    The old way: renders block the machine; the workstation is the bottleneck. Aperture: the server renders while you keep editing — from anywhere, on anything.

The design decisions

Why we win on speed — by architecture, not marketing.

We own the transcript and the timeline

Most tools bolt a transcript onto a player. We own both ends: text operations are real timeline ops (razor, ripple) executed by the same engine that plays and renders. That's why "cut this sentence" is one op — not a transcript suggestion you re-do by hand.

Browser-first, server-backed

The client composites live with WebCodecs; the server conforms with ffmpeg. You get instant feedback and consistent, professional exports — with zero installs on any device, anywhere.

Library is a database, not a folder

Collections, smart (saved-search) collections, tags, sha256 duplicate detection, and transcripts are queryable. The library finds things for you instead of hiding them from you.

Honest AI strategy

We build AI where it compounds with the timeline — text editing, search, captions, highlights, auto-tagging — and we generate media where it sells: images and video on Pro. We don't pretend a chat window is an editor.

Your edit is never locked in

OTIO and project JSON export on every plan. Realtime co-editing with presence. API tokens and webhooks for machine integration. If you leave, your work leaves with you.

Team-grade from day one

Audit trail with sign-off export, per-collection permissions, internal-only notes, SSO via OIDC, metering. The governance a company needs is not an enterprise upsell bolted on later.

The honest comparison.

Review tools don't edit. Web editors don't do governance or archive. Transcript editors don't run a render farm. Aperture is the whole loop — ingest, search, cut, review, deliver, automate — in one browser tab.

CapabilityApertureReview tools (Frame.io-class)Web editors (CapCut-class)Transcript editors (Descript-class)
Real multi-lane NLE✓✗BasicSingle-track feel
MAM + review + NLE + API in one product✓ one loopReview only — can't cutWeak MAMNo archive API
Search result opens the editor at that second✓ deep-link to timecodeTranscript search only✗Own docs only
Preview = render (same edit ops client & server)✓✗ApproximateApproximate
Karaoke captions with word timings, burned at export✓ ASS/libassBasicWeb-only trick✓
Realtime multi-user timeline with presence✓ in a tabComments onlyCo-edit, no timeline✗
Per-lane audio stems at export✓ every lane✗✗Partial
Interchange: EDL + FCPXML + OTIO✓ all three✗✗✗
−14 LUFS loudness-normalized delivery, one click✓✗ApproximatePartial
Watch folders + resumable ingest, self-hosted✓ your server✓ SaaS only✗✗
Rules engine + signed webhooks + audit export✓ via API todayEnterprise tiers✗Partial
Guest review where clients decide: sketches on the frame, approval states, internal-only notes✓Comments, no sketch✗Partial
Recordings arrive as layers — screen + camera as separate tracks, re-layoutable✓ in-browser✗ (Loom: flat file)✗✗
API-first with published OpenAPI docs✓ /docs, 33 pathsEnterprise tiersPartialPartial
One tool, one price✓✗✓✓
  • "Frame.io-class" = review/MAM platforms whose core is commenting and asset management, not editing.
  • "CapCut-class" = browser editors with light library and governance features.
  • "Descript-class" = transcript-first editors with limited multi-lane depth and no review-link governance.

Principles we don't trade away.

  • The browser is the workstation — no installs, ever, on any device
  • The transcript is first-class editorial data, not a subtitle afterthought
  • Review happens where the work lives — never in a side channel
  • AI must perform an op you can undo, not generate noise
  • Client-facing surfaces are always watermarked and always revocable
  • Open formats (OTIO, JSON) are non-negotiable
  • Buy, don't build, where the market already wins (never reinvent codecs or gen models)

"We are the cheapest way to get Descript's text loop and Frame.io's review loop in one place — because we own both the timeline and the transcript engine."

— Aperture product thesis

Try the argument
yourself.

Free plan, open registration. Your first sequence is one click away.