FastPix for news publishers

Video API for short-form news apps

FastPix Video API has everything you need to run a short-form news app. Fast field uploads, a vertical feed, live coverage that clips itself, and the data behind every story.

Per-minute pricing, no per-title fee. $25 in signup credits, no credit card.

35-90sto encode a package~12slive quote to vertical clip9platforms, one story
A breaking news package uploaded, encoded, clipped to vertical and published across destinations

Trusted by teams shipping video at scale

Customer logoCustomer logoCustomer logoCustomer logoCustomer logoCustomer logo

Why FastPix

Complete video infrastructure for news publishers

One API, whole stack

Upload, encoding, live, playback, AI and data all come from the same API key.

Uploads that resume

Chunked resumable uploads keep a large file moving on a weak connection instead of starting again.

Built for scale

Multi-CDN delivery scales with the audience, so a spike runs on the same setup as a quiet hour.

Analytics built in

Every session reports watch time and playback quality, with no separate analytics product to buy.

Customer story

We were proud of our tech stack. But we had too many vendors. One for video, another for AI, another for playout. It created extra work for the tech team and for management.

Indira Devi Gollapudi

Technical Head, Aadhan Media

Read the Aadhan story
Aadhan Media

Upload from the field

Fast mobile video upload from a reporter at the scene

FastPix moves a phone recording off a reporter's handset while they are still at the scene. It goes up in parallel chunks, resumes after a dropped signal, and reports progress throughout.

  • Small chunks tuned for cellular, so a reporter on 4G at a protest does not restart the upload. Guide

  • Resumable SDKs for iOS, Android, Flutter and web, so the app your reporters carry already has it. Guide

  • Webhooks at each stage, so the newsroom sees progress instead of a spinner and a guess. Guide

  • Audio levelled on the way through, so a windy street piece matches a studio read. Guide

  • URL pull for wire and agency material, which is how most non-field footage actually arrives. Guide

A reporter's handset footage uploaded in resumable chunks over 4G from the scene

Archive and publishing

Video CMS and publishing controls for a newsroom

FastPix holds every story as an asset carrying your own fields, from story ID and language to region and publisher. Your CMS publishes and unpublishes by flipping access on the playback ID.

  • Ten custom fields per asset: story ID, language, region, publisher and desk. Guide

  • The language versions of one story sit in a playlist, ordered and reorderable through the API. Guide

  • Publish by creating with public access, and unpublish by flipping the playback ID to private. Guide

  • Update metadata on a published story without touching the video or the URL. Guide

One story held as assets in four languages with custom fields and publish controls

Vertical feed

Vertical video feed with swipe and instant next story

The FastPix player ships a real 9:16 feed, not a landscape player turned sideways. It prefetches the next story while the current one plays, so a swipe lands on a frame.

  • Native 9:16 playback on web, iOS and Android, driven by one playback ID per story. Guide

  • The next story prefetches while the current one plays, which is what makes a swipe feel instant. Guide

  • Autoplay muted with tap to unmute, the behaviour a news feed needs on a phone. Guide

  • A poster frame per story, so a card is never black while the feed is still loading. Guide

  • Preload set per placement, so the feed fetches what it needs and nothing further down. Guide

A vertical 9:16 news feed that prefetches the next story so a swipe lands on a frame

Content protection

Hotlink protection, signed playback and watermarking

FastPix signs every playback URL with a short-lived token your service mints. Restrict playback to the domains you list, and watermark the file so a copy carries your mark wherever it goes.

  • Signed playback URLs, a JWT on a 2048-bit RSA key pair, short-lived and minted by your own service. Guide

  • Domain and browser restriction, the hotlink lever, bundled rather than sold as a security add-on. Guide

  • Visible watermark as image or text, placed by pixel or percentage with opacity control. Guide

  • Rotate the signing key and every outstanding token dies at once, the fastest takedown lever you have. Guide

Signed playback URLs, domain restriction and watermarking protecting a news video

Measurement

Story, viewer and playback analytics for news video

FastPix Video Data reports what every story did after it published. Views and completion per cut, where readers leave, and whether playback quality was the reason they went.

Story-level data

