Platform · Deployment
Your cloud, your install, your keys.
Raidu runs inside your AWS, GCP or Kubernetes install. One dedicated install per organisation. No Raidu-operated SaaS.
Runs inside your AWS, GCP or Kubernetes install.
Last reviewed
Illustrative. No customer data.
The difference
Their way, and ours.
Their wayRaidu
A SaaS subscription where your data passes through the vendor.A dedicated install in your cloud.
Audit records held by the vendor.Tamper-evident records with full audit chain retention.
SSO added after the fact.SAML, OIDC, Google Workspace SSO, MFA and SCIM on install.
How Raidu handles it
How the install works.
- 01
Pick your cloud.
AWS: CloudFormation with ECS Fargate. GCP: Terraform. Any Kubernetes cluster: Helm. One install, one organisation, no shared tenancy.
- 02
Tamper-evident records.
Every record is hash-chained with SHA-256. Records are written to write-once storage.
- 03
SSO and SCIM on day one.
SAML, OIDC and Google Workspace SSO connect to your identity provider. MFA is enforced. SCIM provisions and deprovisions users as your directory changes.
Platform
What the deployment covers.
Common questions
Answered straight.
Is there a Raidu-operated SaaS option?
No. Every install is dedicated to one organisation and runs in that organisation’s cloud.
Which cloud providers are supported?
AWS (CloudFormation, ECS Fargate), GCP (Terraform) and any Kubernetes cluster (Helm).
Where are records kept and how are they protected?
Records are hash-chained and written to write-once storage in your own install.
Does Wheelhouse support air-gapped installs?
Yes. Wheelhouse runs on your premises or fully air-gapped with no telemetry, no CDN and no error reporting leaving the install.
What SSO and provisioning options are available?
SAML, OIDC and Google Workspace SSO for authentication. MFA enforced. SCIM for automated user provisioning and deprovisioning.
What is the latency overhead?
You choose how deep the checking goes for each use case.