App Services Billing Model

Parent: MongoDB Atlas App Services · Published reference · snapshot 2026-10-02

Depth-first rabbithole dossier for App Services Billing Model; source-anchored research pack.

These notes link each claim to its source. A source may be a research report hosted on this site rather than the primary document. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

Structure and components

1. The billing page carries an end-of-life banner: "Atlas App Services has reached its end-of-life status and is no longer actively supported by MongoDB. Triggers remain available in the Atlas UI." https://www.mongodb.com/docs/atlas/app-services/billing.md 2. Apps are billed "according to how much they're used on a daily basis" across four independently measured usage types: Requests, Compute, Atlas Device Sync, and Data Transfer. https://www.mongodb.com/docs/atlas/app-services/billing.md 3. All App Services Apps in one Atlas project share a single daily free tier. Usage below the thresholds i [source]
52. Stitch launched in public beta on 2017-06-20. TechCrunch reported "Pricing is currently based on the amount of data transfer". [S24] (H18) 53. MongoDB's World 2017 deck offered 25 GB free per month, then $1/GB, with Stitch free during the World event. [S25] (H19) 54. A later Stitch deck charged $1/GB from Stitch to clients or services, with 25 GB free per month and free transfer to Atlas. [S26] (H20) 55. Stitch therefore had one meter, egress, on a monthly allowance. [S24, S26] (H21) 56. The 2019-06-18 announcement that Realm and Stitch would merge said nothing about pricing. [S21] (H22) 5 [source]
31. App Services is invoiced monthly as part of Atlas. All Atlas payment methods work, including prepaid Atlas Credits. https://www.mongodb.com/docs/atlas/app-services/billing.md 32. Costs of a linked Atlas data source are billed separately from App Services, as Atlas charges. That includes database operations, backup, and cluster-to-App-Services egress (an Atlas Data Egress charge). https://www.mongodb.com/docs/atlas/app-services/billing.md 33. Atlas invoices list App Services as its own row in the "Summary by Service" table. Cost Explorer can group monthly usage by an "App Services" service, [source]
- The gate is **met on host count, but not on publisher independence.** Sources come from mongodb.com (docs, pricing, community forums), api.github.com (MongoDB's own doc-source history), oneuptime.com and maxkarlsson.dev. - MongoDB authored or hosted every substantive pricing claim. The two third-party sources are thin: oneuptime mentions only alert types, and maxkarlsson.dev (2020-08-25) says only that "MongoDB recommends _against_ using the free tier in production". - No independent third party confirmed or refuted the daily free tier. - The disconfirming sources are MongoDB's own pricing p [source]

How it works

35. The billing page moved to the new docs-app-services repo on 2022-05-10. Commit #31 on 2022-06-01 renamed "Realm" to "App Services." https://api.github.com/repos/mongodb/docs-app-services/commits?path=source/billing.txt&per_page=100 36. MongoDB's Realm SLA change log records a product rename from "MongoDB Realm" to "Atlas App Services" on 2022-07-19. https://www.mongodb.com/legal/sla/realm 37. Commit [ticket identifier redacted by repository privacy gate] (2022-10-24) replaced "Once the sum of all application usage in a project exceeds a free tier usage threshold, App Services immediately begins to bill for any additional usage" with [source]
**Handoffs for concept-family-explorer (not chased):** - Atlas Data Egress pricing - Atlas Triggers pricing after EOL and its successor SKU - Atlas billing alerts and the lack of cost caps - Maximum Throughput Triggers - Edge Server GA pricing - How App Services appears in Atlas invoice line items and FOCUS SKUs - Device Sync deprecation and migration alternatives [source]
22. Incident (2023-04-21): a Unity bug wrote player state every frame. It produced 39,000 writes in a 2-minute spike, used up the free compute in that spike, and was billed $2.60, rising to over $14. The user estimated a $500+ exposure. https://www.mongodb.com/community/forums/t/i-was-charged-2-60-when-using-m0-forever-free-tier/223141 23. A MongoDB staff member answered (2023-04-24/27) that no cost-capping feature exists to stop App Services at a spend threshold. Billing alerts only send notifications. https://www.mongodb.com/community/forums/t/i-was-charged-2-60-when-using-m0-forever-free-ti [source]
- Atlas Device Sync deprecation and migration alternatives - Atlas Triggers billing after App Services EOL - Atlas data-egress (data transfer) billing - Atlas billing alerts and the lack of cost caps - Edge Server preview pricing [source]
**Inherited, not repeated:** The parent says that triggers still consume the App Services billing budget after EOL, and that rate limits are shared with request billing. The claims below add only child-specific detail, corrections, or limits. [source]
**Inherited parent facts:** the parent notes say "Triggers remain active and continue to consume the shared App Services billing budget" and "rate limits are shared with request billing". The claims below do not repeat those. They add only deltas, corrections and limits. [source]
**Out of scope:** Atlas cluster, backup and egress pricing beyond where it meets App Services. Also out of scope: how Triggers, Functions, Rules and Auth work, and the alternatives to Device Sync and the Data API. Those are sibling or parent frontier items. [source]
- Atlas Triggers post-EOL pricing and successor SKU. - Atlas invoice line-item and FOCUS SKU naming for App Services. - Atlas Data Egress pricing. - Edge Server GA pricing. [source]
- S1 https://www.mongodb.com/docs/atlas/app-services/billing/ (the reports also cite it as https://www.mongodb.com/docs/atlas/app-services/billing.md) - S2 https://www.mongodb.com/pricing - S3 https://api.github.com/repos/mongodb/docs-app-services/commits/d696564 - S3 https://github.com/mongodb/docs-app-services/pull/780 - S4 https://api.github.com/repos/mongodb/docs-app-services/commits/d805ca2 - S5 https://api.github.com/repos/mongodb/docs-app-services/commits/86b8107 - S6 https://api.github.com/repos/mongodb/docs-app-services/commits/0d995da - S6 https://github.com/mongodb/docs-app-services [source]
Handoffs for concept-family-explorer (not chased here): Atlas Data Egress pricing; Atlas billing alerts and cost controls; Atlas Triggers throughput limits (Maximum Throughput Triggers). [source]
- https://www.mongodb.com/docs/atlas/app-services/billing.md - https://www.mongodb.com/docs/atlas/app-services/deprecation.md - https://www.mongodb.com/docs/atlas/app-services/sync/device-sync-deprecation.md - https://www.mongodb.com/docs/atlas/atlas-ui/triggers/functions.md - https://www.mongodb.com/docs/atlas/atlas-ui/triggers/limitations.md - https://www.mongodb.com/pricing - https://api.github.com/repos/mongodb/docs-app-services/commits?path=source/billing.txt&per_page=100 - https://api.github.com/repos/mongodb/docs-app-services/commits/d696564 - https://api.github.com/repos/mongodb/docs-a [source]
- https://www.mongodb.com/docs/atlas/app-services/billing.md - https://www.mongodb.com/docs/atlas/app-services/deprecation.md - https://www.mongodb.com/docs/atlas/app-services/sync/device-sync-deprecation.md - https://www.mongodb.com/docs/atlas/atlas-ui/triggers.md - https://www.mongodb.com/pricing - https://www.mongodb.com/legal/sla/realm - https://www.mongodb.com/company/newsroom/press-releases/mongodb-unveils-vision-for-the-development-products-realm - https://www.mongodb.com/community/forums/t/i-was-charged-2-60-when-using-m0-forever-free-tier/223141 - https://api.github.com/repos/mongodb/ [source]
- https://www.mongodb.com/docs/atlas/app-services/billing/ (fetched as `billing.md`, 2026-10-02) - https://www.mongodb.com/pricing - https://github.com/mongodb/docs-app-services/pull/780 - https://github.com/mongodb/docs-app-services/pull/752 - https://github.com/mongodb/docs-app-services/commits/master/source/billing.txt - https://www.mongodb.com/docs/atlas/app-services/deprecation/ - https://www.mongodb.com/docs/atlas/app-services/sync/device-sync-deprecation/ - https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-adminappmeasurements - https://www.mongodb [source]
- https://www.mongodb.com/docs/atlas/app-services/billing.md - https://raw.githubusercontent.com/mongodb/docs-app-services/master/source/billing.txt - https://api.github.com/repos/mongodb/docs-app-services/commits?path=source/billing.txt&per_page=50 - https://api.github.com/repos/mongodb/docs-app-services/commits/d696564 - https://api.github.com/repos/mongodb/docs-app-services/commits/d805ca2 - https://api.github.com/repos/mongodb/docs-app-services/commits/86b8107 - https://api.github.com/repos/mongodb/docs-app-services/commits/0d995da - https://www.mongodb.com/pricing - https://www.mongodb.co [source]

Measurements and reference values

25. MongoDB moved its App Services doc source into the docs-app-services repo on 2022-05-10 and renamed "Realm" to "App Services" in the docs on 2022-06-01. https://api.github.com/repos/mongodb/docs-app-services/commits?path=source/billing.txt&per_page=50 26. From 2022-10-24 the docs said: "As soon as a project exceeds any monthly free tier threshold, App Services starts billing for additional usage of any kind for that project." The earlier wording was "Once the sum of all application usage in a project exceeds a free tier usage threshold, App Services immediately begins to bill for any addit [source]
43. Commit [ticket identifier redacted by repository privacy gate], "Billing Migration and Modernization" (2024-07-01), changed "monthly basis … each month" to "daily basis … each day" and renamed "Monthly Free Tier" to "Daily Free Tier." https://api.github.com/repos/mongodb/docs-app-services/commits/d696564 44. The same commit replaced "1,000,000 requests or 500 hours of compute or 10,000 hours of sync runtime" and "10GB of data transfer" with daily limits of 50,000 requests, 25 hours of compute, 30,000 minutes of sync, and 0.5 GB of data transfer. https://api.github.com/repos/mongodb/docs-app-services/commits/d696564 45. Each daily th [source]
1. Each App Services App is billed on daily usage across four independently measured types: Requests, Compute, Device Sync and Data Transfer. https://www.mongodb.com/docs/atlas/app-services/billing.md 2. Requests cost $2.00 per 1,000,000 ($0.000002 per request). https://www.mongodb.com/docs/atlas/app-services/billing.md 3. Compute costs "$10.00 / 500 runtime hours (~$0.000000005 / ms)". https://www.mongodb.com/docs/atlas/app-services/billing.md 4. *Derived:* $10 / 500 h works out to about $5.56×10⁻⁹ per ms. So the rounded $5×10⁻⁹/ms figure in the doc's formulas and examples is about 10% below [source]
21. The current docs give a single daily free tier shared by all Apps in an Atlas project: 50,000 requests, 25 h compute, 30,000 sync minutes and 0.5 GB data transfer per day. https://www.mongodb.com/docs/atlas/app-services/billing.md 22. The worked examples subtract each free-tier allowance from its own meter independently. For example, the mobile app is billed for requests minus 50,000 and for sync minus 30,000 minutes. https://www.mongodb.com/docs/atlas/app-services/billing.md 23. The free tier is scoped to the project, not the App. Splitting work across several Apps in one project does not [source]
1. **Daily or monthly free tier.** - Docs (since 2024-07-01): a daily free tier of 50k requests, 25 h compute, 30k sync minutes and 0.5 GB. https://www.mongodb.com/docs/atlas/app-services/billing.md - Pricing page (2026-10-02): a monthly tier of "1 million requests OR 500 hours of compute OR 10,000 hours of sync runtime (whichever occurs first), plus 10 GB". https://www.mongodb.com/pricing - The pricing page matches the pre-2024-07-01 docs (commit d696564). Most likely it was never updated, but no source says which one invoicing actually uses. 2. **Per-meter or "any threshold" trigger.** - Old [source]
Pass 0 (billing docs): 16 claims. Pass 1 (docs git history, pricing page, forum): +9 → 25 (36%). Pass 2 (function limits, trigger limits, third-party): +4 → 29 (14%). Pass 3 (search for independent sources of the daily model, EOL pages): +0 new billing mechanics, only gate evidence (0%). Verdict: **BUDGET_EXHAUSTED (soft stop)**. Only one pass came in under 5%, and the stop rule needs two in a row. One more pass is still likely to pay off on two questions: whether a timed-out function is billed for its full runtime, and what is billed after EOL. Both would need MongoDB support or invoice evide [source]
**Verdict: BUDGET_EXHAUSTED (soft stop), not SATURATED-DEPTH.** Only one pass came in under 5%, and the rule needs two in a row. This session also could not use Firecrawl, shell curl or the 403-blocked forum threads. One more pass on how App Services line items appear in a real Atlas invoice CSV or FOCUS SKU export might still yield claims. [source]
26. All Apps in one Atlas project share **one daily free tier**. Usage under the thresholds on a given day is not billed. [S1] (M21, H3, E1, P21) 27. The daily thresholds are 50,000 requests, 25 compute hours, 30,000 sync minutes and 0.5 GB of transfer. [S1] (all four reports) 28. The worked examples subtract each allowance from its own meter. The mobile example goes over the request allowance and still subtracts 30,000 sync minutes. The backend example goes over requests and still subtracts 90,000,000 compute ms. [S1] (M23, H47, E6, P22) 29. The current page never states the per-meter rule in [source]
The last two rows are both under 5%. That only shows the four reports overlapped heavily on the same MongoDB sources; it does not mean the questions are exhausted. Each report soft-stopped independently because web, shell and Firecrawl access was restricted. **Verdict: BUDGET_EXHAUSTED.** A next pass could still answer four questions: 1. Which free-tier model the invoice engine applies, using real invoice CSV or FOCUS SKU line items. 2. Whether a timed-out function is billed for its full runtime. 3. What successor SKU or pricing applies to Atlas Triggers after EOL. 4. When the 2024 daily switc [source]
12. Compute is billed per millisecond of runtime for non-sync, non-auth requests at $10 / 500 runtime hours (~$0.000000005/ms). https://www.mongodb.com/docs/atlas/app-services/billing.md 13. Internal inconsistency: the prose says the memory multiplier "begins at 1 … and increases by 1 for every 32MB." The formula, however, is `Runtime × (Memory (MB) / 32MB)`. Read literally, the formula gives a fractional multiplier below 1 for small requests, which contradicts the prose floor of 1. The worked examples use multiplier 1 for 4 KB payloads, which matches the prose. https://www.mongodb.com/docs/at [source]
18. MongoDB launched Stitch as a backend-as-a-service in public beta on 2017-06-20. TechCrunch reported that "Pricing is currently based on the amount of data transfer developers need." https://techcrunch.com/2017/06/20/mongodb-launches-stitch-a-new-backend-as-a-service-and-brings-atlas-to-azure-and-google 19. MongoDB's MongoDB World 2017 launch deck (Drew DiPalma) offered "Atlas Free Tier + 25 GB Free per Month" and said Stitch was "100% Free during world, and only $1/GB throughput afterwards." https://www.slideshare.net/slideshow/introducing-stitch/77211235 20. A later Stitch introduction de [source]
Verdict: **BUDGET_EXHAUSTED (tool-constrained), not SATURATED-DEPTH.** No two consecutive passes fell below 5%. Two more passes could still pay off: (a) archived snapshots of the Stitch billing docs (2018–2019) and of mongodb.com/pricing around July 2024; (b) forum or support notices announcing the daily free tier. [source]
15. Requests cost $2.00 per 1,000,000 ($0.000002 each). [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 16. Compute costs $10.00 per 500 runtime hours, which the docs state as "~$0.000000005 / ms". [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 17. The exact compute rate is $10 / (500 h × 3,600,000 ms/h) ≈ $0.00000000556/ms. So the published per-ms figure understates the hourly price by about 10%. The worked examples use the rounded per-ms figure. For example, the backend example's 15,246,000,000 ms costs $76.23 at the rounded rate and ≈ $84.70 at the exact rate. [source]
28. Before July 2024, the docs described a **monthly** project-wide free tier: "1,000,000 requests or 500 hours of compute or 10,000 hours of sync runtime (whichever occurs first)", plus 10 GB of transfer. [doc, removed lines] https://github.com/mongodb/docs-app-services/pull/780 29. Under "whichever occurs first", crossing any one threshold ended the whole free tier for the project. The pricing page says: "Once the sum of all application usage in a project exceeds the free-tier threshold, Atlas begins billing for additional usage." [doc] https://www.mongodb.com/pricing 30. The docs commit "DO [source]
| Pass | Focus | New claims | Cumulative | New-info rate | |---|---|---|---|---| | 0 | Current billing doc | 27 | 27 | 100% | | 1 | Docs diff (PR #780), pricing page, deprecation pages | 9 | 36 | 25% | | 2 | Admin API metering, trigger limits, Edge Server diff, third-party | 5 | 41 | 12% | [source]
Verdict: **BUDGET_EXHAUSTED (soft stop), not SATURATED-DEPTH.** The rate is falling, but two consecutive passes under 5% were not reached. Web search, scraping, and shell were restricted this run. Likely payoff from one or two more passes: the MongoDB forum threads (403 here), a dated announcement of the July 2024 billing change, and actual invoice line-item names. [source]
| Pass | Focus | New claims | Rate | |---|---|---|---| | 0 | Billing doc baseline | 22 | 100% | | 1 | Pricing page, deprecation pages, forum reports | 12 | 35% | | 2 | Doc-source git history (dated changes) | 7 | 17% | | 3 | Function constraints, derived bounds, Atlas billing doc | 4 | 9% | | 4 | Third-party sweep (cloudzero, amnic, freetier.co, oneuptime, agentdeals) | 1 | 2% | [source]

Problems, failure modes and limitations

| Parent says (inherited) | Child delta | |---|---| | "Triggers remain active and continue to consume the shared App Services billing budget" | **Partly supported, not confirmed.** The pricing page still lists Triggers and Functions under App Services pricing [S2]. The current Atlas Triggers and Functions pages say nothing about billing [S15, S16]. No successor pricing page for Triggers was found (H55, P43–44, E28). | | "Rate limits shared with App Services request billing" | **Made concrete.** The default cap is 10,000 concurrent requests, with HTTP 429 above it. MongoDB says the cap exists p [source]
41. The default concurrency cap is 10,000 requests, with HTTP 429 above it. MongoDB says it partly guards against "unintended billing charges", and support can raise it. [S17] (M35, E16; the two reports describe what the cap applies to differently, see D8) 42. Functions are capped at 300 s of runtime and 350 MB of memory per request. [S16] (E14, P17) 43. *Derived:* under the step rule, the largest multiplier is about 11 (P18), or "about 11–12" (E15). One request's compute is then capped at about $0.0165 at the rounded rate. *Synthesis:* about $0.0183 at the exact rate. [S1, S16] 44. The docs d [source]
76. The billing page has an EOL banner ("…Triggers remain available in the Atlas UI"). It changes no price or threshold. [S1] (H1, M41) 77. Database Triggers are not deprecated, and Functions used from Triggers remain. Auth triggers are deprecated. [S12] (M37, H54, E26, P39) 78. Device Sync was removed on 2025-09-30, so the sync meters have nothing left to measure. The billing page still describes both. [S13, S1] (M38, H53, E25, P40) 79. Once App Services Auth is removed, auth triggers stop firing and stop producing billable requests. [S12] (M39, E26, P42) 80. The billing page still lists Grap [source]
7. The following do not count as requests: requests to an authentication provider, requests blocked by the app's IP Access List, and requests to an invalid HTTP endpoint. https://www.mongodb.com/docs/atlas/app-services/billing.md 8. If a function calls another function, both executions count as one request. A trigger execution's request also covers the functions and EventBridge forwarding it invokes. https://www.mongodb.com/docs/atlas/app-services/billing.md 9. A custom error handler that runs after an EventBridge trigger fails counts as a billable function execution. https://www.mongodb.com/d [source]
25. Device Sync, the Data API/HTTPS endpoints, the Device SDKs, App Services Authentication, Wire Protocol, and Rules/Roles are deprecated. Device Sync's EOL was 2025-09-30. https://www.mongodb.com/docs/atlas/app-services/sync/device-sync-deprecation.md ; https://softinstigate.com/en/blog/posts/mongodb-deprecates-data-api/ 26. Database Triggers, and Functions used from Triggers, are not deprecated. Authentication Triggers are deprecated and stop firing once App Services Authentication is gone. https://www.mongodb.com/docs/atlas/app-services/deprecation.md 27. The billing page still lists Graph [source]
50. GraphQL API and Static Hosting deprecation notes reached the billing page on 2024-03-12 and 2024-03-26. https://api.github.com/repos/mongodb/docs-app-services/commits?path=source/billing.txt&per_page=100 51. Commit #842 "Deprecation" (2024-09-09) added deprecation structure to all App Services docs and set noindex/norobots on every page. Commit [ticket identifier redacted by repository privacy gate] removed the noindex directive on 2024-10-16. https://api.github.com/repos/mongodb/docs-app-services/commits?path=source/billing.txt&per_page=100 52. Commit #852 (2024-10-01) removed Edge Server references from the billing page. https://a [source]
1. App Services bills Apps on daily usage across four independently measured dimensions: Requests, Compute, Device Sync runtime, and Data Transfer. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 2. Five request types count as billable requests: Function executions, Trigger executions, GraphQL requests, HTTPS (endpoint/webhook) requests, and Sync operations. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 3. If a function calls another function, both executions count as one request. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 4. A trigger execut [source]
37. App Services has reached end-of-life. Database Triggers are not deprecated, and Functions stay available inside Triggers. [doc] https://www.mongodb.com/docs/atlas/app-services/deprecation/ 38. Device Sync is end-of-life and is removed on 2025-09-30. After that, the Sync-runtime and sync-operation request dimensions have no live source. [doc+derived] https://www.mongodb.com/docs/atlas/app-services/sync/device-sync-deprecation/ 39. Authentication triggers are deprecated. After App Services Authentication is removed they no longer execute, which ends that source of billable trigger requests. [source]
39. App Services is at end of life. Database triggers and Functions-with-Triggers remain available; authentication triggers are deprecated. https://www.mongodb.com/docs/atlas/app-services/deprecation.md 40. Device Sync was removed on 2025-09-30. That retires the sync-runtime meter and the sync-operation request type in practice, but the billing page still describes both. https://www.mongodb.com/docs/atlas/app-services/sync/device-sync-deprecation.md ; https://www.mongodb.com/docs/atlas/app-services/billing.md 41. GraphQL is marked deprecated on the billing page. The Data API and HTTPS Endpoint [source]
1. Apps are billed on **daily** usage across four separately measured meters: Requests, Compute, Device Sync runtime and Data Transfer. [S1] (M1, H2, P1) 2. Five request types are billable: Function executions, Trigger executions, GraphQL requests, HTTPS endpoint or webhook requests, and Sync operations. [S1] (M2, H8, P9) 3. If a Function calls another Function, both together count as one request. [S1] (M3, H9, E8, P10) 4. A Trigger execution is one request, and that request covers everything the trigger invokes, including Functions and EventBridge forwarding. [S1] (M4, H10, E8, P11) 5. EventB [source]
35. By default Atlas limits Trigger request traffic to 10,000 concurrent requests and returns HTTP 429 above that. The docs say the limit exists partly to prevent "unintended billing charges". It can be raised through support. [doc] https://www.mongodb.com/docs/atlas/atlas-ui/triggers/limitations/ 36. Each collection with a Database Trigger holds one change stream. The cluster tier caps change streams: 5 on a free cluster, 10 on Flex, 100 on M10/M20, and 1,000 on M30+. This caps how many trigger sources can generate billable requests. [doc+derived] https://www.mongodb.com/docs/atlas/atlas-ui/t [source]
9. Billable request types are Function executions, Trigger executions, GraphQL requests, HTTPS/webhook requests and Sync operations (changeset upload, conflict resolution, changeset download). https://www.mongodb.com/docs/atlas/app-services/billing.md 10. If a Function calls another Function, both executions bill as one request. https://www.mongodb.com/docs/atlas/app-services/billing.md 11. A Trigger execution is one request that includes every operation it invokes, including Functions and EventBridge forwarding. EventBridge forwarding was added to the doc on 2023-05-11. https://www.mongodb.co [source]
15. Compute covers runtime and memory for all requests except sync and authentication. It is billed per millisecond of runtime. https://www.mongodb.com/docs/atlas/app-services/billing.md 16. The doc's prose describes a step multiplier: it "begins at 1 … and increases by 1 for every 32MB of memory" a request uses. https://www.mongodb.com/docs/atlas/app-services/billing.md 17. Functions stop at 300 s of runtime per request and may use up to 350 MB of memory. https://www.mongodb.com/docs/atlas/atlas-ui/triggers/functions.md 18. *Derived from 3, 16 and 17:* one request can bill at most about 300,0 [source]

Comparisons and alternatives

1. The current billing docs define a **daily** free tier: "All App Services Apps in a MongoDB Atlas project share a single daily free tier." The thresholds are 50,000 requests, 25 hours of compute, 30,000 minutes of sync runtime, and 0.5 GB of data transfer. https://www.mongodb.com/docs/atlas/app-services/billing.md 2. Commit d696564 ("[ticket identifier redacted by repository privacy gate] Billing Migration and Modernization", 2024-07-01) made the switch from monthly to daily. It removed "1,000,000 requests or 500 hours of compute or 10,000 hours of sync runtime (whichever occurs first)" and "10GB of data transfer". It added the daily [source]
- **D1. Daily or monthly free tier** (raised by all four reports). - The docs since 2024-07-01 say daily, per meter: 50k / 25 h / 30k min / 0.5 GB [S1, S3]. - The pricing page on 2026-10-02 says monthly, coupled: "1M requests OR 500 h compute OR 10,000 h sync (whichever occurs first) + 10 GB" [S2]. - metacto (updated 2025-10-13) repeats the pricing page [S27], so it is not an independent confirmation. - The 2023 staff forum answer [S22] states the monthly model, but it predates the change. - The commit history suggests the pricing page is stale. No source says which model the invoices apply. - [source]
- **Daily vs. monthly free tier (the main conflict).** Since 2024-07-01 the docs say the free tier is daily: 50K requests, 25 h compute, 30K sync minutes, and 0.5 GB (https://www.mongodb.com/docs/atlas/app-services/billing.md). On 2026-10-02 the MongoDB pricing page still says "a monthly free tier: 1 million requests or 500 hours of compute, or 10,000 hours of sync runtime (whichever occurs first), plus 10 GB." It also still uses the older "Once the sum of all application usage … exceeds" wording (https://www.mongodb.com/pricing). Third-party pricing guides repeat the monthly figures. No sourc [source]
- **Daily vs monthly free tier.** Side A, the billing docs since 2024-07-01: daily, 50k requests / 25 h / 30,000 sync-min / 0.5 GB (https://www.mongodb.com/docs/atlas/app-services/billing.md). Side B, the MongoDB pricing page as fetched 2026-10-02: monthly, "1 million requests OR 500 hours of compute OR 10,000 hours of sync runtime … plus 10 GB" (https://www.mongodb.com/pricing). A third-party cost guide (published 2025-07-14, updated 2025-10-13) repeats side B (https://www.metacto.com/blogs/the-true-cost-of-mongodb-a-deep-dive-into-pricing-and-integration). A 2023 staff forum answer also stat [source]
21. All Apps in one Atlas project share a single **daily** free tier. Usage below the thresholds in a given day is not billed. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 22. The daily thresholds are 50,000 requests, 25 compute hours, 30,000 sync minutes, and 0.5 GB of data transfer. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 23. The free tier is subtracted separately from each dimension. Each worked example deducts the allowance per dimension: 50,000 requests, 90,000,000 compute ms (= 25 h), 30,000 sync min, and 0.5 GB. Going over one dimension does not [source]
23. MongoDB's docs repo added the first MongoDB Realm billing page on 2020-05-18 ([ticket identifier redacted by repository privacy gate], "Realm Billing"). https://api.github.com/repos/mongodb/docs-realm/commits?path=source/billing.txt&per_page=100 24. That first page already billed "on a monthly basis" and already used the four meters at today's prices: $2.00 per 1M requests, $10.00 per 500 compute hours, $0.08 per 1M sync minutes, and $0.12 per GB. https://raw.githubusercontent.com/mongodb/docs-realm/ca688ac9/source/billing.txt 25. The data-transfer price fell from Stitch's $1/GB to $0.12/GB, and the monthly free egress fell from 25 G [source]
- Sources: 9 distinct documents on 5 hosts: mongodb.com (docs, pricing, forum, newsroom, legal), api.github.com and raw.githubusercontent.com (MongoDB docs-repo history), techcrunch.com, and slideshare.net. - Independence: **met only partially.** At least 3 sources and different hosts are satisfied. But only TechCrunch is editorially independent of MongoDB, and it covers only the 2017 Stitch model. Everything after 2020 rests on MongoDB-authored material: docs, git history, pricing page, and staff forum posts. The git history is the strongest primary evidence because it is dated and verbatim. [source]
- **Monthly vs daily free tier (unresolved, high impact).** The docs billing page, updated 2024-07-01, says the free tier is daily, per dimension: 50k / 25 h / 30,000 min / 0.5 GB (https://www.mongodb.com/docs/atlas/app-services/billing/). The live pricing page, read 2026-10-02, still says monthly, coupled "whichever occurs first": 1M / 500 h / 10,000 h + 10 GB (https://www.mongodb.com/pricing). A third-party summary updated 2025-10-13 repeats the pricing-page version (https://www.metacto.com/blogs/the-true-cost-of-mongodb-a-deep-dive-into-pricing-and-integration). The docs change is newer and [source]

Facts and statements

Run: /rabbithole, 2026-10-02. Concept: **App Services Billing Model** (parent: MongoDB Atlas App Services). [source]
- Hosts: mongodb.com (docs, pricing, forum), api.github.com (MongoDB docs repo history), metacto.com, softinstigate.com. That is four hosts, so the ≥3 host requirement is met. - Independent authorship is weak. Most claims come from MongoDB itself (docs, pricing page, docs repo). The non-MongoDB sources are one forum user, one cost-guide vendor, and one migration-vendor blog. No neutral source states the daily model, and the search for "50,000 requests" daily App Services found only Firestore results. The daily-model claims rest on MongoDB primary sources alone. - Disconfirming evidence was sou [source]
**In scope:** how Atlas App Services meters and prices usage. That covers the four billing dimensions, how each one is counted, the free tier, invoicing, the formulas, the internal inconsistencies in the docs, how the model changed over time, and how end-of-life affects billing. [source]
**In scope:** how Atlas App Services usage is metered and priced. That covers the four meters (requests, compute, sync runtime, data transfer), the free tier, units and formulas, what is excluded, invoicing, cost controls, how the model changed over time, and what App Services end-of-life (EOL) changes for billing. [source]
**In scope:** the four meters, how requests are counted, prices and formulas, the free tier, invoicing and metering, limits and how spending runs away, the history from Stitch to Realm to App Services, and what end-of-life (EOL) does to billing. [source]
In scope: how Atlas App Services meters and bills usage (requests, compute, sync runtime, data transfer), the free tier, invoicing, and how those rules changed over time and around end of life (EOL). Out of scope: sibling App Services features (auth, rules, deployment), Atlas cluster billing, and migration targets. Claims inherited from the parent extract are not repeated. Only deltas, corrections, and limits appear below. [source]
20. App Services bills egress to clients and external services at $0.12/GB. Data moving from a linked Atlas cluster into App Services is billed separately, as Atlas Data Egress. One read path can therefore pay two egress charges. https://www.mongodb.com/docs/atlas/app-services/billing.md 21. Linked data-source costs (database operations, backup) are billed separately from App Services. https://www.mongodb.com/docs/atlas/app-services/billing.md [source]
In scope: how MongoDB has metered and charged for its serverless app backend (Stitch → MongoDB Realm → Atlas App Services), the metered dimensions, the free-tier rules, and how the rules changed over time. Out of scope: Atlas cluster billing, Device Sync / Data API / GraphQL as features, the deprecation programme beyond its billing effect, and migration alternatives. Those are sibling frontier items. [source]
26. App Services charges appear on the monthly Atlas invoice, which totals all daily overages. Any Atlas payment method works, including prepaid Atlas Credits. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 27. Costs from a linked Atlas data source, such as database operations and backup, are billed separately from App Services. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ [source]
The gate is **met on host count but only weakly on independence.** Four hosts were used: mongodb.com (docs, pricing, and Admin API reference), github.com (the mongodb/docs-app-services history and diffs), and metacto.com. All substantive content comes from MongoDB. GitHub is MongoDB's own docs repo, and metacto paraphrases the pricing page. No independent measurement of real invoices was found. The disconfirming source I looked for did turn up: the pricing page contradicts the docs. The MongoDB community forum threads on App Services billing returned 403 and were not read. [source]
34. App Services charges appear on the monthly Atlas invoice, which totals the daily overages. That sentence was added in commit d696564. [S1, S3] (M26, M30, H5, E3, P31) 35. Any Atlas payment method works, including prepaid Atlas Credits. [S1] (M26, H6, P31) 36. Costs of the linked data source, such as database operations and backup, are billed separately. [S1] (M27, H6, E21, P32) 37. Atlas invoices show App Services as its own row in "Summary by Service". Cost Explorer can group by an "App Services" service over up to 18 months. [S19] (P33) 38. The App dashboard shows the current day's usage [source]
Run: /rabbithole, 2026-10-02. Parent: MongoDB Atlas App Services. [source]
32. The App dashboard shows the current day's usage. [doc] https://www.mongodb.com/docs/atlas/app-services/billing/ 33. The Admin API `GET /groups/{groupId}/apps/{appId}/measurements` returns five measurements: `request_count`, `compute_time` (HOURS), `data_out` (GIGABYTES), `sync_time` (GIGABYTE_SECONDS), and `mem_usage`. [doc] https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-adminappmeasurements 34. The measurements endpoint defaults to the current calendar month (UTC). It offers only `P31D` and `PT1H` granularity, with no daily option. To reconcile ag [source]
Retrieved 2026-10-02. Parent: MongoDB Atlas App Services. [source]
Inherited parent evidence is excluded. The shared Firecrawl cache (Data API partner repos, Hasura, auth and rules docs) holds **no billing content** and is excluded. All four reports agree on this. [source]
| Origin | Independent of MongoDB? | What it supports | |---|---|---| | MongoDB, Inc.: docs, pricing, Admin API, docs-repo git history, SLA, newsroom, staff forum posts, Stitch decks | No (this is the single primary origin) | Everything about current mechanics and history | | TechCrunch [S24] | Yes | The 2017 Stitch egress model only | | Forum end users [S22, S23] | Yes (first-hand) | The runaway-spend incident and the request-count mismatch | | softinstigate [S28] | Yes | The deprecation list only | | oneuptime [S29] | Yes | The alert type name only | | maxkarlsson.dev [S30] | Yes | "Recommen [source]
17. Sync runtime is billed for the whole time a client has an active connection, "even if they are not transferring data". An idle open connection is billable. https://www.mongodb.com/docs/atlas/app-services/billing.md 18. Unit inconsistency: the prose says sync is "billed at a set rate for each millisecond of sync runtime per user", but the price and formula use minutes ($0.08 / 1,000,000 runtime minutes). https://www.mongodb.com/docs/atlas/app-services/billing.md 19. Device Sync pauses automatically after 30 days of inactivity (documented 2023-03-16, commit 7b8729f). https://api.github.com/r [source]

Related concepts

Billing — is a part of App Services Billing Model
App — is a part of App Services Billing Model
Services — is a part of App Services Billing Model
Model — is a part of App Services Billing Model

Children

No children recorded.

← the whole tree · 3D view· how to read this page