What is Cushy

Cushy is a cross-cloud management console — a single pane of glass for teams running infrastructure on AWS, Google Cloud, Azure and Alibaba Cloud. It connects to your cloud accounts with read-only access, discovers what you run, and presents inventory, network topology, cost, audit and team management in one calm interface designed for the people who stare at it during an incident at 3 a.m.

Who it is for

Cushy is built for SRE, platform and cloud infrastructure teams who operate more than one cloud and are tired of switching consoles, re-authenticating, and mentally translating between four different names for the same concept. It is equally useful to a FinOps practitioner who wants normalized spend across clouds, and to a security or platform owner who needs one place to manage who can see and change what.

What it does today

• Cross-cloud inventory — a live, searchable list of your resources across every connected account, kept fresh by a background sync engine. Real for all four clouds — AWS, GCP, Azure and Alibaba.
• Network topology — a map of your VPCs/VNets, subnets and the links between them, with a colour-and-glyph status scale that is safe for colour-blind operators.
• Cost & FinOps — billing data normalized to the FOCUS standard, broken down by cloud, service and tag, with budgets and statistical anomaly detection.
• Identity & access — organizations, a fixed role model from Viewer to Owner, multi-factor authentication, single sign-on with your own OIDC identity provider, and API tokens for automation.
• Audit — an org-scoped trail of who did what, when and from where.

What is on the roadmap

Most major surfaces are shipped: all four connection adapters — AWS, GCP, Azure and Alibaba — are real, as are the Terraform execution engine, pipelines and deploy agents, Git connections, SAML and SCIM, cross-cloud connectivity, monitoring and the AI assistant. Account vending and the marketplace are on the roadmap. See Feature status & roadmap for the honest status of each.

How the pieces fit

Everything is scoped to an organization (a tenant). You connect cloud accounts to your organization; a sync engine keeps their inventory fresh; roles decide who can view versus change things; and a brand-new organization starts with an empty console until its first cloud connection turns healthy, at which point the console fills with your real data. The next page, Core concepts, defines each of these terms.