Select any value and trace it back to the system, record and processing step that produced it.
02See exactly what the picture looked like yesterday, last week, or at the moment something went wrong.
03Close a berth or delay a vessel in a safe copy of the model and see the knock-on effects before you act.
04Explore a 3D model of your site with the live data in place — built from your own drone and laser scans.
Tessara reaches data no SaaS platform can touch. A single static connector agent sits beside your source systems — deep inside networks that allow no inbound access — and holds one encrypted, outbound-only connection to the control plane. Every sync job is cryptographically signed; source credentials never leave the agent host.
ERP databases, file shares, REST APIs, message queues and OT historians. Connector agents extract on-site and stream versioned, resumable segments back over the same channel.
The governed centre of your estate — datasets, pipelines and schedules declared as code; every sync order signed, every state change recorded, drift reported the moment it appears.
Connector agents pull from JDBC databases, files, APIs, queues and historians — landing data as versioned, immutable datasets with manifests, checksums and resumable upload.
Pipelines as code — SQL first, Python second — with full lineage: every dataset version records exactly which inputs and which transform version produced it.
The ontology maps datasets onto object types, properties and links — Person, Vessel, Site, Transaction, Sensor — with object- and property-level policy and classification markings.
Object explorer, graph view, map and time-series — search, filter and pivot across links, save investigations, and build dashboards over ontology queries.
Actions defined on object types — flag, assign, annotate, or kick off writeback through an agent — with mandatory audit and approval workflows on every change.
Purpose-based access requests, classification markings and row-level tenancy from day one — every grant scoped, time-bound and recorded.
Raw tables answer queries; an ontology answers questions. Tessara maps your fused datasets onto the real things your operation runs on — and every property traces back through lineage to the source row, the pipeline version and the sync job that delivered it. When an operator acts, the decision carries its evidence with it.
Ask a question in plain English and get an answer drawn only from your own data, with links to where every fact came from. It sees only what you are cleared to see, and it runs inside your network.
Beyond questions, it can find datasets, navigate an imported 3D site and draft what-if revisions in plain language. Checked tools validate each draft, and simulated results are always labelled as such.
The governed ontology is the model of your operation — and Tessara lets you see it. Follow one scenario — Harbour Watch — end to end: MV Kestrel inbound to Felixstowe with a flagged consignee. Watch her track land on the live picture, see the terminal as a spatial twin, and test what happens across berths, consignments and customs if you hold her at anchor — every view still bound by clearance, every marker still carrying its provenance.
Start with open mapping, terrain and building data, then add the detail only you hold: private LiDAR surveys, drone or phone photogrammetry, CAD drawings and BIM models. Bring those inputs into a common site frame, connect the places and assets to governed operational records, and build a 3D world twin you can explore, question and use for scenario modelling.
Tessara is built for organisations whose data is too sensitive, too regulated or too operational for the SaaS default. The same platform, tuned to the mission.
Fuse departmental systems into one governed model inside your own estate — classification markings, purpose-based access and auditor-defensible provenance on every value.
Connector agents sit beside historians and SCADA networks that allow no inbound access, streaming versioned data out over one outbound channel — the enclave never opens a door.
Air-gapped deployments with Airlock-only imports. Link vessels, cargo, sites and people across feeds; rank what matters; act with mandatory approval workflows.
Investigate transactions, counterparties and accounts on one ontology with full lineage — evidence that stands up to your regulator, produced inside your perimeter.
Pre-stamped installers enrol on first run — keypair generated on-site, token cleared, identity signed. No manual certificate ceremony.
Every sync job and writeback is Ed25519-signed and addressed to one agent. A compromised control plane still cannot redirect your data to an unpinned destination.
In air-gapped installs, one architecturally one-way bridge imports signed bundles — reference data, model artefacts, platform updates. Nothing flows out. Ever.
Why your data platform must live inside your perimeter — and what to demand of any vendor who claims it can.
The trust architecture for air-gapped data fusion: outbound-only agents, signed work orders and the import-only Airlock.
The case for an operational ontology — objects, links and provenance that let operators act on the world, not query it.
Grounding assistants on data people are cleared to see — an operating model for AI under regulation.
Sovereign data fusion, a governed ontology and Tessara Assistant — single host, one port, entirely under your control.