Evaluation console: every document here is a mock-up we made up, and every check on this page runs as pure code inside this container — no model, no model client, nothing leaving the process — but this copy sits on our server, so please keep real client data out and run the licensed appliance inside your own network. How this works · Privacy.

From this page to a running appliance

How you get it, and what happens when it ends

Five steps, no account to create and no sales call in the middle of them. Each one says what we do, what you do, and which clause of the licence it comes from.

The whole journey

  1. 1

    Try it here, on the samples or on your own file

    You are on the evaluation console now. Nothing to sign up for. Use the supplied documents, or bring your own — but not real client data, because this copy runs on our server rather than inside your network (clause 13.2).

    Open the console →

  2. 2

    Tell us you want one

    The enquiry form on the console takes three things: a work email, your firm's name, and your FCA firm reference number if you have one. We receive exactly those and nothing else — no IP address, no record of what you clicked (clause 13.5). You get an automatic acknowledgement straight away, and a reply from a person.

  3. 3

    Pick a plan and pay the proforma

    Three plans, priced in pounds, on the licence page: £1,200 a month rolling, £850 a month on a twelve-month term, or £695 a month paid a year in advance. We issue a proforma invoice carrying the plan, the terms and the quality clauses as an addendum. Paying it accepts the agreement (clause 5).

  4. 4

    Delivery, normally within one business day

    One email, with four things in it (clause 6.1):

    • the container image reference, and its sha256 digest, so you can pin exactly what you ran;
    • your signed licence key file;
    • the run guide;
    • the countersigning public key, for the monthly quality statements.

    Nothing is shipped physically and we install nothing on your systems.

  5. 5

    Run it, and check it yourself

    Put the key where the appliance reads it and start the container. It verifies the signature on your own machine and calls nobody to do it (clause 6.2).

    docker pull <image>@sha256:<digest>
mkdir -p config && cp license.key config/
docker run --rm -p 127.0.0.1:8000:8000 \
  -v "$PWD/config:/app/config:ro" \
  --network none \
  <image>@sha256:<digest>

    --network none is not a typo. The validation engines make no outbound call at all, so the appliance works with the network switched off entirely. That is the quickest way to satisfy yourself that clause 3 is true rather than merely written down. Then open /trial: it will say licence state: valid and show the date it expires.

When the licence ends

Whether it expires, you do not renew, or either of us ends it early — this is what the copy on your machine does (clause 6.5). There is no remote kill switch, because there is no connection to send one down.

It stops processing

POST /v1/* answers HTTP 402, naming the date that passed and who to contact. It does not crash, and it does not go quiet.

It can still explain itself

Health, the docs, /trial and the monthly Quality Statement keep answering, so you can close your own records and evidence any claim.

It deletes nothing

Your documents, results, ledger and reports stay where they are and stay yours. We hold no copy, and never could.

It sends nothing

Expiry is a date comparison on your machine, not a message to us. Your own API credentials are untouched throughout; remove them when you decommission.

You then stop using it and remove the image and the key within 30 days.

What you may do with it

The short version of clause 12. It is yours to run for your own business, on your own machines, on your own data.

Yes
  • As many of your own users and as much throughput as your machines will carry.
  • No per-user, per-record or per-call charge. We do not meter you — we cannot, we receive nothing.
  • Your own data, and any data you are authorised to process.
  • Anywhere in your own group.
No
  • Running it as a bureau, processing other firms' data as a service.
  • Sharing the licence key outside the entity it was issued to.
  • Working around the expiry, or running on after the licence ends.
  • Publishing a benchmark of it without asking us first.

Your model credentials, your bill. If you run an edition that calls a model provider, you supply your own API key and contract with that provider directly. You set the spend and rate limits. We have no visibility of what it costs you and no liability for it, including spend caused by your own automation or a misconfiguration (clause 12.3).

Every month, the appliance reports on itself

You do not have to take our word for the quality, and you do not have to send us your data to prove it. The appliance keeps its own score on your machine and produces a statement of counts — never content — that you choose whether to send us (clauses 9A and 9B).

  1. At month end, export the Quality Statement from /trial/statement.
  2. Email it to us if you want to claim a credit, within 14 days.
  3. We check it against the month before and countersign it.
  4. If the Engine Quality Score fell below 99.5%, or the self-test failed two days running, that month's fee is credited.

Questions before you commit

Read the licence in full — it opens with a one-page summary — or the trust centre, where every claim about the data boundary is checkable from the page itself. Otherwise, write to hello@apexdatarouting.co.uk.