OEM
When the chart is part of what you sell
A Pro or Business license covers using ORTEX Charts inside your own application. An OEM agreement covers redistributing it: shipping the library as part of a platform you sell, embedding it in a product your customers deploy themselves, or building on the source with your own engineers. It is the only plan that puts your own logo on the chart. It is priced by the deployments it reaches, agreed in a conversation rather than a checkout.
ORTEX data can be added. The library ships without data. ORTEX is a market-data company first: the short interest, options flow, fundamentals, analyst estimates and corporate events behind app.ortex.com are published through the ORTEX API at docs.ortex.com, and an OEM agreement can add a data licence alongside the library, so the chart and the numbers you choose to put on it come under one contract.
What is included
Rights, source, and a person to call
Redistribution rights
The right to ship the library inside your product to your customers, including on-premises deployments you do not control, under terms that flow down to them.
Source access
A read-only mirror of the library source, published from the internal repository at each release. TypeScript, tests and the playground, so your engineers can read, debug and extend rather than guess.
A named engineer
One person who knows your integration, a response-time commitment, and a direct channel that is not a shared inbox.
Roadmap input
Your requirements enter the roadmap as a named commitment with a date, and features can be built to contract when the timing does not fit the roadmap.
The mirror
What source access actually looks like
Every OEM customer gets a Git repository of their own. It carries the library source and nothing else: no infrastructure, no internal planning, no other customer's name. It is published by an automated export from the release tag, so what you read is exactly what the release was built from.
# What an OEM customer clones
git clone git@gitlab.com:ortex/charts-oem/<your-company>.git
packages/ # math, core, financial, lite, ui, viz, react — full TypeScript source
examples/ # the playground, runnable
tests/ # the unit and visual suites that gate every release
docs/ # the same documentation this site publishes
CHANGELOG.md
LICENCE-OEM.md # your agreement, named to your companySource access is not a transfer of ownership, and it is not open source. The agreement names the people who may read it, forbids publication, and survives the term. In exchange, you are never blocked on us to understand a behavior.
Delivery
Three ways the library reaches you
Most customers
Hosted kit
One script tag. A per-customer build served from our content delivery network, keyed to the domains you register, updated in place within the major version.
Product teams with a build pipeline
Private registry
npm install with a token we issue. The same minified builds with type definitions, versioned, so your lock file decides when you move.
OEM only
Source mirror
A read-only Git mirror of the library source, published per release from the internal repository, with the internal material removed.
All three carry the same signed license key and the same code. What differs is what leaves our hands. The installation guide covers the first two in detail.
Practical questions
Asked in every OEM conversation
- What happens to our deployment if we stop paying?
- Use ends with the agreement, as on every plan. An OEM contract can include a run-off period so that a product already shipped is not stranded; that period is agreed in the contract rather than assumed.
- Can we modify the source?
- Yes, within your product, and we would rather you sent the change back so it survives the next upgrade. Removing the license or branding checks is the one modification the agreement names as a breach.
- Does the library call home?
- No. There is no hidden telemetry. The hosted kit is served from our network and therefore appears in our access logs, and the agreement permits an optional, documented check-in that reports a key identifier, a hostname and a version. Both are disclosed, and the second can be switched off for enterprise deployments.
- Who owns what we build on top?
- You do. Your indicators, adapters, themes and integrations are yours, and nothing in the agreement claims them.
- Is there an escrow arrangement?
- Yes, on request, for OEM agreements. The source mirror already removes most of the reason to want one.
- Can we get a security review?
- Yes. The library makes no network call of its own unless you opt in to the revocation list (one JSON read, after the key verifies), has no eval, no third-party runtime dependencies and no third-party code: every package installs with an empty dependency tree, and no file in it is copied, ported or adapted from another library, so the inventory is the library itself. We will answer a questionnaire.