Deployment ownership
Put processing where your customers need it
License software for your VPC, on-premises systems, edge nodes, or appliance. Scope Linux profiles around your infrastructure and operational requirements.
Why WaveMinds
Keep control of the platform behind your product.
Choose a deployable media intelligence foundation when deployment ownership, extensibility, and integration depth are central to your product.
The decision
Own your product. Reuse a common foundation.
Media runtime, GPU processing, AI, storage, access control, and usage are closely related engineering problems. WaveMinds brings them into one platform boundary.
Integration depth
Connect models, providers, and workflows
Use composable platform plugins and independent services to fit your storage, identity, AI, key authority, and application boundaries.
Product continuity
Extend from one media foundation
Reuse CoreMF across live video, RTC, production, recording, and protection. Select the full platform or a focused SDK as your product requires.
Build vs. buy
Choose based on what your team needs to own.
Compare the integration and operating responsibilities alongside the feature list.
| Approach | Strong fit | What your team owns |
|---|---|---|
| Build from components | Media infrastructure itself is your core differentiator and you have the team to maintain it. | Media/AI integration, provider contracts, storage/index, control services, deployment, and ongoing verification. |
| Hosted media APIs | A provider-operated service matches your geography, product, and operating model. | Application integration, provider dependencies, data placement decisions, and service economics. |
| CoreMF SDK | You need an embeddable media engine and already own platform services. | Application/backend services, storage/index, identity, key/license authority, and operational integration. |
| WaveMinds Platform | You want a deployable media intelligence backend with customer-controlled infrastructure. | Your application, vertical logic, validated models, customer integrations, and selected deployment operations. |
Common questions
Make the product boundary explicit.
Start with the package, deployment profile, and evidence your team needs.
Is WaveMinds a hosted API service?
The primary product is licensed software that customers deploy in their own VPC, on-premises, edge, or appliance environment. Optional managed profiles are a future direction.
Can we use only the media engine?
Yes. The CoreMF SDK family supports engine embedding, RTC/App, Broadcast/GPU, and engine-only protected media. Use WaveMinds when you need the platform services around it.
Does the first release run natively on Windows and macOS?
The WaveMinds backend is Linux-first. Full native Windows and macOS backend packaging is deferred. CoreMF engine/SDK supports Linux, macOS, and Windows, subject to selected package and hardware profiles.
Are AI models and commercial DRM production-ready in every profile?
Readiness is profile-specific. AI requires selected production models and dataset/runtime evidence. Commercial DRM requires vendor agreements, credentials, player/device validation, and approved license flows. See release scope.
What is the release date?
The WaveMinds target release is Q1 2027. Current component verification and selected released baselines do not represent a general platform production release.
What compliance certifications are available?
Formal certifications are pending. Tenant isolation, policy, audit, and protected-media architecture support enterprise control requirements; internal QA verification is separate from external compliance certification.
Start a conversation
Evaluate the fit against your actual deployment.
Tell us about your workflow, deployment constraints, and integration needs. We will scope an evaluation around the right package and deployment profile.