Skip to content
Creation1618
Creation1618

The platforms

Each runs standalone — its own login, its own data perimeter, its own agreement.

White institutional architecture against an open sky

TXRA

Pilot-ready

Real-world assets, tokenised and issued with enterprise layers of proof — every deal sealed, every investor able to check it themselves.

How it runs

Technology profile

Architecture
Multi-tenant cloud platform over a managed relational system of record, with one product across web, iOS and Android.
The record
An append-only event ledger plus a separate append-only administrative audit trail that cannot be updated or deleted — including by an administrator.
Verification
Record integrity can be recomputed from an export by an outside party, and verification runs inside the product. Independent third-party witnessing is built and exercised against real authorities; it switches on per deployment.
Intelligence
The analytical core is deterministic, not learned: feasibility, triage and risk are rules-based screening that shows its working and a reviewer can override. A language model drafts and extracts; it never decides.
Integration
Bank-feed capture is built against Australia’s Consumer Data Right and consumed through a third-party accredited data recipient. Full self-service export under Australian Privacy Principle 12.
Security
Isolation enforced across the whole data model rather than page by page, role-and-permission access control, per-tenant scoping on every deal surface, encryption in transit and at rest, self-service export and account deletion.

Public standards implemented

  • SHA-256
  • Australian Privacy Principle 12

Implemented against the published specifications.

Every screening result shows the reasons that produced it, and a human can override any of them on the record. A language model drafts and extracts; it never decides, and the product runs rules-only without it.

Sectors
Finance · Property & infrastructure · AI & digital

Rows of archived records filed on their edges, receding into the distance

Attest1618

Pilot-ready

The enterprise engine for evidence and proof — sealed, handed over, and checked by the other side.

How it runs

Technology profile

Architecture
A layer beneath the operator’s own product: sealing runs where the records live, and the check runs on the counterparty’s machine.
The record
Evidence sealed into portable documents over an append-only record, with a published record of checks.
Verification
By the holder, offline, with the free published kit — a one-file verifier, a receipt that re-checks itself in any browser, and independent timestamping.
Intelligence
No model in the evidence path. Every verdict is arithmetic the counterparty can re-run.
Integration
Consumed through a published surface — the same one the family’s own platform buys through. Documents are plain, open files; nothing proprietary to hold, forward or verify one.
Security
Every document names its issuer, demonstration data declares itself inside the seal, and partial disclosure never hides that it is partial.

Public standards implemented

  • SHA-256

Implemented against the published specifications.

Deliberately model-free: the counterparty can re-run every check, and the verifier reports what it did not check.

Sectors
Finance & investment · Government & public sector · Property & built environment · AI & digital

A circular library, shelves of volumes curving around the reading floor

Seal1618

Pilot-ready

The enterprise protocol for records that authenticate — stamped, sealed, and accepted on sight. Your records keep their value after every contract ends.

How it runs

Technology profile

Architecture
Not an application: a published protocol — versioned formats, a verification recipe, a reference verifier and samples, all public.
The record
Plain, open documents that carry their own integrity.
Verification
Offline, free, by anyone — specified precisely enough to implement independently.
Intelligence
None, by definition. Every verdict reproduces identically in any conformant implementation.
Integration
Implementable in any language from the specification alone; the samples are the fixtures to check against. No licence to verify, none to implement.
Security
The trust model is written down beside the formats: what a seal proves, what it cannot, and the claims we refuse to make.

Public standards implemented

  • SHA-256

Implemented against the published specifications.

A protocol earns trust by being reproducible: two strangers running two implementations reach the same verdict on the same document.

Sectors
Government & public sector · Finance & investment · AI & digital

A pipette dosing sample wells in a laboratory

CrestX + TraceX

Working build

Scientific research, findings, record keeping and compliance out front — with the contract, manufacturing, logistics, finance and administration layer underneath.

How it runs

Technology profile

