Platform

Built for regulated retail. Not adapted for it.

Purchase limits, age gates, employee attribution, and permission boundaries are structural. Every consequential action lands in a hash-chained audit record you can hand to a regulator and they can verify without trusting us.

  • Cryptographically anchored audit

    Audit events are canonicalized, Merkle-rooted, and chained to the previous anchor. Tampering with history is detectable, not merely discouraged.

  • Deterministic limits engine

    Purchase limits evaluate through a versioned, testable ruleset — same inputs, same answer, every time, with the reason recorded.

  • Isolation by construction

    Tenant and location boundaries are enforced in the data layer and the policy layer, not by remembering to add a filter.

AUDIT ANCHOR CHAIN Root verified
  1. ANCHOR 0041214:02:11Z
    events1,284 events
    prev root6b81…dd03
    merkle root9f2c…a417
  2. ANCHOR 0041314:32:11Z
    events1,097 events
    prev root9f2c…a417
    merkle rootc740…1e9b
  3. ANCHOR 0041415:02:11Z
    events1,411 events
    prev rootc740…1e9b
    merkle root3ad5…77f2
recomputed3ad5…77f2matches
Illustration of three sequential audit anchors, each referencing the previous Merkle root, with the latest recomputed root matching the stored value.

Illustrative. Demos run in a dedicated environment with our team.

In detail

What compliance covers

Hash-chained audit anchors

Events are canonicalized to a stable encoding, hashed into a Merkle root, signed, and linked to the prior anchor. Verification recomputes the root independently and reports a mismatch rather than a pass.

Versioned purchase-limit rulesets

Jurisdiction rules compile to an evaluable ruleset with its own test suite. New Mexico ships today; the authoring model exists so a new jurisdiction is a ruleset, not a rewrite.

Age and identity verification

ID scan workflows and consent capture are integrated into checkout, with the verification result attached to the transaction.

Role-based access and overrides

Fine-grained permissions with explicit manager overrides. An override is a recorded event with an actor and a reason, not an unlogged bypass.

State traceability integrations

Package and transaction data is modeled to reconcile against state traceability systems rather than being reshaped at export time.

Evidence you can hand over

Audit records are exportable and independently verifiable, so responding to an inspection is a retrieval problem instead of a reconstruction project.

See it running on real workflows.

Demos are run by our team in a dedicated demo environment, walked through live on a call — so you see the parts that matter to your operation, not a generic tour.