Production operations
Understand plans and usage
Match the current plan terms and resource limits to the application instead of relying on old prices, screenshots, or the word free.
8 minute lesson
Plan names, included usage, commercial-use terms, and prices can change. Treat the current pricing and limits pages as the source of truth.
Identify who owns billing, which workloads consume build time, bandwidth, functions, image optimization, logs, and other metered products, and what happens at a limit. Set available spend or usage controls and alerts before traffic grows. A free deployment is not permission to ignore acceptable-use or commercial eligibility rules.
Map each meter to application behavior. A bot can increase bandwidth and function invocations; an image-heavy page can consume transformation usage; noisy branches can multiply build minutes and retained deployments. This makes a spike diagnosable and suggests a safe response such as rate limiting, caching, disabling an optional feature, or blocking an abusive source.
Record the date and source for plan assumptions because limits and included usage change. Use the platform’s current controls where available, but also define an application-level degradation path. A cost alert that arrives without an owner or action is only a notification.
Create a usage budget for Field Notes with an owner, the current plan, three relevant meters, warning thresholds, and an action if usage spikes.
Lesson completed