CastFork
Solutions · Tech Teams

Ship the feature, then show your work

Launch streams, demo days, and office hours all have the same failure mode: something drops mid-broadcast and nobody notices until the replay looks wrong. CastFork is built to make that not happen, and to tell your own tools when it does.

Get started freeSee pricing

30+

Destination catalog

2160p

Passthrough ingest quality

6

Webhook retry attempts

The reliability problem

A launch demo is the wrong moment to discover a bad connection

Point whatever you already run — OBS, vMix, a CI-triggered encoder — at CastFork over plain RTMP, and a live health monitor watches bitrate, dropped frames, and per-destination connection status the whole time you’re on air, not just at the start.

  • Custom RTMP works with anything that already speaks RTMP or RTMPS
  • Encrypted RTMPS keeps your ingest secure on every plan
  • One RTMP endpoint and stream key per account, reset it anytime
Live health
Bitrate
6,200 kbps
Dropped frames
0
YouTube
connected
X
connected
Built for you

What a technical team actually wants from a streaming vendor

Bring your own encoder

No forced migration to a new production tool. Point your existing pipeline at one RTMP endpoint and CastFork fans it out.

Signed webhooks, not a polling loop

Stream started, stream ended, a destination failed, a recording finished — each POSTs to your endpoint with an HMAC signature. See the developer docs.

Recurring demos and office hours

Line up a pre-recorded release ahead of time, or just go live on the same cadence every week from Studio.

Honest about what’s Enterprise-only

A security review and dedicated infrastructure are Enterprise features today; SSO isn’t built yet on any plan — we say so on the pricing page instead of hiding it behind a demo call.

The integration problem

Your team lives in Slack, not a browser tab watching a dashboard

CastFork can call your own server the moment something happens — a launch stream going live, a destination erroring out, a recording finishing processing — so your team finds out in the channel they’re already watching instead of a CastFork tab nobody has open.

  • HMAC-SHA256 signed payloads, verified against the raw request body
  • Automatic retries on failure: 1m, 5m, 30m, 2h, then 6h
  • A delivery log shows every attempt, response code, and payload
Read the webhook docs

castfork-event: stream.started

{ "type": "stream.started", "data": { "session": { "id": "sess_9…" }, "destinations": [ { "id": "yt_1", "kind": "youtube" }, { "id": "x_1", "kind": "x" } ] } }

Tech team FAQ

What engineering teams ask first

Reliability

The live health monitor flags it immediately, and if you've set up a webhook endpoint, a destination.failed event fires with the error code so your on-call channel finds out in real time.

No. Custom RTMP works with any encoder that outputs a standard RTMP or RTMPS stream — point your current pipeline at CastFork's ingest URL and nothing else changes.

Integration

Yes — set up a signed webhook endpoint under Settings → Webhooks, subscribe to stream.started (and whichever other events you want), and have your own server relay it to chat.

Not yet on any plan — SSO isn't built today. A security review and dedicated infrastructure do ship on Enterprise. We'd rather say that plainly than bury it in a sales call.

You can line up a pre-recorded release ahead of time from Upload & Stream, or just go live from Studio on the same weekly slot — either way there's no per-event setup cost.

Launch day shouldn't be a lesson in your own infrastructure

Free covers two destinations at once, no time limit, no card required.

Get started free