How a story performed across everyone, which is the desk decision behind what gets covered next.

  • Completion per cut, not per story, because two versions of one package perform differently. Guide

  • Where readers leave, which in news is usually one specific sentence.

  • Top performing stories, so the next bulletin is planned on evidence rather than instinct.

Viewer engagement

What one reader did in a session, which is the number that predicts whether they come back.

  • Session watch time, and how many stories they got through before stopping. Guide

  • Repeat views of the same story, usually the clip worth cutting again.

  • Ten custom dimensions, so language, region and desk become filters rather than guesses.

Playback quality

Whether the app got in the way, kept separate from whether the story was worth watching.

  • Startup time and rebuffering, because a stall on a ninety second story is most of it. Guide

  • Playback failures by device, so a broken build surfaces before the store reviews do.

  • Network and region breakdowns, which separate a weak story from a weak connection.

56 dimensions on every session, first 100,000 session plays a month included, and every view available through the API for your own warehouse. Video Data also feeds the Breaking News Agent, so which cuts performed tunes how the next story gets scored and composed.

Story completion, viewer engagement and playback quality analytics for news video

Breaking News Agent

AI media monitoring and automated publishing for newsrooms

The Breaking News Agent watches 200+ sources and tells your desk what is rising before the window closes. It drafts in your voice, cuts a version per platform, and ships in 90 seconds.

  • 200+ sources across broadcast, video, wires and social, deduped and clustered by topic in real time.

  • Every story scored on fit, locality, sentiment and priority, delivered as confidence-scored JSON you can override.

  • Drafted in your voice by a model tuned on your back catalogue, across 10+ languages.

  • Routine stories publish automatically, and anything sensitive routes to an editor with the draft already done.

  • Source to published in about 90 seconds, or roughly 12 seconds for a live broadcast cut.

The Breaking News Agent scoring cross-confirmed sources and composing per-platform cuts

Built API first

Video API and SDKs for a newsroom CMS

Every step above is one documented call on the FastPix API. SDKs cover seven server languages and five client platforms, and a webhook fires whenever a step finishes.

SERVER SDKS

CLIENT SDKS

Read the API reference
API surface
POST/v1/on-demandIngest a package
POST/v1/liveGo live from the field
POSTlive clipCut during the event
POST/playlistsCollections for the archive
POST/watermarkBrand an asset
GET/signing-keysSign playback per viewer
GETVideo Data APIPer-clip performance
DELETE/playback-ids/:idPull one surface
DELETE/on-demand/:mediaIdKill the asset
HOOKvideo.asset.readyTell the CMS
HOOKmedia.watermark.readyBranding applied
HOOKstory.scoredAgent found something

Multi-platform distribution

One long event, cut into the moments each platform wants

FastPix cuts one long event into the clips each platform wants. Mark the moments by timecode or let the Clipping Agent score them, and every cut comes off the same encode.

  • Score the moments on transcript, chapters and named entities, and your desk keeps or discards each one.

  • Nine destinations out, platform-native, from YouTube and Shorts to TikTok, Reels, Facebook, X, LinkedIn, your own app and any RTMP endpoint.

  • Aspect ratio per destination and length by cut, 30 seconds, 90 seconds or three minutes, all off the same encode.

  • Captions in 10+ languages, with moment scoring from the Clipping Agent in early access.

city council session · 1:52:40Scored

MOMENTS SCORED, HIGHER IS BETTER

00:12:040.94
00:41:190.91
01:38:520.97

Scored on transcript, chapters and named entities. Your desk keeps or discards each one before it fans out to nine destinations.

Cloud Playout

Run a 24/7 linear news channel from your archive

Cloud Playout schedules the archive you already have as a linear channel. It cuts to a live input when a story breaks, fills the gaps, and pushes to every destination at once.

  • A rundown rather than a looping playlist, built the way a bulletin is planned. Guide

  • Cut to a live input mid-schedule when something breaks, then back to the rundown. Guide

  • Ad breaks marked with SCTE-35 at known times, for your ad server to fill. Guide

  • Simulcast the channel to YouTube and any RTMP endpoint, in sync, with no second encoder. Guide

  • A 24/7 loop channel for a single strand, built once and left running. Guide

