Connect your providers to Helias
Helias is Virtasant's FinOps platform. It reads the cost and usage data your providers already produce, and turns it into spend visibility, efficiency scoring and savings recommendations.
Each provider has one page, covering the permissions, the commands, how to check it worked, and what a disconnect does.
Supported providers
| Provider | What Helias reads | How we authenticate | Setup |
|---|---|---|---|
 AWS | Cost and Usage Report, plus cost, billing and optimization APIs | An IAM role you create, trusted with your unique External ID | About 5 minutes |
 Google Cloud | Detailed Cloud Billing export in BigQuery, plus project metadata | A service account provisioned for you alone, with no key | About 10 minutes |
 Azure | Cost and usage for the scope you choose, plus resource metrics | A service principal in your tenant, with no secret | About 10 minutes |
 Anthropic | Claude usage and cost across your organization | An Analytics API key you create | About 2 minutes |
 Cursor | Your Cursor team's spend and usage | A Team Admin API key you create | About 2 minutes |
AWS
Anthropic
CursorClouds and AI providers connect differently
They differ in what you hand over.
Clouds give Helias an identity, never a credential. For AWS, Azure and Google Cloud you authorise something that belongs to you and that you can revoke from your own console: an IAM role that trusts only us and only with your unique External ID, a service principal created in your own tenant with no secret attached, or IAM bindings on a service account provisioned for you alone. There is no key to leak and none to rotate. You also choose a scope: your whole organization, or one account, subscription or project.
AI providers have no keyless option, so they take an API key. The key passes through the onboarding app only in memory, is never written to our database and never appears in a log or an error message, and comes to rest only in the environment dedicated to your organization. There is no scope to choose: a Cursor team or a Claude organization is the whole connection.
Whichever you connect, your access is held in an environment dedicated to your organization, which is a separate AWS account per customer. Helias never shares a collector, a service account or a service principal across customers.
Where to start
- New to Helias? Get access first. Access is granted by request and approved by a person, so start there.
- Reviewing this for security or procurement? Permissions lists every grant we ask for, and Security covers what we store, how we authenticate, and how to revoke.
- Ready to connect? Pick your provider from the table above.