Availability & qualification
Preparing CoreMF for commercial release.
The first commercial release is targeted for Q4 2026. SDK and container candidates have recorded packaging and local verification. Final timing depends on release qualification and approval; public availability will be announced here.
Looking for a capability? Browse the searchable feature index ↗
Delivery at a glance
Check availability for your media solution.
| Area | Current position |
|---|---|
| SDK / Runtime / Server | Linux x86-64 packaged candidates with scoped local checks. Commercial release approval remains pending. |
| Application versus extension | Delivery contents and API/extension access are described separately. |
| Other targets and optional packs | Native Windows/macOS verification is confirmed. Delivery uses a matching platform package; ARM64 and optional language/AI packs need their own qualification. No default Python AI pack. |
| Current limits | Dynamic MCU/HD capacity, cloud/TURN, production WHIP and broad GPU/provider/player compatibility are not established by the local baseline. |
| Customer evaluation | Default limits: 30 days from build issuance, up to 1280×720 video and five minutes per graph or service session. Linux SDK/demo enforcement is verified; supplied builds record their settings. Evaluation access is arranged before delivery; no public trial download yet. |
Cross-platform engine, version-specific delivery.
- Ubuntu 24.04 / x86-64
- Recorded clean installed-SDK checks and Linux container baseline. Support remains tied to the exact package and workload.
- Ubuntu 22.04
- Linux compatibility target. Requires a matching SDK/runtime build and target-host verification; no retained installed-package pass is claimed for this version.
- Ubuntu 26.04
- Linux compatibility target. Requires its own dependency/toolchain and installed-package qualification.
- Windows
- Native verification confirmed November 3, 2026. Delivery follows the selected package, toolchain and feature profile; this is not qualification of every codec or GPU.
- macOS
- Native verification confirmed November 3, 2026. The supplied artifact, toolchain and enabled features determine delivery scope.
- ARM64 and services
- ARM64/embedded targets need their own artifacts. CoreServer and the current Runtime/Server containers target Linux; Linux Docker evidence does not qualify native Windows/macOS.
October 27: local Linux baseline, soak and scan
Historical baseline
CoreMF 0.4.0: 37 local checks plus a one-hour CPU RTC/SFU soak with four publishers/four viewers. These results do not qualify the October 29 rebuild.
Artifact hashes, test conditions, reconnect limits, latency/RSS measurements and scan findings are in the engineering appendix.
October 29: rebuilt packages and browser-effects checks
Separate package and browser records
Eight tier/module archives, relocated consumers and 18 packaging regression tests; 120 browser-effect checks on Linux Chrome/local CPU SFU. See the dated scope.
These checks do not renew the earlier soak/security scan or establish end-to-end RTC latency and broad browser/device support.
Installed SDK and native plugin integration
A recorded application-extension path
The release record documents a native ABI template compiled from the source SDK and loaded through the installed API runner to process real video. Decoded output matched the no-plugin path frame-for-frame.
This is native-video evidence for that package/interface. It does not qualify Python/JavaScript, audio sample processing, arbitrary customer plugins or an AI model pack. Matching plugin development materials and rights are selected separately.
Compare media-access interfaces ↗Feature limits to check before deployment
- RTC/SFU: local CPU evidence does not qualify cloud/TURN, network faults, dynamic MCU or production capacity.
- CoreGL / hardware codecs: qualify the actual device, driver, transfers and workload.
- LL-HLS / WHIP: LL-HLS playback/timing is profile-specific; WHIP is preview/development-only.
- Product finishing: GPL-only grading/CDL paths and optional advanced color-management integrations are excluded.
- DRM / stream crypto: production key authorities, CDMs and player/provider interoperability need separate qualification.
RTC reference applications
Camera effects before transmission.
Off, Blur, Hide and image replacement process the camera in the publishing browser. Reviewed segmentation assets are served locally; the selected image remains in the browser. Processed video travels through normal RTC publication.
Formal recorded scope is Linux Chrome/local CPU SFU. Broader device testing is separate. Segmentation can leave visual artifacts; it is not guaranteed background concealment. Worker OffscreenCanvas/WebGL2 and adequate device resources are required.
Packaged RTC menus hide Meeting Server MCU GPU/CPU entries; both remain visible in development.
Deployment responsibilities
Native plugins are trusted in-process code. The deployment must provide authentication, TLS, supervision and capacity management.
Threading, transfers, recovery and shutdown behavior are configuration-specific. Follow the API lifecycle contract and retest affected profiles after runtime or pipeline changes.
Package exclusions
Keep internal tools out of customer delivery.
CoreStudio, MVP, the internal graph UI and internal QA/tools/docs are excluded. Reference-only privacy/video-quality integrations, AGPL-dependent AI configurations and customer GPL encoder executables are also excluded.
The native engine and selected language bindings are separate from those applications. Storage, indexing, tenant billing and platform operations are outside SDK scope.
Build with CoreMF
Discuss a supported configuration.
Confirm the package identity and acceptance criteria for your target workload.