CoreMF products & licensing

One CoreMF engine. Choose your license.

Compare deployment and redistribution rights, with planned SDK and container delivery.

Commercial licensing

Choose the rights for your deployment.

CoreMF is proprietary commercial software. These four license tiers apply to the selected SDK or container delivery. Pricing is agreed directly through annual licenses or hardware royalties.

Startup

Operate an early deployment.

Annual license

Up to 10 software nodes for eligible hosted/internal use. Software-product and hardware redistribution are excluded.

Contact sales ↗

Commercial

Ship your software product.

Annual license

Unlimited software deployment and software-product distribution within the licensed scope. Hardware redistribution requires OEM or Enterprise rights.

Contact sales ↗

OEM / Embedded SDK

Build CoreMF into your device.

Per-device royalty or annual flat rate

Commercial software rights plus redistribution of runtime binaries inside agreed customer hardware products. Products, volumes and fees are specified in the agreement.

Contact sales ↗

Enterprise

Agree broader product coverage.

Annual license

Unlimited software nodes and OEM redistribution within the agreed enterprise scope, with negotiated hardware coverage, support and escrow terms.

Contact sales ↗

The signed agreement defines the licensed customer, products, node counting, coverage, delivery artifacts and fees.

Support, source access and renewal terms
Topic Commercial structure
SDK and containers The tiers apply to the selected SDK or container delivery. Optional source, bindings and AI packs are selected separately.
Support and ABI The offer includes priority email support with a 48-hour response and a quarterly C ABI stability commitment. The agreement defines coverage hours, supported versions, severity and scope.
OEM integration Agreed device/toolchain scope, custom SoC builds on request and quarterly royalty reporting. Requested targets need qualification.
Enterprise support Named support engineer, a 4-hour critical-response SLA within agreed coverage, quarterly roadmap sessions and one annual on-site integration workshop, subject to agreed capacity and terms. A response target is not a resolution deadline or a hosted-service uptime guarantee.
Source access and escrow Source-code delivery requires separate proprietary source rights. Enterprise escrow is conditional source release under its terms, rather than immediate source access.
Renewal Deployment rights after expiry, new deployments, updates and continued support are defined before contract signature.
Media runtime, customer encoders and third-party rights

The commercial SDK dynamically links an audited LGPL-compatible media runtime. Applicable third-party licenses, notices and corresponding-source materials accompany the selected delivery; third-party rights remain separate.

Customers can provide compatible encoder executables at runtime. Those executables are not bundled with the commercial SDK, linked into CoreMF at build time or loaded as customer encoder libraries.

Executable interoperability does not automatically place CoreMF under the GPL. Actual coupling and distribution still determine the applicable obligations; custom-worker arrangements require their own review.

CoreMF licenses its own technology. Codec patent rights and other third-party permissions are not implicitly included. Consulting deliveries are governed by their agreements and selected dependencies.

Delivery formats

Receive CoreMF as an SDK or container.

Embed

Media SDK

Integrate graph control and media processing inside your application through the public API and selected bindings. Your team builds the application logic and UI.

Included materials
  • CoreMF shared library and CoreMF_API.h
  • CMake/pkg-config metadata, API docs and selected examples
  • Graph JSON assets and API-based runner
  • Matching audited media runtime and required third-party materials
Explore SDK integration ↗

Run pipelines

Runtime Container

Run file, network and Graph JSON pipelines as media jobs or workers in your infrastructure. Your application supplies job orchestration, storage and service policy.

Included runtime

API-based runAPI runner, media runtime and required dependencies. Application development headers are supplied with the SDK.

Try a processing example ↗

Serve applications

Server Container

Start from an API-driven media and RTC backend. Your team integrates identity, application policy, network configuration and service operations.

Included server scope

CoreServerAPI adds reference HTTP/media sessions, selected browser reference clients and signaling. The customer configures authentication, TLS, secrets and network/TURN connectivity, and manages capacity.

Explore media-server solutions ↗

These are delivery options for the same engine. Features, operating systems and dependencies follow the selected build. Check platforms and availability ↗

Bindings, plugins and source options

Select application bindings and matching plugin interfaces for custom video frame and audio sample access. Optional AI processors/models and proprietary source delivery are agreed separately; no Python AI pack is included in the base candidate. Explore extension interfaces ↗

Your next step

Evaluate the fit or discuss your integration.

Evaluate CoreMF

Choose relevant capabilities and request the matching SDK or runtime under the current availability limits. Default evaluation limits are 30 days, 720p and five minutes per graph or service session, subject to the supplied build and terms. Evaluation does not grant production, redistribution or source rights.

Plan your evaluation ↗

Need project-specific engineering?

Commission customization, product integration or performance and deployment work. Services are optional and quoted under a separate project agreement with defined deliverables and rights.

Explore engineering services ↗

Build with CoreMF

Find the fit for your product.

Tell us your project, target platform and deployment model.

Discuss your project ↗