Self-hosted live operations

Run every live
stream your way.

Send one feed everywhere. Keep channels on air. Run your media operation on infrastructure you control.

Install on your server Talk through your setup
Signal flow / illustrated example Explore the workflows

One feed · many destinations

Your servers / your controlRTMP · SRT · WebRTC ingestNo software output caps

01 / Workflows

One operation.
Three ways to run it.

From a single event to an always-on channel or a regional fleet. Start with the work in front of you.

01 / Multistream

Broadcast once.Deliver everywhere.

Keep your encoder. Send one live feed to platforms, CDNs, and private links from one place.

  • OBS and hardware encoders
  • RTMP / SRT / Icecast outputs
  • No software output caps

For agencies, live events, and creators

Explore the workflow

02 / 24/7 channel

Keep your channelon air.

Turn reusable files and Google Drive media into a scheduled channel. Keep fallback content ready when a live source needs cover.

  • Playlist playout
  • Reusable media library
  • Different audio per destination

For channel operators and content teams

Explore the workflow

03 / Distributed fleet

Add regions.Keep one clear view.

Place media nodes near events or audiences. Manage routes, see node health, and give each operator the access they need.

  • Regional media nodes
  • Visible recovery and attention states
  • Role-based access

For broadcast operations and platform teams

Explore the workflow
Organize your media library Explore the creator workflow Building a streaming product?

02 / Inside Fluxomni

Your operation,
in clear view.

Watch a route take shape in the operator UI. Inputs, destinations, playlists, and live preview stay together in one workspace.

Fluxomni Studio / route workspaceProduct recording
Create a route, configure its destinations, and monitor the stream from one workspace.

Workspace

Route workspace

Fluxomni route workspace showing route execution, routing, outputs, and live playback controls

Use arrow keys, carousel controls, or thumbnails to move between screenshots.

03 / Operational control

Ready for the work
behind the stream.

Your servers, your data, and open protocols. Backups, access, monitoring, and recovery have a place in the workflow—and a guide when you need it.

Source recovery / illustrated example

Primary source selected
Live inputOn air
Fallback fileReady
Output routeSame destinations.

Fallback media is ready when a live source needs cover.

Actual recovery depends on source and node health.

01

Recoverable installs

Back up routes, credentials, cached media, and runtime data so a server problem does not reset the business.

Read the guide
02

Private or public access

Run behind HTTPS, Tailscale, Cloudflare Tunnel, or your own reverse proxy so only the right people can reach it.

Read the guide
03

Operational visibility

Track route health, node capacity, and stream issues in the UI. Export telemetry to your monitoring tools.

Read the guide
04

Attention feed

One list shows broken outputs, storage pressure, node issues, and known conditions.

Read the guide
05

Pinned versions & rollback

Pin release tags, move forward or back with one env var, and repeat the same setup for each client.

Read the guide
06

Planned maintenance

Restart the web UI for updates while media work keeps running on assigned nodes when the runtime allows it.

No telemetry. Fluxomni does not phone home with analytics or tracking data.

Your infrastructure. Capacity depends on your CPU, bandwidth, and egress. See sizing ↗

04 / Pricing

Start self-hosted.
Find your production path.

Evaluate and build for free. For paid, client, event, or production use, tell us what you run and we will help choose the commercial path.

Personal and evaluation

Free self-host

$0

Personal, hobby, development, and evaluation use

Start here to evaluate Fluxomni or run personal and development projects.

  • Full multi-destination streaming
  • Linear channel playback
  • Single-host and distributed fleet
  • Published Docker images on GHCR
  • Community support via GitHub Issues
Install now

Recommended

Business

Commercial license

Agencies, broadcasters, studios, and teams using Fluxomni for paid, client, or production work

Choose this path when streaming supports a client, event, business, or internal service.

  • Everything in Free
  • Commercial-use license terms
  • Priority email support
  • Security and release guidance
  • Optional deployment review
Contact sales

Roadmap access

Platform Early Access

Design partner

Teams building streaming products or media platforms on their own servers

Apply when you want to discuss product embedding, automation, and render jobs as the platform evolves.

  • Everything in Business
  • Early platform roadmap access
  • Direct roadmap influence
  • Architecture and integration feedback
  • Design-partner terms for early cohort
Apply for early access

Commercial licensing terms are being finalized. Tell us your team type, intended use, route volume, and deployment needs so we can respond with the right path.

05 / Get started

Your server.
Your first stream.

Install on Linux or macOS with Docker, on x64 or ARM64. The installer can set up Docker for you. Linux is the usual choice for production.

  1. 01

    Install the stack

    Pull the images and start Fluxomni with one command.

    curl -fsSL https://install.fluxomni.io | bash
  2. 02

    Open your workspace

    Visit your server's address to reach the operator UI.

    http://<your-server-ip>/routes
  3. 03

    Send your first stream

    Create a route, add destinations, and point your encoder at the generated publish address.

    rtmp://<your-server-ip>:1935/live/<publish-key>

Version pins, edge builds, and media nodes

Pin a version

curl -fsSL https://install.fluxomni.io | FLUXOMNI_VERSION=v26.3.1 bash

Edge channel