channel · always onScheduled
RUNRundown scheduledarchive, in bulletin orderGA
LIVEStory breaks, cut to livethen back to the rundownGA
ADSSCTE-35 break markedyour ad server fills itGA
OUTOut to YouTube and RTMPone channel, every destinationGA
GFXChyron and L-bandnot in the docsConfirm

Benchmarked against five video APIs

Upload and startup, measured against five video APIs

Two numbers a newsroom feels. How long a large file takes to get up, and how long a reader waits before the first frame. Same file, same region, same network, open harness.

Upload time467 MB file, lower is better
FastPix70.3s
Vimeo90.2s
Cloudinary123.9s
api.video157.3s

Chunked upload sends the file in parallel parts and picks up again after a dropped connection, which is exactly where a reporter on cellular loses time.

Cold time to first frameshort clip, nothing cached
FastPix1.29s
Cloudinary1.60s
api.video1.74s

A reader swipes through a dozen stories in a session, so the wait happens a dozen times. Gumlet posted 1.12s on a few runs only, so it is not treated as comparable.

Where we lose: api.video publishes a short clip 4.6 seconds sooner, at 23.6s against 28.2s. Per-title encoding also produced 35% smaller files at matched quality.

How it comes together

What it takes to run video in a digital newsroom

Five steps between a reporter pressing record and a story playing in the feed.

01

Get it off the phone

Chunked resumable upload from the handset, resuming after a dropped signal on the way back.

Guide
02

Tag it to the story

Write story ID, language, region and desk into custom fields as the asset is created.

Guide
03

Caption and localise

Captions generate during processing, and you attach a subtitle or audio track per market.

Guide
04

Put it in the feed

The player prefetches the next story while the current one plays, so a swipe lands on a frame.

Guide
05

Read what it did

Completion, drop-off and playback quality per story, filtered by the fields you set.

Guide

Bring a real story and a stopwatch

Send us a package the way your field team actually sends it. In 30 minutes we will publish it, cut the vertical version and kill it, timed against your own window.

· 30 minutes· Your footage· Including the takedown
Talk to us

Prefer to try it yourself? Start free with $25 in credits

Common questions

News video questions, answered.

  • How fast is a clip actually publishable?

    A playback ID comes back immediately and the video is servable while remaining renditions finish. Full encode of a 10-minute 1080p source is 35 to 90 seconds. A webhook tells your CMS when the full ladder is ready.
  • Can someone hotlink our video on their own site?

    Not if you restrict it. Playback can be limited to a domain allowlist, and signed URLs carry a short-lived JWT that expires by default in five minutes. A visible watermark is the third layer, so a screen-recorded copy still carries your mark. There is no forensic or per-session watermarking.

  • Can a reporter upload from their phone on a bad connection?

    Yes. Resumable upload SDKs ship for iOS, Android and web, so an upload that drops on 3G resumes from where it stopped rather than restarting the file. The playback ID comes back on acceptance, before encoding finishes.

  • How many platforms can one story go to?

    Nine destinations, each with its own aspect ratio, length, captions and brand graphics, generated from one story rather than re-edited per platform. Captions and cuts cover 10+ languages.

Pricing

Rate card

Per minute, with the player and analytics already in it. No charge per story, per title or per seat. See full pricing.

ENCODING

Pay per minute encoded

$0.0267/min 1080p Pro

Per-title ABR encoding across H.264.

Up to 720p Pro$0.0213 / min
Up to 1080p Pro$0.0267 / min
1440p (2k) Pro$0.0427 / min
2160p (4k) Pro$0.0855 / min

STREAMING

Pay per minute streamed

$0.00067/min 1080p Pro

Multi-CDN delivery from 300+ POPs.

Up to 720p Pro$0.00054 / min
Up to 1080p Pro$0.00067 / min
1440p (2k) Pro$0.00108 / min
2160p (4k) Pro$0.00217 / min

STORAGE

Pay per minute stored

$0.00268/min 1080p Pro

Assets stored and CDN caching, lifecycle handled.

Up to 720p Pro$0.00215 / min
Up to 1080p Pro$0.00268 / min
1440p (2k) Pro$0.00430 / min
2160p (4k) Pro$0.00860 / min