Skip to content
Creation1618
Creation1618

Verifiable
by design.

An Australian technology group building verifiable systems of record — cryptographic proof, event-sourced data, open standards.

Request a demonstrationFive product lines
Product lines
Five
Public standards implemented
17
Specifications published
Two
Built in
Australia
Two solids, one shared corner — nothing hidden.

Most business software asks you to trust what it reports.

Ours record what happened, then hand the party who has to rely on it a way to check the result themselves.

Cryptographic verification

Hash-chained, append-only records. On AllotX and AssetDNA the head is timestamped by an independent RFC 3161 authority, proven against a live public one — and where no authority is configured the surface says “pending” instead of claiming a timestamp.

Event-sourced by construction

The log is the source of truth and every view is derived from it, so the audit trail is not a feature someone remembered to add — it is the thing the product is made of.

Deterministic intelligence

Scores, confidences and projections are computed by rules that print their own working and refuse when the data is too thin. No model sits between your record and the number on the screen.

Open standards, not lock-in

GS1 EPCIS 2.0, GS1 Digital Link, Peppol UBL 2.1, JSON Schema 2020-12, OAuth 2.0, RFC 3161 — records leave in formats other systems already read.

Tenancy as a boundary

Per-tenant isolation, role-scoped access, AES-256-GCM on stored credentials, signed expiring embed tokens, hashed API keys, and an audit trail over access as well as change.

Portable by default

Full export at any time in a documented open format. On AssetDNA and EarthX the verification recipe ships with the export, so it stays checkable after you stop being a customer.

Public standards implemented across the family

  • AES-256-GCM
  • Australian Privacy Principle 12
  • GHG Protocol Scope 1/2/3
  • GS1 Digital Link
  • GS1 EPCIS 2.0
  • HMAC-SHA-256
  • ISO 4217
  • JSON Schema 2020-12
  • JSON-LD
  • JWS HS256
  • OASIS UBL 2.1
  • OAuth 2.0
  • Peppol BIS Billing 3.0
  • RFC 3161
  • SDMX-CSV 2.1
  • SHA-256
  • W3C Web Push (RFC 8291/8292)

Implemented against the published specifications. No conformance certification is held or claimed.

The suite

Five product lines

Architecture and technology profiles
Pilot-readyAssetDNAThe verifiable operating record of a building.Property & built environment · Finance & investment · Environmental technologyExplore Working buildTXRAWho held what, and when — provable on demand.Finance · Property & infrastructure · AI & digitalExplore Pilot-readyAllotX + BPNPromotions and rewards a participant can check for themselves.Retail & hospitality · Financial services · Digital platforms & AIExplore Working buildTraceX + CrestXCustody and evidence, from the factory floor to the invoice.Smart logistics & supply chain · Agritech & food · Advanced manufacturingExplore Early buildEarthXEveryday actions, turned into assurance-ready evidence.Environmental technology · Finance · AI & digitalExplore
The technology

How a record becomes checkable

The full technology picture

  1. Two of our specifications are public right now — AssetDNA’s export format and its inbound connector contract — and the connector ships an in-browser conformance validator you can run against your own feed before you ever contact us.

  2. An AssetDNA record export is checkable offline with standard tooling in any language, so the verification does not depend on our systems, our company, or our continued existence.

  3. TraceX emits supply-chain events and invoices in open external standards we do not control, so your records leave in formats other systems already read.

  4. Independent third-party timestamping is claimed only where it is actually implemented: AllotX and AssetDNA. Every other platform keeps a tamper-evident record without that layer, and each page says so.

Four steps, four gates

What each gate is for

  1. 01

    See it

    Open to anyone. No agreement, no account, no sales call.

  2. 02

    Assess it

    A mutual NDA — so we can answer specifics rather than generalities, and anything confidential you tell us is protected the same way.

  3. 03

    Trial it on your data

    An evaluation agreement: evaluation-only use, your data stays yours and leaves with you, and the tenancy expires on a fixed date.

  4. 04

    Deploy it

    A licence and an implementation plan with named owners and dates on both sides.

Sydney, August 2026

Vietnam – Australia Tech Connect Forum

10 August 2026 · University of Technology Sydney

Book a meeting at the forum

  • Pilot on your own data

    A scoped, time-boxed evaluation tenancy on one product line, one building, one programme or one campaign. You keep everything you put in, and you keep everything that comes out.

  • Distribution, white-label and joint venture

    Several of these platforms are designed to be run under someone else’s brand, or embedded inside a product that already has the customers. A local partner keeps the licence, the customer relationship and the market knowledge.

  • Research and standards collaboration

    Grading how strongly a claim is evidenced is an open research question, not a solved one. We would rather argue about the grading ladder with a university than defend it alone.

Pick the conversation that fits.

See a demonstration

Any platform, on our demonstration data, with your questions driving it.

Request a demonstration

Propose a pilot

One product line, one building, one programme. Time-boxed, on your data.

Start a pilot conversation

Take the overview

A printable, non-confidential overview to forward internally.

Open the overview