The core platform

PhyCloud Your system of record for physical operations

Ingest, stream, index, correlate, govern, verify and retrieve PhyUDM events across a hot operational store and a long-term lakehouse — through one API and one catalog.

Capabilities

What the platform guarantees

The promise is not that PhyCloud performs every analysis. It is that events are preserved and served reliably enough that you can run whatever authorised analysis you need — with our tools, a partner's, or your own.

Ingestion

Single-event, batch and streaming ingestion of valid PhyUDM events, with schema validation, version negotiation and idempotent, append-only writes.

Live operations

Subscriptions with resumable cursors, latest-known-state projections per source, and freshness, heartbeat and telemetry-gap detection.

Correlation

Time, source, type, mission, incident and geospatial indexing, so events from systems that share nothing else land on one timeline.

Retrieval and replay

Historical time-window retrieval, synchronised multi-source replay, and a coverage API that reports which ranges exist and which are missing.

Provenance

Source, capture time, ingestion time, integrity metadata and chain-of-custody on every event — independently verifiable, including after compaction.

Governance

Fine-grained scopes, purpose-aware access policies, retention classes, legal hold, evidence sealing, and an audit trail over every search and export.
Storage model

Two tiers, one platform

A data lake is economical storage for large volumes, but it will not answer a command-centre query in milliseconds. PhyCloud combines an operational store with a governed lakehouse instead of forcing one model onto every workload.

Bronze Source

Original vendor payloads and files, retained only where ownership, contract, purpose and policy permit it.

Silver PhyUDM

Validated, normalised, provenance-tagged events. The canonical cross-vendor operational history and the centre of the platform.

Gold Data products

Incident timelines, mission summaries, coverage reports, KPIs and compliance datasets — each with lineage back to its Silver events.

Silver is the strategic layer. Bronze preserves source fidelity but cannot be assumed available for restricted vendors, and Gold datasets must never become unexplained facts disconnected from their inputs.

Deployment

Managed, owned, or both

Open formats are what make the ownership claim real. Canonical history is written as Parquet with signed manifests — an open table format follows only when scale justifies the operational complexity.

PhyWare-managed

We operate hot storage, the lakehouse, catalog, retention and query infrastructure.

Simplest adoption and strongest managed operations.

Customer-owned lake

PhyCloud writes canonical files and manifests straight into object storage you control.

Strongest ownership; integrates with analytics you already run.

Hybrid

We operate the hot tier and continuously deliver canonical PhyUDM history to your storage.

Recommended for enterprise: operational simplicity plus a portable copy.

Bring your hardest integration

If you can describe the incident timeline you cannot assemble today, we can tell you honestly whether PhyCloud would shorten it.