Skip to content

RESOURCES

Updating, monitoring, and running the platform on a site that never phones home.

Articles in Operations

  • Operations

    The record an auditor can read

    Substrate keeps three local records: Evaluation traces for every operation, Watchman's integrity history, and the provenance record for every node. Together they answer what ran, on what, and when.

    · 4 min read

  • Operations

    Capacity planning for a serving pool

    Sizing a Substrate pool starts with the callers and their latency budgets, not with hardware. Count the callers, know their budgets, and let the pool tell you when it is near its edge.

    · 4 min read

  • Operations

    Customer-initiated support on the platform

    Support for Substrate runs through the customer portal, and every remote session starts with the customer. On sovereign sites, a session needs the customer's attestation and ends on a hard expiry.

    · 4 min read

  • Operations

    How signed updates reach the appliance

    Updates to Substrate are signed bundles. The customer downloads them from the portal or carries them in on media; the appliance verifies the signature, loads the release, and keeps the previous one.

    · 4 min read

  • Operations

    Monitoring a platform that never phones home

    Substrate exposes its health, traces, and integrity record on the facility network and sends nothing anywhere else. Here is how a site watches it with the tooling it already has.

    · 4 min read