PUBLIC DOCUMENTATION · UPDATED AUGUST 2026
The material below is public so buyers, architects, delivery teams, security reviewers, procurement staff and new customers can understand AIDE before an account is created. Customer secrets, credentials, tenant data and sensitive operating detail remain protected inside the product and customer implementation process.
A detailed view of the Azure SaaS platform, application services, PostgreSQL and Blob persistence, identity/RBAC, tenant isolation, billing/entitlements, Marketplace integration, telemetry model, Blueprint discovery, observability, CI/CD and tested recovery controls.
The complete path from product selection and organisation ownership through MFA, paid entitlements, seat controls, invitations, roles, initial project/programme or Blueprint scope, telemetry setup, the first control review and onboarding acceptance.
How to use Projects, Programmes, Blueprint and the Admin Centre as a control system: observe evidence, assess system impact, preview a response, commit an authorised intervention and verify what happened next.
Connector principles and operating patterns for Jira, Azure DevOps, Dynamics 365, Power BI, Azure Resource Graph and CMDB/asset evidence, including provenance and fresh/ageing/stale/silent telemetry assurance.
Identity, tenant isolation, audit evidence, recovery, deployment controls, data protection and the boundary between AIDE's standard SaaS controls and customer-specific assurance.
Procurement-friendly entry points, indicative subscription model, Australian-hosted cloud posture and information useful to Commonwealth/state buyers and security/procurement reviewers.
Support coverage, priority/response targets, customer-support entry points and links to public documentation for self-service evaluation and onboarding.
Public SaaS terms overview and privacy information for customers, prospects and marketplace reviewers.
Start with Solution Architecture, then Government Buyers or Terms, followed by the Onboarding Process.
Read Solution Architecture and Security & Assurance. The architecture page also describes tenant boundaries, observability, recovery and commercial entitlement enforcement.
Read Customer Onboarding, Operating Guide and Integrations & Telemetry.
Read Solution Architecture, then the Blueprint sections of the Operating Guide and Integrations & Telemetry.
Public documentation intentionally explains the platform design and customer process without publishing secrets or tenant-specific implementation details. The following remain inside authenticated AIDE or the controlled implementation process: connector credentials and tokens, customer tenant identifiers, private architecture evidence, project/programme content, audit records, exports, reports, organisation branding artefacts, customer-specific network/security configuration and sensitive support diagnostics.
The things a customer needs to evaluate, buy and plan AIDE should be easy to share. The things that could expose a customer's environment should not be.
Start with Solution Architecture Then read Customer Onboarding
