Pricing and purchase

Three years saves $18,000 against three annual terms.

Renewal is a new purchase order, raised when you choose to raise it. Terms run to their end date and stop.

Activation writes a single activation file that every Reamer product on that machine reads, so Reamer Server and Reamer Research side by side consume one seat between them. To move a seat, deactivate it on the first host and activate it on the second. LICENSING.md ships in both kits with the full seat policy, term anchoring, and every activation failure mode.

• Pin a stable hostname A StatefulSet does this by construction, since pod names are stable and ordinal and the hostname follows the pod name. A Deployment assigns a fresh random name on every restart, so each restart presents as a new machine. Pair the pinned hostname with a persistent $HOME/.config/reamer.
• Or activate elsewhere and mount the result Activate once on a host with curl and a stable identity, then ship the resulting activation.json into the container as a read-only mounted secret. The running container never contacts the licence server, which suits a distroless runtime image.

Activation binds to a machine fingerprint. LICENSING.md carries the full procedure, including a manifest example and a readiness check you run inside the container across a restart.

1. 01
   Request the kit

   One email naming your company, which product, and the machine or container you will evaluate on. Kits are host-locked, so the machine determines the key.

   You
2. 02
   Kit and evaluation key

   Sent by reply. The kit carries the header, the execution specification, deployment steps, and the vendor questionnaire pack.

   Us
3. 03
   Evaluate

   Read the header, link the library, run it against your own data. Your security review gets VENDOR_QUESTIONNAIRE_PACK.md, which ships inside the kit and answers the standard vendor due-diligence questions.

   You
4. 04
   Purchase order

   Seat count and term. Sent to [email protected].

   You
5. 05
   Invoice, then payment

   Invoiced against the PO on your standard terms.

   Both
6. 06
   Licence keys

   Issued on payment, one per seat. Activation runs offline after issue, so normal operation stays entirely local to your machine.

   Us

Every step above runs over email. A call happens only if you ask for one.

Sales and commercial

[email protected]

Licensing and technical support

[email protected]

Vulnerability reports

[email protected]

Privacy and data requests

[email protected]

Covered hours

Roughly 09:00 to 18:00 UTC, weekdays

Email is the support channel. A message sent outside the covered hours is picked up at the next covered hour, so plan an escalation path that needs faster coverage for a live incident around that window. To escalate an open request, reply on the same thread marked urgent and state the trading impact.

Support is included with an active licence, rather than sold as a separate add-on or metered per incident. Requests are triaged into three tiers:

1. S1
   Production down

   A licensed, live Reamer Server instance is down or rejecting all orders.

   Priority
2. S2
   Degraded

   Partial functionality lost with a workaround available, such as one strategy instance misbehaving while others run normally.

   Next
3. S3
   Question

   No production impact: an integration question, a documentation clarification, or a feature request.

   Queued

For an incident, run bin/reamer-diag-bundle --config <path> against the affected instance and attach the resulting file. It carries a health and metrics snapshot plus retained event-bus records, with the monitoring auth token redacted.

VENDOR_QUESTIONNAIRE_PACK.md ships inside the kit and is the standing answer to a security questionnaire, support model, vulnerability disclosure policy, data-handling statement, and business-continuity review.