costs
The workshops that use cloud or third-party services bill your own accounts, not ours. This page covers what to expect and how to keep your spending under control.
what you're responsible for
Some workshops have you use outside services. Those run on your accounts:
Anything you deploy to AWS, GCP, Azure, Cloudflare, Vercel, and similar providers is billed to that account, including resources you forget to tear down. For example, the MCP workshop's final lessons deploy to an AWS account. That work stays within the free tier, but the account is yours.
Auth providers, databases, observability platforms, and similar tools a specific workshop may use have their own free tiers and paid plans.
We don't see your usage of those services and can't control what they charge. Check each vendor's pricing page before you run — it's the source of truth.
Cloud and SaaS pricing moves. Don't trust a number you read in a tutorial — including this one — over the vendor's current page.
protect yourself
Every major vendor lets you cap monthly spend or get notified at a threshold. Configure one before you start.
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.
If a workshop is over and you don't plan to keep building on it, revoke the cloud and third-party credentials it used so a leaked one can't be billed against your account later.