Authority rule
Telemetry cannot become execution.
SDK interfaces carry OBSERVE authority only. Gateway handles CONFIRM and ENFORCE only after authenticated server-side authorization.
Developer documentation
Instrument first. Authorize deliberately.
Production interfaces for signed agent telemetry, normalized event evidence, local runtime instrumentation, and fail-closed CONFIRM/ENFORCE handling.
Self-directed evaluation
Quickstart: prove GuardState before you trust it
Evaluate GuardState without a sales call, broker credential, production account, or proprietary strategy disclosure. Start in the browser, test your own sanitized scenario, then move to a private Hybrid-Edge evaluation only when it adds value.
Read documentationHybrid-Edge system design
Architecture and authority boundaries
GuardState separates intelligence, authority, execution, and evidence so institutions can keep sensitive control-plane functions inside environments they govern while retaining a consistent operating and diligence experience.
Read documentationFinancial evidence model
Universal Event Ledger
Correlate financial-agent decisions, control outcomes, provider lifecycle events, reconciliation, incidents, and economics without confusing proposals, orders, acknowledgements, fills, and account effects.
Read documentationAgent instrumentation
GuardState SDK
Instrument agentic investment systems with signed observation and correlation data while keeping financial authorization in independent GuardState control boundaries.
Read documentationExecution-side enforcement
GuardState Gateway
A narrow, independently governed boundary between approved financial actions and provider execution. Gateway verifies authority; it does not trust client-side intent.
Read documentationInstitution-controlled runtime
GuardState Edge and Edge Fleet
Place GuardState's secure runtime close to sensitive agent, policy, data, and provider systems while maintaining verifiable node identity, capability, policy, health, and evidence.
Read documentationPrivate architecture discovery
GuardState Stack Scanner
Assess an agentic investment stack without requiring source-code, credential, account, balance, position, or proprietary strategy upload as the starting point.
Read documentationVersioned protocol contracts
Financial-authority specifications
Inspect the contracts that make GuardState's financial-authority model independently reviewable across identity, Mandate, Acceptance, Permit, evidence, telemetry, conflicts, and provider boundaries.
Read documentationDeterministic verification
Conformance and provider simulation
Evaluate adapter behavior, provider lifecycle semantics, Permit binding, reconciliation, and failure handling before relying on a real financial-provider connection.
Read documentationDiligence-ready evidence
Security and assurance
Review GuardState's technical security evidence, control boundaries, release provenance, and current third-party assurance status without conflating internal testing with independent certification.
Read documentationInstitutional review
Technical control mappings
Connect GuardState technical evidence to common governance and supervisory review topics without turning an engineering mapping into a legal conclusion or regulatory endorsement.
Read documentationEvidence rule
Reported capability is not verified capability.
Identity, signature, freshness, correlation, policy, authorization, provider, and commissioning evidence determine the product state.