ShippedUsage credits
See how your application uses its resources and what that usage costs. Pay for Shipped services through a shared customer credit balance.
Understand where your credits go
Shipped credits pay for the hosting services your application uses, including selected compute, data, storage, delivery, builds, and email. Review usage by resource rather than judging cost only by visitor counts. Two applications with the same audience can have very different costs because their requests, data, background work, and reserved capacity differ.
Review rates and capacity commitments
A resource can have measured usage charges, provisioned capacity charges, or both according to its rate. Review the credits and currency equivalent before selecting a resource or changing its size. Include staging, retained recovery data, and temporary migration overlap in your estimate, because those resources can continue to incur charges beyond the live web process.
Choose how additional spending is approved
Use your plan’s included monthly credits and make additional purchases when needed. Optional automatic top-ups require explicit limits, so increasing a resource or balance does not authorize unlimited charges. Review included-credit reset rules and purchased-credit terms, and set a budget that accounts for the services your application needs to keep running.
A little more detail
Questions about Usage credits?
Does one credit always equal the same amount of every resource?
No. Different resources have their own rates and units. Review the published rate and currency equivalent for the selected service rather than assuming the same amount of compute, storage, or email costs the same.
Will my account be charged automatically without a limit?
Additional purchases and optional automatic top-ups follow the authorization and limits you choose. Review the terms and spending settings before enabling top-ups or approving a resource change.
From your workspace to the web