Built with governance at the foundation
Organisation design touches sensitive structural, staffing, and cost data. Orgonaut is built with tenant isolation, auditability, encrypted transport, and access control as foundational concerns — not features added after the fact.
Tenant isolation
Row-level multi-tenancy enforced through request resolution, model scopes, and guarded bindings. Tenant-scoped routing ensures your organisational data is isolated from other accounts. Context-bleed guards protect against data leakage.
Identity and access
Sign in through Google, Microsoft, or GitHub OAuth. SAML support for organisation-policy-oriented access control. Tenant membership and invitation management with scoped permissions.
Audit trail
Scenario changes and operational mutations are traceable through append-only audit events. Full event logging pipeline with scenario history, lineage, and snapshots. Activity statements provide visibility into what changed, when, and by whom.
AI governance
Astro and MCP operate within the same permission and scenario boundaries as the product. Astro can read broadly but write actions require explicit confirmation. Baseline writes are blocked — AI cannot modify your Live operating state.
Integration security
Tenant-scoped webhook endpoints with authentication and validation. HTTPS/TLS is used for data in transit, with secret handling and redaction for queued integration processing. OAuth-backed MCP routes follow explicit scope rules.
Data access controls
Tenant-scoped routing and data access controls. Scenario-aware protections ensure changes in one scenario cannot affect another. Import, integration, admin, and security writes remain human-owned.
What we can tell you clearly
Tenant isolation is enforced through request resolution, model scopes, and guarded bindings. Your data is scoped to your account and cannot be accessed by other tenants.
Scenario changes and operational mutations are traceable through append-only audit events. You can review what changed, when it changed, and who made the change.
Traffic to and from Orgonaut is served over HTTPS with TLS/SSL certificates, so data in transit is encrypted.
Astro and MCP operate within the same permission and scenario boundaries as the rest of the product. AI cannot modify your Live operating state — write actions are confined to mutable scenarios and require explicit confirmation.
Orgonaut supports Google, Microsoft, and GitHub sign-in through OAuth, as well as SAML for organisation-policy-oriented access control.
We host Orgonaut on Railway, so the service also benefits from platform-level controls Railway documents publicly, including SSL certificates, traffic encryption, and edge DDoS protection. You can review Railway's public details on its pricing and enterprise pages.
A note on certifications
We do not currently claim SOC 2, ISO 27001, or other formal security certifications. We believe in being honest about where we are. If you have specific compliance requirements, contact us to discuss your needs.
Security contact
For security-related questions or to report a concern, email hello@orgonaut.co.
Questions about our security posture?
Get in touch and we will provide the detail you need for your evaluation.