Release status

Target release: Q1 2027.

WaveMinds is in pre-release. The target is a Linux-first, deployable media intelligence backend, with package scope and production evidence defined per deployment profile.

Pre-release · Platform target Q1 2027

Buyer summary

A release target with explicit delivery boundaries.

The product definition describes the intended platform. Implementation, verification, deep review, and release are separate states.

Area Current posture Release focus
Core platform CoreMF integration, plugin contracts, and runnable service baselines are in place. Select Linux deployment profiles, install/runbook evidence, persistence/providers, and retained operational verification.
Selected released baselines Local/CoreMF logging, selected local/local-compatible stores, and local/file-backed load-balancer coordinator. These component profiles do not imply a generally released WaveMinds Platform.
Services & reliability Runnable product and reusable services are deep-reviewed for selected current profiles. Production restart/failover behavior, deployment runbooks, selected persistence, and retained evidence.
Backend platforms Linux-first backend and Linux container/runtime profiles. Native macOS dev/demo and Windows enterprise/OEM backend profiles are deferred; CoreMF engine/SDK remains cross-platform.

Protected media

Local/internal baselines first; commercial profiles by evidence.

Treat DRM playback and stream crypto as separate evaluation tracks.

DRM playback

Select vendors, players, and license flow

Local ClearKey/internal verification is the starting point. Commercial Widevine, PlayReady, and FairPlay profiles require vendor approvals, credentials/certificates, license-path validation, and real player/device evidence.

Stream crypto

Select key custody and runtime profile

Local/internal encryption paths have verification evidence. Managed KMS, Vault, HSM, customer key custody, and regulated/FIPS profiles require selected-provider operational and security evidence.

AI scope

Integration baselines need production model evidence.

The plugin layer and CoreMF Python processor registry provide the integration foundation. Release selection is specific to the algorithm, model, runtime, and product use.

  1. 01

    Select the model and package

    Define the algorithm, runtime, hardware, dependencies, and distribution rights.

  2. 02

    Connect platform controls

    Integrate tenant policy, usage, media/event indexing, and privacy behavior.

  3. 03

    Retain use-case evidence

    Validate dataset-backed accuracy, performance, resource use, and failure behavior for the selected deployment.

Enterprise readiness

Verification and compliance have different scopes.

Internal QA establishes build/runtime behavior. Formal external certifications and vendor approvals have their own requirements.

Formal SOC 2, ISO, HIPAA program/BAA capability, FIPS validation, and other external compliance certifications are pending. Architecture and internal verification should be evaluated against the controls and procurement needs of your deployment.

Evaluation should identify the package, deployment topology, models, key/DRM providers, persistence, hardware, operating runbooks, and evidence required for your rollout.

Future directions

Additional product lanes remain on the roadmap.

Game SDK, cloud gaming, and AR/VR/XR are future expansion directions. They are outside the first WaveMinds platform release commitment.

Review the defined product packages ↗

Start a conversation

Plan an evaluation before your production rollout.

Tell us about your workflow, deployment constraints, and integration needs. We will scope an evaluation around the right package and deployment profile.

Discuss your project ↗