Resoto enables a broad set of exploration and automation scenarios. Its foundation is a graph-based data model, which exposes resource metadata and dependency relationships between your service's assets.
Resoto's documentation is organized as follows:
Getting Started walks you through the installation process. Start here if you're new to Resoto.
How-To Guides provide step-by-step instructions for performing specific tasks.
Concepts provide an overview of how Resoto works.
Reference is a manual covering the details of Resoto. It is assumed that you already have a basic understanding of important concepts.
Development lists instructions and guidelines for Resoto development and contributions.
Why Cloud Asset Inventory?
Cloud-native infrastructure today is fragmented because:
Resource Proliferation in the Cloud
With containers and serverless functions, services have become more abstract, and the size of the individual deliverable has become smaller but many times more numerous.
Bulkhead Partitioning of Resources
Cloud providers have made partitioning resources into separate accounts, projects, and namespaces easy. This allows for better isolation and security, but also makes it harder to get a consistent view of the state of the world.
Engineers using Infrastructure-as-code (IaC) in CI/CD pipelines make it easy to spin up new resources.
Multiple Service Providers
Many organizations use multiple services and cloud providers to take advantage of the unique features of each provider.
Resoto helps you overcome these challenges by providing a single source of truth for your cloud assets.