> For the complete documentation index, see [llms.txt](https://docs.strongcompute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongcompute.com/byo-cloud-api-keys.md).
# BYO Cloud API Keys
In order to track cloud compute costs, organisation admins are able to add API keys for a variety of clouds under the API Keys tab. There are 2 types of vendors currently supports:
* Compute Vendors: sync compute costs - useful for Strong Control, Instances, Costs and FinOps
* AI Providers: aggregate token/usage data - currently used for the LLM Spend metrics, and soon to be expanded to FinOps
*Please note that all API keys and secrets are stored encrypted, and cannot be accessed again once saved. To update your API keys, please input the new values on the Edit screen, or delete and recreate the Vendor.*
As of 11-02-2026, Strong Compute supports the following cloud compute vendors:
* Amazon Web Services (AWS)
* Arkane Cloud
* Microsoft Azure
* Brev
* Crusoe
* CUDO Compute
* Google Cloud Platform (GCP)
* E2E Networks
* GPU Salad
* Hyperstack
* Jarvis Labs
* Lambda
* Latitude.sh
* Modal
* Nebius
* Oblivus
* Oracle
* Runpod
* Scaleway
* Together AI
* Vultr
The following cloud vendors are coming soon.
* Hydra Host
* Verda
* OVH
As of 25-08-2026, we also support the following AI Providers:
* Anthropic
* Fireworks AI
* Gemini
* OpenAI
* xAI
We are planning to expand the AI Providers list to also include the following in the near future:
* Kimi
Click on the Setup button for the cloud vendor you want to configure and complete the form to supply API keys for that vendor.
### Vendor Requirements and Setup
Most vendors require API keys to be properly configured in order to be used by Strong Compute. Refer below to the requirements and setup guide for each vendor:
* [Amazon Web Services (AWS)](/byo-cloud-api-keys/api-setup-amazon-web-services-aws.md)
* [Microsoft Azure](/byo-cloud-api-keys/api-setup-microsoft-azure.md)
* [Brev](/byo-cloud-api-keys/api-setup-brev.md)
* [Crusoe](/byo-cloud-api-keys/api-setup-crusoe.md)
* [Cudo Compute](/byo-cloud-api-keys/api-setup-cudo-compute.md)
* [E2E Networks](/byo-cloud-api-keys/api-setup-e2e-networks.md)
* [Google Cloud Platform (GCP)](/byo-cloud-api-keys/api-setup-google-cloud-platform-gcp.md)
* [GPU Salad](/byo-cloud-api-keys/api-setup-gpu-salad.md)
* [Jarvis Labs](/byo-cloud-api-keys/api-setup-jarvis-labs.md)
* [Hyperstack](/byo-cloud-api-keys/api-setup-hyperstack.md)
* [Lambda](/byo-cloud-api-keys/api-setup-lambda.md)
* [Latitude.sh](/byo-cloud-api-keys/api-setup-latitude.sh.md)
* [Modal](/byo-cloud-api-keys/api-setup-modal.md)
* [Nebius](/byo-cloud-api-keys/api-setup-nebius.md)
* [Oblivus](/byo-cloud-api-keys/api-setup-oblivus.md)
* [Oracle](/byo-cloud-api-keys/api-setup-oracle.md)
* [Runpod](/byo-cloud-api-keys/api-setup-runpod.md)
* [Scaleway](/byo-cloud-api-keys/api-setup-scaleway.md)
* [Vultr](/byo-cloud-api-keys/api-setup-vultr.md)
AI Provider setup guides:
* [Anthropic](/byo-cloud-api-keys/api-setup-anthropic.md)
* [OpenAI](/byo-cloud-api-keys/api-setup-openai.md)
* [Together AI](/byo-cloud-api-keys/api-setup-together-ai.md)
* [xAI](/byo-cloud-api-keys/api-setup-xai.md)
See below
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.strongcompute.com/byo-cloud-api-keys.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
