Documentation

Everything you need to connect a cloud account and read the security, performance, and cost reports it produces.

Getting started

Create your organisation, connect a cloud account, and run your first scan.

How access is granted

Three ways to connect a cloud account, depending on how much standing access you want to grant.

AWS

EC2, EBS, S3, RDS, VPC, and Security Groups, with Cost Explorer and CloudWatch metrics.

Azure

VMs, Managed Disks, VNets/NSGs, Storage Accounts, and SQL Servers, with Cost Management and Monitor metrics.

GCP

Compute Engine, Persistent Disks, VPC networks, Firewall rules, Storage buckets, and Cloud SQL.

Kubernetes

Any cluster, anywhere — EKS, AKS, GKE, on-premises, or k3s.

Security reporting

Every rule violation, with severity, remediation, and which framework control it maps to.

Performance & reliability reporting

Single points of failure and under-provisioned resources, surfaced before they cause an incident.

Cost reporting

Every recommendation shows the pricing assumption behind its dollar estimate — nothing is a black-box number.

Roles & permissions

Seven fixed roles, so access maps to how security, platform, and finance teams actually divide responsibility.

API keys

Machine-to-machine authentication for the in-account collector, separate from user login.