curl -fsSL https://install.fluxomni.io | FLUXOMNI_VERSION=edge bash

Add a media node

curl -fsSL https://install.fluxomni.io | bash -s -- media-node

Read the full installation guide

06 / FAQ

The details before
you install.

Get clear on licensing, deployment, protocols, support, and where Fluxomni fits.

Can I use Fluxomni commercially?

Licensing

Personal and evaluation use is free. For paid, client, event, or production work, tell us what you plan to run so we can guide you to the commercial path.

How does this compare to Restream / Castr?

Positioning

Fluxomni is self-hosted: you run it on your servers, add outputs without software tier caps, and scale with your own CPU and bandwidth. See the comparison.

How does this compare to AWS MediaLive or Wowza?

Positioning

Fluxomni gives you self-hosted media infrastructure with a browser UI and owned servers. For paid or production use, talk to us about the commercial path. See the comparison to decide whether that model fits your team.

Do you offer managed hosting?

Support

Not today. Business can include deployment review. If managed hosting is essential, talk to us about Platform Early Access.

Is there a SaaS / managed-cloud version?

Positioning

Not today. Fluxomni is self-hosted media infrastructure. If managed hosting matters to your team, tell us about your use case.

What protocols do you support?

Operations

Ingest supports RTMP push/pull, SRT push, and WebRTC push. Outputs support RTMP/RTMPS, SRT, Icecast, and file output for local recording. Browser preview uses HLS.

Can Fluxomni stream without an external encoder like OBS?

Operations

Yes. Linear channel mode plays scheduled local or Google Drive files to your destinations. Backup files can play when live sources fail.

Does it run on Windows?

Operations

Not natively. Fluxomni runs on Linux and macOS with Docker on x64 or ARM64. WSL2 with Ubuntu works for installation. Production usually belongs on a Linux server or cloud VM.

What kind of support do I get?

Support

Free self-host gets community support through GitHub. Business adds priority email, release and security guidance, and optional deployment review. Platform Early Access adds direct roadmap input.

What's on the roadmap?

Support

Shipping now: live multistreaming, linear channels, reusable media storage, and distributed fleet. Coming next: advanced media workflows and distributed render jobs. Later: automation, object storage, and automated highlights.

Still deciding whether Fluxomni fits your operation? Tell us what you need.

Compare your options

How Fluxomni fits your stack

Compare self-hosted operation with SaaS multistreamers and enterprise media platforms.

vs SaaS multistreamers

Restream, Castr, StreamYard

Fluxomni Restream / Castr
Self-hosted
✓ Yes
✕ SaaS only
Per-stream fees
✕ None
✓ Tiered $20–$300+/mo
Unlimited outputs
✓ No software caps
~ Tier-capped
Data sovereignty
✓ Yours
✕ Vendor-hosted
Setup
Docker on Linux/macOS
Sign up

vs enterprise media platforms

AWS MediaLive, Wowza, AntMedia

Fluxomni AWS MediaLive / Wowza
Operator UI
✓ Modern, browser
~ Partial / separate tools
Distributed fleet
✓ Built-in
✓ Available
Pricing model
Fixed infra + license
Per-minute / per-channel
Self-hosted
✓ Yes
~ Wowza: yes, MediaLive: no
Learning curve
Docker + install
Multi-day

Requires Docker on Linux or macOS (x64/ARM64), with Linux ARM64 and Apple Silicon Macs covered by the published ARM images. No native Windows support, but WSL2 (Ubuntu on Windows) installation has been tested. You run the server — capacity is bound by your CPU, bandwidth, and egress, not by Fluxomni's software.

Latest release / September 2026

New in Fluxomni 26.3.1

Source-session contract upgrade, WebRTC program playback with route authorization, media-node compatibility, reliable live takeover, and hardened API boundaries.

Studio v26.3.1 / Core v26.3.1 / API @fluxomni/api-client@26.3.1

Sessions

Resilient source sessions

Independent source sessions preserve verified publishers across refreshes and recover from agent failures.

Playback

Play and relay Program

WebRTC program playback with HLS fallback, route ownership enforcement, and safe relay endpoints.

Fleet

Version-aware media nodes

Nodes advertise wire-contract versions and Fleet blocks incompatible execution with clear upgrade guidance.

Reliability

Live takeover and recovery

Live publishers keep priority over file fallback, preferred pulls recover automatically, and crash recovery reaps orphan processes.

Release notes ↗Full changelog ↗

Platform direction

Start with streaming. Grow into media operations.

Live multistreaming, linear channels, reusable media, and distributed fleets are available today. Future workflows build on the same self-hosted foundation.

Shipping now

  • Live multistreaming (RTMP / SRT / WebRTC ingest)
  • Linear channel playback with playlists + Google Drive
  • Artifact library with reusable local + Drive media
  • Distributed fleet with automatic failover
  • DVR recording + HLS preview

Coming

  • Advanced artifact workflows
  • Distributed render jobs
  • Event-driven automation workflows

On the roadmap

  • Expanded integrations (Slack, webhooks, object-storage backends)
  • Automated highlight generation

Building a streaming product? Help shape the next layer.

Apply for Platform Early Access