> 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/welcome.md). # Welcome ## Welcome to Strong Compute ### Welcome to Strong Compute Strong Compute cuts your AI infrastructure bill — immediately and verifiably. We target an 80% reduction in AI infrastructure costs, and we've seen drops of up to 30x. We do it on the cloud spend you already have, while future-proofing how you spend on tokens. Hyperscaler FinOps is mature. AWS, Azure, and GCP are covered. AI spend isn't — it's spread across neoclouds and token providers that traditional tooling was never built for. Strong Compute closes that gap. We manage the 18 neoclouds AI teams actually use — CoreWeave, Lambda, Crusoe, and more — and integrate token spend controls for Anthropic, OpenAI, and other model providers. In short: we stop the runaway cloud bill so you can focus on product. ### Why this matters AI workloads are moving fast to AI-native providers. Every new vendor adds another invoice, another dashboard, and another blind spot. That's how bills run away — spend grows across vendors built for AI, not for cost reporting. Strong Compute exists to own that problem. ### Get started Connect supported vendors in [BYO Cloud API Keys](/byo-cloud-api-keys.md). Review balances, charges, and limits in [Billing](/basic-concepts/billing.md). ### What Strong Compute gives you * **Immediate, verifiable savings:** Cut costs on your existing cloud spend — targeting 80% reductions, with drops of up to 30x observed. * **Neocloud coverage:** Manage costs across the 18 neoclouds AI teams use, from one place. * **Token spend control:** Set and enforce limits on Anthropic, OpenAI, and other model provider usage. * **Budget control:** Set spending limits for organisations, projects, and members. * **Credit-aware workflows:** Bring your own vendor API keys and spend your own cloud credits. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.strongcompute.com/welcome.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.