# Usage guidelines Source: https://docs.quake.ai/docs/usage-guidelines Markdown: https://docs.quake.ai/docs/usage-guidelines.md --- # Usage guidelines This page sets the terms under which Quake AI publishes sample code, command line transcripts, infrastructure-as-code templates, proofs of concept, configuration snippets, and other technical content across this documentation site. The same terms apply whether Quake AI hosts the content on this site, references it from a how-to guide, embeds it in a tutorial, or hands it to you through a support channel. Procedural and strategic pages render a short Usage Guidelines block at the bottom of the article that summarizes these terms and links back to this page. ## What counts as Quake AI Content Quake AI Content includes: - Sample code in any language, including snippets shown inline and complete files linked from the page. - Command line examples and shell transcripts. - Infrastructure-as-code templates, including OpenTofu modules, Terraform configurations, Heat templates, and Ansible playbooks. - Configuration files, manifests, and policy documents. - Proofs of concept and reference architectures. - Any other technology Quake AI personnel hand you through a documentation page, support ticket, or community channel. ## Production use Quake AI publishes Quake AI Content to help you learn the platform, test an integration, build a prototype, or evaluate a service before you commit to production. Do not run Quake AI Content against production accounts, production data, or any other data you are not prepared to lose, replace, or expose. You are responsible for testing, securing, and adapting Quake AI Content before you put it into a production-grade workload. Specifically, you decide: - Whether the content meets your security review standards. - Whether it handles the inputs, scale, and failure modes your workload encounters. - Whether it complies with your operational, regulatory, and contractual obligations. - Whether it is suitable for the specific data classification you operate on. Quake AI provides Quake AI Content under the [Quake AI Customer Agreement](https://www.rumble.cloud/terms) or the relevant written agreement between you and Quake AI, whichever applies. Your use of Quake AI Content is also subject to the [Acceptable Use Policy](https://www.rumble.cloud/acceptable-use). ## Charges and resources Quake AI uses fixed-plan pricing. Your monthly invoice covers the plan tier you subscribe to and the add-ons attached to it. Within a plan, most resources Quake AI Content provisions do not change the bill: private networks, subnets, routers, security groups, Block Storage volumes within the tier quota, inbound and outbound data transfer, and API calls all come with the plan. The canonical [Quake AI pricing page](https://www.quake.ai/pricing/) lists the current plans and add-on rates. Quake AI Content can still increase the bill when it provisions add-ons or capacity beyond your plan tier: - **Public IPs** beyond the one that dedicated-vCPU plans include. - **Object Storage** beyond the 1 TB that dedicated-vCPU plans include, in per-TB add-on blocks. - **Block storage** beyond the plan tier quota. The custom-package calculator prices the additional capacity. - **Compute capacity** beyond the plan tier (additional vCPUs or RAM). The custom-package calculator prices the additional capacity. Quake AI Content can also exhaust your project's plan capacity even when it does not change the bill. A second VM on the Developer plan, for example, exceeds the plan's capacity and fails to provision until you release the first. Before you run any Quake AI Content that creates resources: 1. Read through the resource list the content provisions. 2. Confirm the resources fit your plan capacity and identify any add-ons the content adds to the invoice. 3. Plan how you will release the resources when you finish the exercise. For OpenTofu and Terraform templates, `tofu destroy` or `terraform destroy` releases the resources the template manages. For Heat templates, deleting the stack releases the stack-managed resources. For Console-driven walkthroughs, each step that creates a resource has a counterpart later in the page or in the [Operate](/docs/operate) section that shows how to release it. ## Third-party comparisons Migration content, evaluation content, and provider comparison content on this site reference services and features published by other cloud providers, including but not limited to AWS, Google Cloud, Microsoft Azure, DigitalOcean, and Hetzner. Those references reflect what those providers documented publicly as of the validation date on the page. Cloud providers change pricing, quotas, service limits, regional availability, and product capabilities frequently. A statement about a third-party provider that was current on the validation date may be out of date by the time you read it. Verify provider-specific claims against the provider's own current documentation before you base a procurement, architecture, or migration decision on what you read here. ## Reporting issues If you find Quake AI Content that produces incorrect results, fails to apply, charges resources the page did not list, or otherwise diverges from what the page describes, file feedback through the page-bottom feedback widget or open a support ticket through the Quake AI portal.