What you're responsible for

A workshop may ask you to use services that charge for usage. Common ones include:

• LLM API usage — tokens you send to providers like Anthropic, OpenAI, or others are billed to your account.
• Cloud infrastructure — anything you deploy to AWS, GCP, Azure, Cloudflare, Vercel, etc. is billed to that account, including resources you forget to tear down.
• Third-party SaaS — auth providers, databases, observability platforms, and similar tools have their own free tiers and paid plans.

We don't see your usage of those services and can't control what they charge. Anything you set up runs against your accounts.

Check pricing before you run

Each vendor's own pricing page is the source of truth. A few common ones:

• anthropic.com/pricing — per-token rates by model.
• openai.com/api/pricing — OpenAI API pricing.
• aws.amazon.com/pricing — AWS service pricing.

Rates change. Don't trust a number you read in a tutorial — including this one — over the vendor's current page.

Protect yourself

• Set a billing alert. Every major vendor lets you cap monthly spend or get notified at a threshold. Configure one before you start.
• Tear down what you deploy. If a workshop has you stand up cloud resources, follow its teardown step. An idle resource you forgot about can quietly accumulate charges for months.
• Rotate keys you no longer need. If a workshop is over and you don't plan to keep building on it, revoke the API keys it used so a leaked key can't be billed against your account later.