For partners
Sell the document layer, not the converters.
PDF → Markdown → compressed context → embeddings → search
Contextum is one docker compose up -d in the customer’s environment, and one HTTP call between it and your client. It fits the deployments a hosted service cannot take, and it leaves the model, the agent and the authorization exactly where they already are.
01 / Who this is for
Four kinds of partner
The product is the same in every case. What differs is who runs it and who owns it.
01
Integrators and SIs
You already own the agent stack of your customers. Contextum is the file part of it — delivered by us, deployed by you, into an environment the customer controls.
02
Resellers
You sell what you can support. Contextum is a licence with a support attachment, and the customer relationship stays with us — so the renewal is not yours to chase.
03
Technology partners
Your platform is where the documents arrive. Contextum turns them into context without asking the customer to change the model, the agent or the authorization.
04
Strategic partners
You have the reach and the expertise; we have the product and the measurements. The terms are worked out per partnership, not from a list.
02 / What is delivered
One command, one call, one licence
The delivery is a single docker compose up -d with the conversion licence inside it. The customer keeps the deployment, the database and the logs — that is what makes the partnership work in the accounts where a hosted service is not an option.
01
The pipeline
Five stages behind one HTTP call: CONVERT, COMPRESS, EMBED, INDEX, VAULT. The request names the stages and the order, and a subset can run on its own.
02
The operator console
Every job, every artefact and every stage metric, live in the browser. A SIMULATION badge appears whenever a stage fell back to the built-in simulator.
03
The conversion licence
The licence of the conversion engine travels with the delivery. Without it the service runs in a free mode with a limited document size.
04
The measurement
We run a document set of yours through the pipeline and hand over what it measured: bytes, tokens, savings, chunks, and search quality against the baseline.
The surface a partner integrates with
Six calls. What happens behind them is not part of the integration story.
| Call | What it does |
|---|---|
| POST /api/v1/jobs | submit a document and queue a job |
| GET /api/v1/jobs/{id} | the status, the stages and the metrics of a job |
| GET /api/v1/jobs/{id}/artifacts/{artifactId} | take an artefact: Markdown, chunks, embeddings |
| POST /api/v1/search | search the knowledge base of your tenant |
| GET /api/v1/meta | the option catalogue: profiles, compression levels, languages, stages |
| GET /healthz | readiness and dependencies — the only route that needs no key |
03 / How it plugs in
What stays where it is
The partner keeps everything that is already theirs. Contextum takes the file part of the request and nothing else.
The model is yours
Contextum never calls an LLM. The embeddings endpoint is yours, and the answer is produced by your agent, on your endpoint, under your policy.
The authorization is yours
Per-document access rights are not modelled by the platform — that is the agent layer’s job, and it stays with the code you already wrote.
The tenant comes from the key
Access is by a key the customer issues: <secret>|<tenant>|<scopes>|<maxJobs>. The tenant is derived from the key before anything else happens, only the SHA-256 of the secret is kept, and the key is never logged.
Two protocols
HTTP for the work, gRPC for the control, NATS JetStream inside. The same client calls it either way — there is no separate partner API to learn.
04 / The commercial terms
What the partnership is
Revenue share, counted year over year. The share is on the recurring part — support and product updates — and it is paid for as long as the customer stays.
The customer relationship stays with AnetLab. The partner introduces, deploys and supports; the renewal and the account are ours.
Licence keys: a partner can request them for a customer deployment, and the request goes through the same path as any other.
The terms themselves are worked out per partnership — the shape of the revenue share, the certification path and what the development fund covers are agreed in writing, not taken from a list.
What the product costs the partner
Nothing at the start of the relationship, and nothing per document: the customer pays for the licence and for support, the partner takes the agreed share of the recurring part, and the deployment is ordinary product work.
05 / What we bring
Two things, and they are the ones that cost us the most
01
Marketing materials
The product description, the figures with their conditions, and the claims that are safe to publish — so you do not have to write the evidence yourself.
02
A development fund
A budget for the partner-side work: the integration, the deployment, and the training of your engineers.
06 / The rules
Three rules that let you publish on your own
These are the rules we hold ourselves to, and the reason you can write your own material without asking us every time.
Do not name the conversion engine
The licence is OEM and the engine sits behind an interface. The vendor’s name is not ours to publish — in your material or in ours.
Do not publish a percentage without its condition
A saving measured on a contract is not a saving measured on a technical document: the same platform measured 0.25 % on one profile and 19.05 % on another.
Do not present a simulated stage as a measurement
Every stage returns a simulated flag. While it is set, the number is not a platform measurement — and the console shows a SIMULATION badge.
07 / Talk
Bring us a customer
The product is public, the measurements are public, and the limits are public. A partnership starts the same way a demo starts: with a document set and a question about it.
Prefer to write directly? partners@anetlab.com
What to bring
Who the customer is and what they are trying to read.
The deployment shape: the number of roles, the database, the cloud.
What you want from us: a licence key, a demo, a deployment.