DEV3 Technologies home

DEV3 Castember – Live Streaming Platform Laravel Script with Chat, Gifts, Gemini AI admin tools & Flutter App

Live-streaming platform on Laravel 12 and Filament 4 with Gemini AI admin tools (bring your own key): channels, live chat, gifts and payouts, replays, moderation and a language switcher. Bring your own media server. Web installer and demo data included. Flutter app source included.
by DEV3 TechnologiesVerified Author(0) 0 sales 1 viewsUpdated 15 Nov 2026

Video tour. Pick a section below to browse 48 screenshots in 6 sections.

App & phone tours

Tap play to watch each app. Nothing downloads until you do.

  • Mobile web0:18
  • Live app app1:14

Castember is the software for running your own live-streaming service. Creators go live from OBS or the browser, viewers watch and chat in real time and send gifts, and your team keeps the place safe with reports, strikes, appeals and takedowns. It is built by DEV3 Technologies on Laravel 12 and Filament 4, with a public site, a creator studio, an operator panel and one Flutter app (live) whose source is included.

What it does

  • Channels and live pages. A live-now page with LIVE badges, viewer counts and poster frames, category pages, channel pages with About panels, a schedule with reminders, and replays with chapters that creators mark during the stream.
  • Live chat that stays fair. Messages carry a server sequence number so every viewer sees the same order, and a retried send never shows twice. Realtime runs on Laravel Reverb with a polling fallback. Channels set slow mode, followers-only, link rules and a word filter, and moderators can delete, time out or ban from a mod desk.
  • Creator studio. Go live (OBS server URL and a stream key shown once after a password check, with rotation), schedule, channel profile and panels, chat settings, moderators, replays, earnings, payouts and strikes with an appeal form.
  • Bring your own media server. Two drivers: rtmp_hls for OBS into an RTMP/HLS server such as SRS or MediaMTX, and sfu for a LiveKit-protocol SFU. Playback links are signed per viewer and expire; a ban or takedown cuts a viewer or a stream off. A step-by-step guide and a webhook signature tester are included.
  • Gifts, coins and payouts. Coin packs, a gift catalogue, creator earnings in diamonds, a holding period and monthly payout batches. Money is integer minor units, a retried gift is charged once, and refunds and chargebacks claw back what was gifted. A consistency command (castember:check) reconciles gifts, coin ledger, earnings and diamond ledger.
  • Moderation. Reports with SLA timers, remove, warn, strike, suspend and ban actions, appeals decided by a second moderator, blocklists for words, patterns and files, takedowns that revoke the stream key and pause the channel, and an age gate at sign-up.
  • Gemini AI admin tools. 17 admin areas carry reviewable suggestions: explain a failed session from its event log, triage a report, draft a decision notice, summarise a creator, flag unusual earnings and more. Results open in an editable preview, are never applied on their own, and decisions taken after an AI draft are audited. You add your own Google Gemini key in Settings; the demo shows clearly labelled sample output.
  • Language switcher. A Google Translate switcher with ten languages on the public site and both panels; private pages such as chat, reports, earnings and keys are excluded. The Flutter app has its own in-app language picker.
  • Operator panel. /admin has 16 resources plus a dashboard with the Ember Bed (one glowing coal per live channel), a live monitor wall, drivers status and platform reports, split across owner, trust and safety, content operations and finance roles.
  • API. A key-based REST API with signed webhooks, and the app API used by the Flutter app.

The Flutter app

The live app (apps/live) has a viewer mode and a creator mode behind one login. Viewers browse live streams and categories, watch with live chat, send gifts, follow channels, buy coins and read their inbox. Creators see a live dashboard, their OBS server and stream key, schedule, earnings and a moderation hub with a live mod desk. Reporting and blocking are available in both modes. It starts in demo mode with bundled sample clips, has a language picker, and includes a store-publishing guide in docs/STORE-PUBLISHING.md. Going live from the phone camera is not in this version: creators publish from OBS or the web studio.

Quality checks

