PhyWare
Talk to us

Optional layers

Applications and deployment layers

Safety and compliance used to define PhyWare. They are now applications on top of the platform — valuable, but never a requirement for adopting it.

Talk to us Read the docs
Applications

Built on the same contracts you get

First-party applications exist to deliver value quickly and to prove the platform interfaces are sufficient for sophisticated products. They are not allowed to become a private back door into the data.

PhySafe

Safety rules, alerting and supported enforcement workflows evaluated against live PhyCloud events and latest-state projections.

PhyComp

Compliance evaluation, evidence mapping and reporting built on retained events, with lineage from every finding back to its source records.

Phylyze

Advanced analysis, anomaly detection and optimisation over the PhyUDM lakehouse — first-party or partner-built.

Architectural rule: any first-party application must consume the same documented, authorised interfaces available to customers and partners wherever practical. This keeps dashboard requirements from distorting the event platform.

Deployment

Where the platform runs

Cloud is the default. These layers exist for the operations where it is not sufficient.

PhyEdge

Local ingestion, buffering, subscriptions and state projection for low-latency and degraded-network operation. Sites keep working when the link does not.

PhyTAU

Hardware-isolated, tamper-evident capture for systems where the integrity of the record must be defensible independently of the host.

Start with the platform, add what you need

Most operators begin with one incident workflow and two or three source classes, then expand coverage, retention and applications as the event layer proves itself.

Talk to us Explore the docs