CLOUD
Four clouds, one control plane.
AWS, Azure, GCP and Oracle at full parity: the same inventory, the same tracked jobs, the same permission system. Not one first-class provider and three integrations that stop at listing instances.
THE MANUAL WAY
What multi-cloud costs you in practice.
THE FOURTH CONSOLE
Four provider consoles, four permission models, four billing pages. Answering "what are we running and what does it cost" means four tabs and a spreadsheet.
THE ORPHANED RESOURCE
A load balancer from a cancelled project has been billing for fourteen months. Nothing tracks resources back to the person or the reason that created them.
THE DRIFTED STACK
Someone fixed something in the console instead of in Terraform. The next apply will quietly undo it, and nobody will connect the two events.
WHAT TALOS DOES
The same operations, whichever provider.
Account inventory
Attach an account and Talos sweeps it: compute, storage, networking, databases, DNS. Resources created outside Talos still appear.
Compute operations
Start, stop, resize and inspect instances across all four providers with one set of verbs and one audit trail.
Object storage
Browse, upload and manage buckets and containers, with per-operation permissions rather than a shared access key.
Infrastructure stacks with drift
Terraform stacks run as jobs, with drift detected against the real provider state rather than assumed absent.
Cost visibility
Spend pulled per provider into one view, so the answer to "what is this costing" does not require four logins.
Bridges into the rest of Talos
Managed clusters appear in Kubernetes management, container registries appear in Docker management, managed databases become backup targets.
HOW IT RUNS
Every action is a tracked job.
WHAT MAKES THIS DIFFERENT
Full parity across all four providers.
Most tools support one cloud properly and reduce the others to a resource list. Talos implements the same eleven areas for each of the four (accounts, inventory, compute, storage, stacks, managed databases, DNS, monitoring, cost, serverless and registries), because the whole value of a single control plane disappears the moment you have to open the provider console for the second cloud.
RELATED CAPABILITIES
Attach one account, read-only.
The first sweep changes nothing. It reports what is running.