The release passed seven gates on the final code: Larastan level 6 with 0 errors, a Pest suite of 528 tests, a build with a small page budget and no 3D, migrations and the full demo seed on MySQL 8 and SQLite, a headless smoke test plus MySQL race checks (parallel gifts against one balance, retried gifts, parallel publishes, key rotation during a stream, payout batches against a refund, double refunds), the web installer driven from the zip, and a secret scan. The Flutter app passed analysis, 58 tests and simulator builds, and ran against the live API including chat over the WebSocket.

What you should know before buying

  • No video server is included. Live video needs a media server you run and set up as described in the documentation: an RTMP/HLS server (SRS or MediaMTX class) with a small signing proxy for OBS, or a LiveKit-compatible SFU for browser go-live. Until it is connected, going live answers a clear "not configured" message. Chat runs on Laravel Reverb (WebSockets) with a polling fallback.
  • Creators go live from OBS or the web studio, not from the app, in this version. The Flutter app watches, chats, gifts and manages a channel.
  • The demo "live" streams are a looped video on demand. The simulated driver plays sample clips as if they were live; chat, gifts, viewer counts and moderation states are real application logic. A real stream is never looped.
  • Stream keys can be rotated. A key is shown once after a password check and only its hash is stored; rotating it revokes the old key at once and ends any stream started with it.
  • Accounts under 18 cannot send gifts, buy coins or go live. Sign-up needs a birth date and refuses under 13.
  • In-app purchases need your receipt verifier. No store credentials or store code are included: you implement one ReceiptVerifier class for the App Store and Google Play, map each coin pack to its store product ids in the admin, and the in-app purchase driver refuses to enable until a verifier is bound.
  • Payments are simulated in the demo. Coins, gifts and creator payouts are simulated until you connect a payment gateway for web checkout, in-app purchases and a payout provider; the simulated drivers are refused on a live install.
  • Gemini AI admin tools need your own Google Gemini API key (Settings → AI); no key or AI usage is included. Without a key the AI buttons stay disabled.
  • A Google Translate language switcher is on the public site and admin; it needs Google's widget to load in the visitor's browser. Private areas (chat, reports, appeals, earnings, payouts, keys) are marked so their text is not sent to Google.
  • One Flutter app with source is included; it was verified in simulator builds, automated tests and against the live API, not on a physical device. Store publishing and approval are your step.
  • Use MySQL or MariaDB for a live site; the concurrency checks were run on MySQL 8. One cron entry every minute is required, and a queue worker plus the Reverb server should run under a process manager.

Included

Source code, the web installer, the Flutter app source with a store-publishing guide, a buyer guide, and demo data for a fictional service run by Emberline Live Studios Ltd: 640 channels, 28,044 viewers, 83,086 follows, 3,743 streams (10 on air) with 1,448 replays, 664,803 chat lines, 18,015 coin orders, 100,092 gifts, 845 creator payouts, 1,910 reports, 521 strikes and 131 appeals, plus six months of support.

How it's built

Architecture, stack, key decisions and the quality gates DEV3 Castember passed before release.

The engineering behind Castember: sequenced chat with a polling fallback, signed expiring playback, stream keys that are hashed and revocable, wallet-locked gifts with idempotency keys and a consistency command over 3,700 demo streams.

The problem it solves

A live-streaming service fails in loud ways: chat lines that arrive in a different order for each viewer, a stream key that leaks and keeps a taken-down stream alive, an HLS link that is shared around after a ban, a retried gift that charges twice, a creator who earns a cent too much, or a media-server webhook that is lost half way. Each case needs one winner, correct money and a record of who did what.

Architecture and approach

Castember is a Laravel 12 application with a Filament 4 operator panel and creator studio, a public site and an app API used by one Flutter app whose displayed gift maths is checked against the same test vectors as the server. Chat messages take a per-stream sequence number under a row lock and a client id is de-duplicated, so a retry shows once and every viewer sees one order; Reverb carries it live and a cursor poll takes over when the socket cannot open. Stream keys are 64 random characters that are stored only as a hash, shown once after a password check and revocable: a rotated or revoked key is refused by every media-server webhook, and a takedown ends the stream, revokes the key and pauses the channel. Playback links are signed per viewer and expire, and a ban stops working at the next playlist request. Webhooks are verified with an HMAC or a JWT, de-duplicated by event id, and answered with an error when the work failed so the media server retries. Gifts lock the sender's wallet first and re-read an earlier send with the same key. Money is integer minor units, and diamonds are floored so the pieces add up exactly. Moderation decisions, appeals and AI-assisted drafts are audited.

