What happens when we're down.
With required local artifacts available, policy evaluation, receipt signing, and offline verification continue on customer infrastructure. Hosted administration and managed evidence services remain separate dependencies. The table names what continues, what degrades, and what becomes unavailable.
Policy evaluation
Continues locallyThe gate evaluates a signed policy bundle already on the device. No call leaves the host to decide allow or deny.
Receipt signing & chaining
Continues locallySigning uses the workspace key held locally. The chain can extend while Aarmos-hosted services are offline.
Receipt verification
Continues locallySupported artifacts can be checked offline against a supplied trust root without calling an Aarmos service.
Kill switch
Continues locallySupported local stop controls act on customer infrastructure rather than through a hosted administration service.
Recovery Point capture & restore
Continues locallyCapture and restore operate on local governance state. Verification can run offline with the required artifacts and supplied trust material.
Change evaluation and activation
Continues locallyHistorical and counterfactual evaluation uses recorded evidence. Human review and controlled activation remain separate from analysis.
Evidence delivery to your SIEM
DegradedManaged evidence routing is not currently enabled; if enabled in future, it would pause during an outage. Local NDJSON export and replication targets keep working the whole time.
Team & Enterprise console
UnavailableMembership, entitlements, SSO/SCIM administration, and the hosted dashboards depend on our control plane.
Entitlement checks for paid features
DegradedCached entitlements continue for the current period; package and membership changes wait for hosted administration.
You own the backup.
A Recovery Point names the policy, authority, identity, receipt head, and configuration a workspace can resume from — and contains none of them. Export the history as newline-delimited JSON, or configure supported direct replication from the device to a customer-controlled destination. In that direct-replication configuration, the data path does not use Aarmos-hosted routing; recovery still depends on the artifacts and trust material the customer retains.
Restore is all-or-nothing and returns a state, never a score: either recoverability is Complete, or every unverified component is named.
Honest limits.
- Local-first covers policy evaluation, receipt signing, and key custody. Account administration is hosted and stops when we do. Managed evidence routing is a hosted capability that is not currently enabled; if enabled in future, it would also depend on our services.
- A Recovery Point proves a state was observed and signed. It does not store the artifacts, so recovery still requires the bundle, keys, and receipts you kept.
- We publish no uptime guarantee here. Availability commitments belong in a contract, not on a marketing page.