Your Atlas bill
Atlas has no fixed monthly subscription. New workspaces add prepaid service balance before deploying. Verified monthly usage invoices deduct from that balance automatically after reconciliation, including applicable tax. Review your balance, payments, invoice line items, and actual totals in Billing. Existing invoice arrangements continue until an administrator switches to prepaid. Payments and legal invoice amounts are in INR; dollar displays use indicative reference conversions.
Deployment can incur service charges. A workspace administrator must complete the required billing setup before deploying. Recent usage can be awaiting reconciliation and not yet deducted. Balance and planning budgets are not hard spending caps. Stopping compute does not remove stored data or its charges. This guide does not quote a workload price: actual application requirements and billing records determine charges.
Read measurements in context
Usage and atlas_get_usage report available hosting, database, operation, and storage measurements. Read each metric's availability, reporting period, update time, and project coverage. Measurements can arrive later than the underlying activity.
An unavailable or blocked measurement is not zero usage. A metric can be unavailable because the connected account cannot access a reporting source. A cumulative recorded operation count is different from an independently measured monthly total.
Atlas does not turn missing measurements into a fabricated invoice estimate. Invoice charges and telemetry are separate records; use the actual invoice for the payable amount.
Review before changing resources
Ask your AI to inspect the relevant project's actual usage and describe any missing coverage before recommending a change. Keep existing resources until an authorized change or migration has been verified.
For a billing question, include the invoice reference and relevant period when contacting Atlas support. Do not include credentials or payment secrets.