Architecture
Two multi-tenant applications. TraceX is event-sourced and built to be embedded — widgets, an SDK and a REST API; CrestX runs behind a closed perimeter.
The record
TraceX keeps a per-tenant append-only event log as the source of truth — editing history is refused, not merely discouraged — with every view derived from it. CrestX keeps a per-tenant activity ledger plus a content fingerprint on each evidence item.
Verification
TraceX re-walks its whole event chain on demand behind an authenticated check, and serves an unauthenticated per-unit provenance page addressed by GS1 Digital Link. CrestX re-verifies its own chain and fingerprints on screen.
Intelligence
Deterministic and explainable, not learned: TraceX scores a match into a confidence figure that prints its own reasons; CrestX scores evidence into a transparent provenance readout capped by its strongest tier.
Integration
Open-format exports, route-served: GS1 EPCIS 2.0 traceability documents in JSON-LD, Peppol BIS Billing 3.0 / UBL 2.1 invoice XML, and GS1 Digital Link identifiers. Accounting-connector integration is built against OAuth 2.0.
Security
Per-tenant isolation applied uniformly on every data access path, role-scoped party portals, read-only reviewer rooms, passwords and API keys never stored in a readable form, embeds that expire on their own, and stored credentials encrypted at rest.

Public standards implemented

  • GS1 EPCIS 2.0
  • GS1 Digital Link
  • JSON-LD
  • Peppol BIS Billing 3.0
  • OASIS UBL 2.1
  • OAuth 2.0
  • SHA-256
  • AES-256-GCM

Implemented against the published specifications.

Both products score their records — settlement confidence in TraceX, evidence strength in CrestX — with deterministic logic that shows its working, rather than a black-box model.

Sectors
Health & life sciences · Research commercialisation & technology transfer · Agritech & animal health · Smart logistics & supply chain

Earth from orbit in daylight, blue ocean under white cloud

Earth1618

Working build

Carbon calculators, waste avoidance, compliance and industry monitors for Scope 3 — the number you publish is one you can stand behind, and the team that traces every number owns the conversation with its assurer.

How it runs

Technology profile

Architecture
One product across iOS, Android and web, over a multi-tenant relational design.
The record
An append-only evidence chain over graded emissions records and the reductions and retirements applied against them.
Verification
An outsider re-derives the whole chain offline from a published pack format — a JSON Schema and a one-page algorithm. No external timestamping is wired, and none is claimed.
Intelligence
Deterministic, not learned: provenance-weighted confidence grading over published emission-factor arithmetic, with the grading rules published in the pack specification so an assurer can re-run them.
Integration
Manual, spreadsheet and connector capture in; an open self-verifying pack and spreadsheet-friendly export out. Bank-feed capture is written but credential-gated and inactive.
Security
Per-tenant isolation across owner, admin, member and auditor roles, with edits and deletions against the evidence chain refused outright rather than logged.

Public standards implemented

  • JSON Schema 2020-12
  • SHA-256
  • HMAC-SHA-256
  • GHG Protocol Scope 1/2/3

Implemented against the published specifications.

The evidence engine is deliberately deterministic — every score and every figure is a rule an assurer can re-run and reproduce exactly, with no model in the loop. Language models appear only in optional back-office assistants that draft copy for a human to approve, never to grade evidence.

Sectors
Environmental technology · Finance · AI & digital

Glass towers seen from the street, dark and mirrored

AssetDNA

Pilot-ready

The sealed vault for anything that must stay intact, and the verifiable operating record of an asset, and information of high value and importance. Keep it safe. Prove it later.

How it runs

Technology profile

Architecture
Cloud-hosted and API-first, over a relational system of record, with verification running on a schedule rather than on request.
The record
An append-only operating record — tamper-evident, and exportable in full at any time.
Verification
Timestamped by an outside authority, so a counterparty re-derives the record offline, without us, using standard tooling.
Intelligence
Deterministic, not learned: every answer is computed from the record and shipped with its citation, and the projection declines to answer when the history behind it is too thin.
Integration
Read-only, one-way connectors — nothing we hold can write back into your systems. A published inbound contract and export schema (JSON Schema 2020-12), an accounting link, a key-authenticated read API and open-data feeds.
Security
Per-tenant isolation with role-based access, encrypted in transit and at rest, and every share scoped, time-boxed and revocable — with an audit trail over who looked as well as who changed.

