A licence to start. A royalty per device after that.
The licence gives access to the engine and its endpoints. The royalty is charged on each device that ships. The same pattern the industry uses to license its best designs.
Two steps. Agreed once, then per device.
The same pattern the industry uses to license its best designs.
Agreed once, for a defined scope.
- The engine and its endpoints
- The SDK and reference designs
- Engineering support
Charged on each device that ships with the engine inside.
Illustration. No rates are published. The royalty basis is to confirm.
Licence types
Evaluation, product, portfolio and academic. More structures are coming.
| Evaluation | Product | Portfolio | Academic | |
|---|---|---|---|---|
| Who it is for | A team testing the engine before a product decision | One product line shipping the engine | Several product lines under one agreement | Research and teaching |
| What you get | An environment, the SDK, your own files | The engine, the endpoints, reference designs | Everything in Product, across the portfolio | [To confirm] |
| Fee | A fixed evaluation fee | A licence fee | One licence fee | [To confirm] |
| Royalty | None | Per device shipped | Per device shipped | [To confirm] |
| Term | [Weeks, to confirm] | [To confirm] | [To confirm] | [To confirm] |
| Support | Onboarding | Implexus engineering | Implexus engineering, named contact | [To confirm] |
Licences are subject to agreement. No rates are published. Cells marked [to confirm] are for the licensing team to complete.
How it starts
From a first conversation to devices in the field.
- Week 0Talk
Tell us what you build, and where it ships.
- Contact form
- A licensing lead replies
- [Weeks, to confirm]Evaluate
Test the engine on your own files.
- Evaluation licence
- app.implexus.io
- SDK
- [Months, to confirm]Build
Build on Safe, Relay and Forge with Implexus engineering.
- Product or portfolio licence
- Reference designs
- OngoingShip
Devices ship with the engine inside.
- Royalty per device
Durations to confirm with the licensing team.
What a licence includes
The Q⁴ Data Engine, for the scope agreed.
Safe, Relay and Forge, in one SDK.
Tested starting points for common builds.
Ready environments on app.implexus.io.
From the Implexus team.
New engine releases within the licence term.
To confirmInclusions vary by licence type. To confirm.
Build it in with a partner
Silicon, system, firmware and cloud partners. Categories, not tiers.
The partner networkPlace the engine on their parts.
Build devices and systems around it.
Integrate it below the operating system.
Run it as a service for their customers.
Questions about licensing
Draft answers. To confirm with the licensing team.
Why a royalty per device?
It ties what you pay to what you ship. A team pays a licence to start, and the royalty grows only as devices with the engine inside reach the market.
What counts as a device?
[Definition of a device for royalty purposes: to confirm.]
Can an evaluation become a product licence?
Yes. Most teams start with an evaluation and move to a product or portfolio licence when they decide to ship.
Do you publish rates?
No. Rates are agreed per licence.
Who signs the licence?
[Licensing entity within the Implexus group: to confirm.]
Start a licensing conversation.
Tell us about your company, what you are building and which endpoint it needs.