Documentation
Connect your stack. Optimize with confidence.
Step-by-step guides for every cloud and tool OptCloud integrates with — how we connect, what permissions we need, what data we collect, and how to verify the integration.
Quickstart
Most teams are live with first recommendations the same day they connect a cloud account.
- 1Connect a cloud account
Start with AWS, Azure, or GCP using a read-only role. Open the provider guide for exact IAM / Service Principal steps.
- 2Confirm least-privilege access
Every connector is designed for read-only metadata and billing data — never application payloads or write access by default.
- 3Explore Cost Explorer & recommendations
Once the first sync completes, open the dashboard to validate spend and review prioritized savings opportunities.
- 4Add data & observability sources
Layer Kubernetes, Snowflake, Databricks, Datadog, or Oracle Cloud for a complete FinOps ledger.
Integrations
Detailed connection guides for every supported provider. Each page covers architecture, permissions, setup steps, and troubleshooting.
AWS
CloudConnect AWS with a cross-account IAM role and External ID via CloudFormation (Console or CLI). OptCloud never needs your root credentials, access keys, or write access.
Azure
CloudConnect Azure by granting admin consent to OptCloud's multi-tenant application and assigning it read-only roles. No app registration or client secret ever needs to leave your tenant.
GCP
CloudConnect Google Cloud via Billing Export to BigQuery by granting IAM roles to OptCloud's published service account. No key file ever needs to leave your project.
Oracle Cloud
CloudConnect Oracle Cloud Infrastructure (OCI) with a cross-tenancy IAM policy. You admit OptCloud's published group by tenancy OCID — no API signing key or private key ever leaves your tenancy.
Kubernetes
On requestAllocate shared cluster cost to namespaces, workloads, and labels across EKS, AKS, GKE, and self-managed clusters — then rightsizing pods and node pools together.
Snowflake
On requestIngest Snowflake warehouse and cloud-services cost from ACCOUNT_USAGE / ORGANIZATION_USAGE so data platform spend sits next to your cloud bill.
Databricks
On requestPull Databricks billable usage so DBUs, jobs, and SQL warehouses are visible in the same FinOps workflows as your clouds.
Datadog
On requestIngest Datadog usage and cost so observability spend is governed with the same budgets, anomaly detection, and FinOps Agent workflows.
Need help connecting?
Our team can walk through IAM policies, CUR/BigQuery exports, or multi-account setups with you.
Talk to us