Lohnt sich dein eigenes Crowdcast?

Build a closest honest personal substitute for Crowdcast in an empty repository.
Use Docker Compose, Jitsi Meet, a small Next.js 15 control panel, PostgreSQL, and TURN; do not offer alternative stacks.
The core loop is: host a small interactive live event in a private video room, issue signed room links, publish a replay, and keep recordings only when every participant is clearly informed.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Deploy Jitsi Meet through pinned Docker images and configure a dedicated TURN service.
Build an owner panel for rooms, signed invitations, expiry, lobby mode, and participant limits.
Show connection diagnostics for camera, microphone, browser, bandwidth, and TURN reachability.
Make recording disabled by default and require an on-screen consent state for every participant.
Store room metadata and audit events, but do not store media unless explicitly enabled.
Add health checks, bandwidth dashboards, backup, restore, upgrade, and incident instructions.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out a global media edge network.
Deliberately leave out public webinar scale and telephony.
Deliberately leave out regulated recording, enterprise compliance, and guaranteed support.
Finish by running the tests and listing the exact commands used.