Outbound-first architecture
The Client initiates communication with the platform. Normal monitoring does not require an inbound cloud connection.
Security architecture
A constrained operational architecture built around outbound communication, strong identity, organization-scoped authorization, and controlled diagnostics.
The Client initiates communication with the platform. Normal monitoring does not require an inbound cloud connection.
Client and browser communication uses HTTPS/TLS.
Google and Microsoft OAuth are supported with TOTP MFA and stronger authentication for privileged administration.
Account membership and resource ownership are enforced server-side for inspected operational endpoints.
Diagnostic logs are requested through defined workflows, redacted before upload, bounded in size, and expired after their visibility window.
No AI diagnosis or remediation shell exists today. Future automation is designed around policy-approved actions rather than unrestricted shell access.