Media runtime
Ingest, process, and deliver
Protocol I/O, graph-based processing, transcode/remux, recording, WebRTC/SFU, and GPU production paths.
WaveMinds Platform
The backend for your media intelligence product.
Bring media processing, GPU production, AI, protected media, storage, tenant control, and usage together in a backend you deploy and operate.
Capabilities
A platform around the media runtime.
CoreMF handles media mechanics. WMPlatform and WaveMinds add the providers and services your deployment needs.
AI runtime
Models inside the media workflow
Detection, tracking, OCR, segmentation, face embedding, pose, and customer models through composable AI plugins.
Storage & index
Connect media to its context
Local, object, and tiered storage; range reads; recording indexes; and AI event correlation. Keep media bytes in media stores and application metadata in the database.
Tenant control
Govern access and resources
JWT validation, entitlements, tenant policy, per-tenant limits, and session/device rules.
Usage & audit
Make operations accountable
Collect usage events, aggregate activity, retain audit trails, and support deployment reporting and customer billing integration.
Operational services
Run selected deployment profiles
Load balancing, CDN control, tier migration, restore/recovery coordination, and replay paths. Production release depends on profile-specific operational evidence.
Protected media
Two protection tracks. One platform authority.
Playback DRM and stream encryption solve different problems. Both use CoreMF media mechanics with platform-owned authorization, key custody, policy, and audit.
Track 01 / Protected playback
DRM for HLS, DASH, and CMAF
CoreMF encrypts and packages media with manifest signaling. WaveMinds supplies key/license services, playback sessions, entitlements, policy, audit, and provider integration. Commercial Widevine, PlayReady, and FairPlay profiles remain vendor-gated.
Track 02 / Stream crypto
Encryption inside media pipelines
Encrypt and decrypt live, internal, relay, storage, and cross-process streams with explicit graph nodes. Platform providers resolve authorized key/session contexts and rotation policy. Managed KMS, Vault, and HSM profiles need provider-specific validation.
Local ClearKey and internal verification paths provide the baseline. Review protected-media release scope ↗
Deployment
Linux first. Your environment.
The first backend release focuses on Linux servers, Linux edge systems, and Linux container profiles.
| Deployment | Fit | Release boundary |
|---|---|---|
| Customer VPC | Private cloud and enterprise media services | Select and validate Linux infrastructure, persistence, and provider profiles. |
| On premises / edge | Local processing, data residency, and site operations | Scope hardware, storage, network behavior, and operational recovery. |
| OEM / appliance | Integrators and vendors delivering a packaged system | Agree runtime capacity, redistribution rights, support, and deployment evidence. |
| Native desktop backend | Future development/demo and enterprise profiles | Full native macOS and Windows backend packaging is deferred. CoreMF engine/SDK remains cross-platform. |
Start a conversation
Build your next media product on your infrastructure.
Tell us about your workflow, deployment constraints, and integration needs. We will scope an evaluation around the right package and deployment profile.