Municipal and enterprise streaming

Flumen

Every client gets their own broadcast — live, recorded, and on their site. Isolated workspaces. You stay in control.

Cities, schools, and companies use Flumen to go live without sharing a platform. You decide how many streams they can run and how much they can store. Their operators never see another tenant.

Stream my meetings Watch a live example See pricing

Product of SOS TECH · flumen.live · (603) 556-4055

Municipal chamber ready for a Flumen broadcast

Chamber · program

SRT · RTMP

Platform

How Flumen is built

Platform architecture

Live on global CDN · VOD on object storage

Standby — waiting for encoder

Contribution

OBS / vMix

RTMPS · SRT · WHIP

Chamber codec

Hardware SRT

Mobile / WHIP

Field contribution

Live CDN

Live input

Per channel · auto-record

Transcode

Adaptive bitrate

Playback + outputs

HLS · DASH · player · restream

Flumen control

Control plane

Console · API · webhooks

Catalog

Titles · quotas · metadata

Archive pipeline

Checksum → object store → clear live cache

Viewers

Live players

Player / HLS / WHEP

Client site

town.flumen.live

Embeds

Allow-listed iframes

Media paths

Live · global CDN

While people watch live, contribution and players stay on the live edge — not the archive.

Recordings · object storage

After archive, people watch recordings from durable storage via library and embeds — never the live cache.

Platform add-ons

Captions & assistive

Closed captioning for every session

Meeting minute sync

Align archives with published minutes

Custom integrations

Civic sites, clerk tools, your stack

API access

Automate channels, archives, embeds

01 · Contribution
OBS · vMix · WHIP
RTMPS, SRT, or WHIP into a Flumen live channel. Each channel maps to one live input on the edge.
02 · Live CDN
Ingest, transcode, live play
While the session is on the air, viewers watch from the live CDN (player / HLS / DASH / WHEP) — same edge as contribution.
03 · Live viewing
People watching the livestream
Live players pull from the global CDN edge. Playback never waits on the archive pipeline.
04 · Flumen control
Console + archive + API
On ready: download → checksum → object storage → clear temporary live recording. Catalog powers library and embeds.
05 · Recorded viewing
People watching recordings
Client sites and embeds stream ready takes from durable object storage via the library — never the live cache.

Live contribution
Encoders publish RTMPS, SRT, or WHIP to Flumen live channels. Stream keys and passphrases are per channel.
Watching live
People on live players pull from the global CDN edge while the session is on the air — not from object storage.
Watching recordings
After archive, people watch ready takes from durable storage through the client site and embeds — never the live cache.

Explore