Quality gates and results

The release passed seven gates, including 528 Pest tests and 14 MySQL race groups run several times each (parallel gifts against one balance, the same gift key repeated, two publishes with one key, a key rotated during a stream, payout batches against a refund, double refunds, the same store receipt from two accounts). The consistency command passes on the demo data: 640 channels, 3,743 streams, 664,803 chat lines and 100,092 gifts with their coin ledger, earnings and diamond ledger.

Tech stack

Area Technologies
Application Laravel 12, Filament 4, Blade, REST API
Realtime Laravel Reverb, HLS, RTMP, LiveKit protocol
Data MySQL 8, SQLite
Frontend Tailwind CSS 4, Vite
Mobile Flutter
Quality Pest, Larastan level 6, Playwright

Inside the build

Your own live-streaming platform: Channels, live chat, gifts, payouts and replays on one site you host, with the live-now grid beside the pitch. Your own live-streaming platform — Channels, live chat, gifts, payouts and replays on one site you host, with the live-now grid beside the pitch.

Bring your own media server: OBS or the browser go live through your RTMP/HLS server or LiveKit-protocol SFU; Castember never pretends to ship one. Bring your own media server — OBS or the browser go live through your RTMP/HLS server or LiveKit-protocol SFU; Castember never pretends to ship one.

Guides & articles

Practical guides and engineering write-ups for DEV3 Castember.

Live-streaming platform software: 7 things to check before you pick a script

Last updated
Live-streaming platform software: 7 things to check before you pick a script: DEV3 Castember

Anyone can show a video player. A live-streaming service has to take a stream from an encoder, keep chat in order, cut off a bad actor quickly and handle gift money exactly. Here are seven things to check before you pick a live-streaming script, with DEV3 Castember as the worked example.

The Castember home page

Video: The Castember tour

1. Who runs the media server?

Almost no script includes video infrastructure, and none should pretend to. Castember says so plainly: you run an RTMP/HLS server for OBS or a LiveKit-protocol SFU for browser go-live, and the documentation shows how to connect it.

Drivers: which stream stack is configured, with a signature tester

2. Does chat stay in order?

Chat needs one order for everyone and no double sends when a phone retries. Castember numbers every message on the server and falls back to polling when the WebSocket is blocked.

Watching a stream with live chat

3. What happens when a stream key leaks?

Keys should be stored hashed, shown once and revocable. Rotating a Castember key ends the stream that used it.

The creator's go-live screen

4. How is the platform kept safe?

Reports, strikes, appeals, blocklists and takedowns are the minimum, together with an age gate. Be wary of any script that promises automatic detection of everything.

Strikes and their rules

5. Is the gift money exact?

Gifts, creator earnings and payouts should use whole minor units, with a retried gift charging once.

Monthly payout batches

6. Are the limits honest?

Coins, gifts and payouts are simulated until you connect payments, in-app purchase needs your own receipt verifier, and the demo streams are a looped video.

A failed session explained in an editable AI preview

7. Is there a mobile app?

Castember includes the source of a Flutter app for viewers and creators with a store-publishing guide. Going live from the phone camera is not in this version, so creators use OBS or the web studio.

Seen enough to try it? Open DEV3 Castember.

Frequently asked questions

The complete source code (version 1.0.0) as a download from your account, with the setup and usage guides shown on this page. You can modify the code to suit your product.

Buying guides: Laravel scripts with Filament panels and a web installer · Next.js or Laravel for a SaaS script?

Questions about this product (0)

Answers from the DEV3 team and the community.

Ask a question

No questions yet.

Wondering about setup, licensing or customisation? Ask, and the DEV3 team will help.

More from this author

View all

Related in Web Scripts & Software

View all