Connect external services

Wire up media providers, metadata sources, payments, messaging, cache, and health monitoring.

Integration Architecture Flow

Connect external services through one operating path for app settings, media delivery, metadata, payments, messaging, caching, analytics, and service health.

Platform architecture

One request path across edge, API, cache, and apps.

Cache HITViewer or admin requestWeb, mobile, TV, or CMSEdge and CDNGlobal delivery layerSecurity layersWAF, auth, rate limitsCache checkIs response cached?CMS and API computeLaravel services and jobsClient app responseBrowse, detail, playbackResponse to userSecure app experience
Fewer disconnected CDN and app rules
Shared service rules for every screen
Clear cache, response, and monitoring path
Operations can reason about the whole service

App Settings

Open App Settings to configure public-facing service identity and product controls: branding, availability, account behavior, default playback preferences, SEO metadata, support contact paths, and feature switches.

Media Providers

Configure upload providers, storage, delivery, connection tests, and provider-driven video processing in Media settings. Common options include Cloudflare Stream, R2, Bunny, and CDN-backed storage.

Provider areaOperator concern
StorageConfirm where images, subtitles, and supporting assets are stored and publicly delivered.
Video processingVerify uploaded videos are ready, playable, and linked to the correct content record.
DeliveryConfirm apps receive secure, performant playback and image URLs.

Metadata

Search TMDB, import records, handle images, and resync seasons to fill metadata quickly while keeping manual editorial control. Tune descriptions, tags, ratings, and merchandising labels after import.

Payments

Connect checkout, subscription status, plan entitlements, PPV purchases, discount codes, and payment history. Use web checkout providers for browser billing and RevenueCat to align mobile subscription events with the same entitlement model.

  1. 1Configure the offerCreate plans, prices, product identifiers, PPV rules, and discount policy in the operator workflow.
  2. 2Connect the providerOpen provider settings → align checkout, billing status, and entitlement updates with the platform.
  3. 3Verify the viewer pathConfirm web checkout, mobile purchases, account status, and playback access all agree.

Messages

Configure mail settings, email templates, notification event settings, Ably-powered live chat, and OneSignal-style push for service communication and viewer engagement.

Mail templates
Keep account, billing, support, and lifecycle messages consistent with the brand.
Push notifications
Connect OneSignal-style integrations for broadcasts, engagement campaigns, and app-level notification delivery.
Realtime chat
Enable Ably for authenticated live chat fan-out while the backend keeps moderation, token issuance, and message acceptance under operator control.

Cache Controls

Use Redis or cache controls to refresh discovery, settings, and computed data after publishing or configuration changes. Run cache tools to confirm updates are visible without exposing low-level cache structure.

Status & Domains

Open system status, domain monitoring, cache controls, and integration tests to validate production readiness before launch, during DNS changes, and after adding a new branded surface.

Installation Wizard

Run the installation wizard to connect critical media services first, then add optional services such as realtime chat when ready.

  1. 1Connect streaming servicesValidate Cloudflare Stream and image delivery settings first. Uploads, live channels, and playback depend on them.
  2. 2Complete core app settingsSet branding, domains, support contact paths, and default product settings before public launch.
  3. 3Optionally enable Ably chatAdd realtime chat from the wizard or integrations page later without blocking the initial launch path.
  4. 4Verify system statusRun connection tests and health checks to confirm all critical dependencies respond before opening the service.

Service Integration Registry

Use this registry to identify production-ready service integrations operators commonly need for a streaming business. Each item describes the service role rather than private setup details.

MetadataTMDBMovie, series, season, episode, cast, poster, and backdrop metadata import.
VideoCloudflare StreamSecure upload, encoding, signed playback, and video processing workflow.
VideoBunny StreamVideo upload, encoding, CDN playback, webhook verification, and signed HLS delivery.
ImagesCloudflare ImagesImage CDN, transformations, optimization, and global delivery for visual assets.
SecurityCloudflare TurnstileBot protection for authentication flows and public forms.
MessagingOneSignalPush notifications for mobile and TV app audiences.
PaymentsSubscription billingWeb checkout, subscriptions, PPV payments, refunds, and billing webhooks.
PaymentsPaddleCommercial checkout and subscription billing path for supported deployments.
PaymentsRevenueCatMobile subscription events and entitlement sync for app-store billing.
EmailSendGridTransactional email delivery and audience messaging integration.
EmailMailchimpBroadcast email and segment/audience marketing integration.
EmailSMTP, Mailgun, SESConfigurable transactional email drivers and template delivery.
AnalyticsGoogle AnalyticsClient-side measurement and frontend tracking for public pages.
AIClaude AIContent optimization, SEO assistance, descriptions, tagging, and editorial acceleration.