Public standards implemented

  • JSON Schema 2020-12
  • OAuth 2.0
  • SHA-256
  • SDMX-CSV 2.1
  • ISO 4217

Implemented against the published specifications.

Every figure is computed from the verified record and shipped with its citation. The forecast refuses to answer when the history behind it is too thin — a property we consider a feature.

Sectors
Property & built environment · Finance & investment · Environmental technology

An analytics dashboard of charts and figures on a laptop, on a bright desk

Cup

Working build

The personal investment desk for the busy individual — one person’s assets, read clearly every morning, in one place.

The technology

Built so the other side can check it

Two decisions we will defend in the room. Everything shown is in the build today; where a capability is dormant until configured, it says so.

Timestamps from someone who is not us

Everything a blockchain promises the party relying on a record — history that cannot be quietly rewritten, time that cannot be backdated, proof that asks no permission — with no node to run, no token to hold and no chain governance to trust. Where a platform does not have this, its profile above says so.

AI where it cannot fabricate

A lender, an assurer or a regulator has to be able to re-run the arithmetic. A black box cannot be re-run — so it is the wrong tool for the load-bearing part.

An interface you can hold us to

Open formats and public verification — designed to be checked, not taken on trust.

The interface is published

Export schemas, open document formats and public verification endpoints — free, versioned, ours to maintain.

Build against it freely

A counterparty or vendor integrates without buying anything or signing anything.

Check it yourself

Verification runs on your machine, offline, with no account — the check does not need our word, or our uptime.

Keep your exit

Records export in the same open formats they verify in, so leaving is a working path rather than a negotiation.

Verification is never faked

A record can carry an independent, dated witness we do not control, and every historical anchor stays verifiable by the authority that issued it.

The language model never decides

A language model may draft, extract or route a question. It never produces a figure on your record, and any failure falls back to deterministic code.

Forecast uncertainty is earned, not asserted

Uncertainty is earned against the record’s own history. When the history is too thin, the system declines to forecast rather than produce confident-looking nonsense.

Privacy floors live in code, not in a policy

Aggregate figures appear only when enough independent records sit behind them — enforced in code, not promised in a document.

Composable without a shared build

Products compose at runtime over documented interfaces. Each stays independently deployable, and separately licensable.

Audit trails an administrator cannot edit

The append-only record rejects an update or delete against its history — including one issued by an administrator, including one issued by us.

Less chain than the alternatives, on purpose

Permanence is the one genuinely useful thing a public chain sells, and it is obtained here without one: records carry a dated, third-party witness we do not control. Where a platform issues tokens, the private register stays the authority.

How it is built — the delivery stack
  • One typed language end to end — web, mobile and server — with shared contracts rather than parallel definitions
  • Server-rendered web and cross-platform mobile from a single codebase per product
  • A relational system of record, schema-first with every change in version control
  • Managed serverless functions for background and integration work
  • Scheduled jobs for periodic verification, anchoring and index recomputation
  • API-first: a versioned REST read API and embeddable widgets on every product
  • Automated unit and integration suites across the estate, with browser end-to-end coverage on the larger products

This names what each platform is built on, not how it is built. The how is shown in a technical deep-dive, under a mutual NDA.

What the stages mean

Pilot-ready
Built end to end and exercised against real external checks. Ready for a first pilot on your own data.
Working build
The full product runs end to end today on a seeded demonstration dataset. Production connectors and live tenancies are next.
Early build
A working prototype covering the core loop.

Sectors we build for

  • Smart logistics & supply chain
  • Agritech & food technology
  • Advanced manufacturing
  • Environmental technology
  • Property & built environment
  • Finance & investment
  • Government & public sector
  • Health & life sciences
  • Retail, hospitality & consumer
  • Research commercialisation
  • AI & digital

Seen something worth a meeting?

Propose a pilot
Platforms · Creation1618