# ASP Pricing Model > Depth-first rabbithole dossier for ASP Pricing Model; source-anchored research pack. Parent: [MongoDB Atlas Stream Processing](https://llms-explorer.com/tree/mongodb-atlas-stream-processing/) · 6 facets · 52 facts · page: https://llms-explorer.com/tree/asp-pricing-model/ ## Structure and components - - At GA (May 2, 2024), MongoDB added an SP10 tier next to SP30, described as "a cost-effective option for exploratory use cases and low-traffic stream processing workloads". https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-generally-available - The GA announcement and the GA forum post contain no price figures. https://www.mongodb.com/community/forums/t/atlas-stream-processing-is-now-generally-available/278813 - In the legacy model, the billing unit was the Stream Processing Instance (SPI) worker: "charges per hour per SPI worker, where the worker — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#phase-1-ga-worker-based-billing-may-2024-dec-2025` - - Host count: the gate is met. Sources come from mongodb.com (docs, blog, pricing, forums), raw.githubusercontent.com and api.github.com (the mongodb/docs repo history), delbridge.solutions, srvrlss.io and oneuptime.com. - Authorial independence: weak. Every primary fact traces to MongoDB itself, through its docs, docs git history, blog or pricing page. The third-party pages only confirm parts of it (the 4-processors-per-worker rule and the current price range) or contradict it (oneuptime). No independent dated technical report on the 2025 pricing change was found. - Tool limits: firecrawl and — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#quality-gate` ## How it works - **In scope:** how MongoDB Atlas Stream Processing (ASP) bills: what it bills, the billing unit, granularity, tier price ranges, data transfer and networking charges, how autoscaling and tier limits affect cost, and how and when the model changed. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#scope` - - Partly met. Five hosts were used: mongodb.com (docs, pricing, blog, changelog), amnic.com, oneuptime.com and checkthat.ai. - Every authoritative claim traces back to mongodb.com. The three independent hosts were all secondary, and two of them disagree with the primary docs. They served as the disconfirming search. - No independent primary source exists, because MongoDB alone sets the prices. - Saturation verdict: **BUDGET_EXHAUSTED (soft stop)**. The new-claim rate fell over 4 passes: pass 0 found about 14 claims, pass 1 about 10 new, pass 2 about 12 new (regional tables and autoscaling), an — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#quality-gate` - - C13. Atlas does not charge for ASP storage. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - C14. ASP charges for all egress data transfer, priced by transfer type and destination and varying by cloud provider in tiers. Transfer is billed per GB of logical size before compression, as tracked by the processor's `outputMessageSize` metric. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - C15. Since 3 Dec 2025, data-transfer pricing reflects region-specific rates for both the processor's region and the destination region. — https://www.mongodb.com/d — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#other-charges` ## Measurements and reference values - - **S44.** Private preview was free. The public preview, announced 13 Feb 2024, charged "preview pricing (subject to change)" but the post gave no price figures. {blog-pp} [H][E26] - **S45.** SP30 was the only preview tier. GA on 2 May 2024 added SP10 as "a cost-effective option for exploratory use cases and low-traffic stream processing workloads". Neither the GA post nor the GA forum thread gave prices. {blog-ga} {forum-ga} [M35][H][E27] - **S46.** Legacy model, quoted from the docs: "charges per hour per SPI worker, where the worker resources and the hourly rate are determined by the SPI ti — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#history` - 5. The pricing page gives each tier a range, not a single price: SP2 $0.06–$0.08/hr, SP5 $0.11–$0.17/hr, SP10 $0.19–$0.30/hr, SP30 $0.39–$0.62/hr, SP50 $1.56–$2.49/hr. The page does not say what moves a price within its range. Region or cloud provider is the likely driver, but this is unconfirmed. — https://www.mongodb.com/pricing 6. These prices exclude data transfer: "Data transfer costs are not included in the above pricing." — https://www.mongodb.com/pricing 7. Derived arithmetic at 730 hours/month: one SP2 processor running full-time costs about $44–$58/month. One SP50 costs about $1,139– — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#tier-price-ranges-list-prices-as-published-on-2026-10-02` - - C30. The ASP SLA (created 25 Jul 2024) applies only to SP10 or higher. It needs at least one processor up for 24 h. Credits are 10% below 99.95%, 25% below 99.0% and 100% below 95.0% monthly uptime. — https://www.mongodb.com/legal/sla/cloud/stream-processing - C31. The SLA still computes credits against fees "for the specific Stream Processing Instance". That is legacy SPI wording that the per-processor/workspace model has not replaced on the SLA page. — https://www.mongodb.com/legal/sla/cloud/stream-processing — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#sla-and-credits` - - **S23.** Baseline hourly rates are SP2 $0.055, SP5 $0.11, SP10 $0.19, SP30 $0.39 and SP50 $1.56. They apply in AWS us-east-1, us-east-2 and us-west-2, Azure eastus and eastus2, and GCP us-central1 and us-west1. {billing.md} [M15] - **S24.** The highest listed rates are in Azure brazilsouth: SP2 $0.0852, SP10 $0.3091, SP30 $0.6346 and SP50 $2.5383. {billing.md} [M16] - **S25.** The pricing page gives these hourly ranges: SP2 $0.06–0.08, SP5 $0.11–0.17, SP10 $0.19–0.30, SP30 $0.39–0.62 and SP50 $1.56–2.49. They exclude data transfer. All tiers are offered on AWS, Azure and GCP. {pricing} [M17] — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#rates` - | Pass | Focus | New claims | Cumulative | New-info rate | |---|---|---|---|---| | 0 | Billing docs and pricing page | 12 | 12 | 100% | | 1 | Changelog and history | 9 | 21 | 43% | | 2 | Autoscaling and limits | 10 | 31 | 32% | | 3 | Disconfirming third parties | 3 | 34 | 9% | — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#quality-gate` - | Pass | Focus | New claims | Cumulative | New-info rate | |---|---|---|---|---| | 0 | billing doc, pricing page | 9 | 9 | 100% | | 1 | changelog, announcement, legacy blog | 8 | 17 | 47% | | 2 | autoscaling, tier guide, limitations | 10 | 27 | 37% | | 3 | SLA, Flex, third-party disconfirmation | 4 (+3 disagreements) | 31 | 13% | — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#saturation-curve` ## Problems, failure modes and limitations - 26. Private preview was free. Public preview, announced 13 February 2024, began charging "preview pricing (subject to change)". — https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-in-public-preview 27. At GA on 2 May 2024 there were two tiers: SP30, from preview, and a new lower-cost SP10. — https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-generally-available 28. Under the legacy model, ASP charged per Stream Processing Instance (SPI) worker. Each worker hosted up to four stream processors. — https://www — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#history-the-dated-changes` - 13. Kafka partition limits are 32 for SP2 and 64 for SP5. SP10 and above have no partition limit. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ 14. A `$source` that exceeds its tier's partition limit makes the processor **fail**; it does not throttle. A topic with more than 64 partitions therefore needs SP10 or higher even at low message volume. — https://www.mongodb.com/docs/atlas/atlas-stream-processing/limitations/ 15. Failover processors are supported only at SP10 or higher. Any processor that needs failover has a cost floor of $0.19–$0.30/hr. — https://www.mongodb. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#tier-limits-that-set-a-cost-floor-no-matter-the-throughput` - - On 2026-02-02, MongoDB's blog said workspaces "introduce a new per-processor pricing model" and that "All existing stream processing instances have been automatically converted to the new model with no service interruption". https://www.mongodb.com/company/blog/product-release-announcements/workspaces-and-new-tiers-for-atlas-stream-processing - The same post says SP10 and SP30 "already existed, but now have new specifications". It lists SP10 at 1 vCPU, 2 GB, 200 Mbps, parallelism 8, and SP30 at 2 vCPU, 8 GB, 750 Mbps, parallelism 16. https://www.mongodb.com/company/blog/product-release-annou — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#phase-4-docs-cleanup-and-the-current-model-2026` - - **Gate met on host count, but with a caveat.** Five hosts were used: mongodb.com, raw.githubusercontent.com (MongoDB's Terraform provider), oneuptime.com, amnic.com and delbridge.solutions. - **The authoritative facts come from a single source.** Every fact about how billing works comes from MongoDB itself. The three independent hosts agree with MongoDB on nothing about pricing that they state precisely. Two of them contradict MongoDB, and the third only repeats the "four processors per worker" figure. - **No independent primary confirmation exists.** No independent primary source, such as a — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#quality-gate` - 8. There are five tiers, each with fixed resources. SP2 has 0.25 vCPU, 512 MB, 50 Mbps, max parallelism 1, and a 32-partition Kafka limit. SP5 has 0.5 vCPU, 1 GB, 125 Mbps, parallelism 2, and a 64-partition limit. SP10 has 1 vCPU, 2 GB, 200 Mbps, parallelism 8, and no partition limit. SP30 has 2 vCPU, 8 GB, 750 Mbps, parallelism 16, and no partition limit. SP50 has 8 vCPU, 32 GB, 2500 Mbps, parallelism 64, and no partition limit. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md 9. SP10 and SP30 kept their names when the model changed, but MongoDB says they "now have new sp — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#tiers-the-rate-key` - 40. Invariant: a processor that is not running accrues no compute charge. Egress, VPC peering and Private Link are billed separately, and the docs do not tie their charges to processor state. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md 41. Limit: a processor's rate can never exceed the workspace maximum tier's rate. With autoscaling it is also capped by `maxTier`. https://www.mongodb.com/docs/atlas/atlas-stream-processing/architecture/ ; https://www.mongodb.com/docs/atlas/atlas-stream-processing/autoscaling/ 42. Limit: SP2 and SP5 cap Kafka source partitions at 32 and — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#invariants-and-limits-summary` - - C8. The listed hourly price per processor, with the range covering cloud and region, is: SP2 $0.06–$0.08, SP5 $0.11–$0.17, SP10 $0.19–$0.30, SP30 $0.39–$0.62, SP50 $1.56–$2.49. All five tiers are available on AWS, Azure and Google Cloud. — https://www.mongodb.com/pricing - C9. The tier resources are: SP2 0.25 vCPU / 0.5 GB; SP5 0.5 / 1 GB; SP10 1 / 2 GB; SP30 2 / 8 GB; SP50 8 / 32 GB. Maximum parallelism is 1, 2, 8, 16 and 64. The Kafka partition limit is 32 for SP2, 64 for SP5, and unlimited for SP10 and above. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - C10. SP1 — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#tier-price-list-data-transfer-excluded` ## Comparisons and alternatives - | # | Side A | Side B | Note | |---|---|---|---| | X1 | Per-GB egress, peering and Private Link rates are published. [M] read them from {billing.md}, the `.md` version of the page. | They are not published in the billing doc or on the pricing page. [E12][P gap 6] fetched the HTML pages. | Likely cause: the rate tables appear only in the `.md` version, not in the HTML pages that [E] and [P] fetched. This is an inference. | | X2 | SP10 and SP30 "now have new specifications". {blog-ws} [E31][P C10] concludes old and new SP10 are not comparable. | The legacy doc has the same vCPU and RAM. What cha — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#contradictions-side-by-side` - - **Announcement date vs. changelog date.** The workspaces/per-processor blog post is dated **2 February 2026**. The changelog dates workspaces to **29 October 2025** and the SP10/SP30 pricing switch to **3 December 2025**. The blog post came about 2–3 months after the change took effect. Treat the changelog as authoritative for effective dates. — https://www.mongodb.com/company/blog/product-release-announcements/workspaces-and-new-tiers-for-atlas-stream-processing vs https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ - **Third-party tier specs conflict with MongoDB.** OneUp — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#unresolved-disagreements-and-disconfirming-evidence` - - **Which date the legacy cutoff used.** The billing doc on 2025-10-29 named instances "created before October 22nd, 2025". The changelog dates the workspace release to 29 October 2025. The October 22 date may be an internal rollout date; no source explains the 7-day gap. (Sources: the 6c4739b raw doc and the changelog, both above.) - **When the conversion happened.** The changelog puts the SP10/SP30 billing switch at 3 Dec 2025. The Feb 2026 blog describes the "automatic conversion" of existing instances without giving a date. It is unclear whether the instance-to-workspace conversion happene — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#unresolved-disagreements` - - **Pricing-page ranges vs. docs tables.** The pricing page tops out at SP10 $0.30, SP30 $0.62 and SP50 $2.49 (https://www.mongodb.com/pricing). The docs list Azure brazilsouth higher, at $0.3091, $0.6346 and $2.5383 (https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md). The page ranges match AWS sa-east-1 only. Either the page excludes Azure or it is stale. - **Workspace launch date.** The changelog says 29 October 2025 (https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/). The announcement blog is dated 2 February 2026 (https://www.mongodb.com/company/blog — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#unresolved-disagreements` - 1. **Change date.** The changelog dates are 29 Oct 2025 (Workspaces) and 3 Dec 2025 (SP10/SP30 per-processor pricing). The announcement blog is dated 2 Feb 2026, and secondary sources use "February 2026". Both are kept. The changelog is the more precise record of when billing changed. Sources: https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ vs https://www.mongodb.com/company/blog/product-release-announcements/workspaces-and-new-tiers-for-atlas-stream-processing 2. **Per-document charge.** Amnic (7 Aug 2026) says ASP "bills per instance-hour plus a per-document rate". Offi — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#unresolved-disagreements-and-gaps` - **Sibling concepts for concept-family-explorer (not chased here):** - ASP vertical autoscaling - ASP workspaces - ASP failover / multi-region HA - ASP tier guide / sizing - ASP SLA - Atlas Flex cost cap - ASP vs Kafka Connector cost comparison — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#how-new-information-rate-fell-pass-by-pass` - 15. In AWS us-east-1, us-east-2 and us-west-2, Azure eastus and eastus2, and GCP us-central1 and us-west1, the hourly rates are SP2 $0.055, SP5 $0.11, SP10 $0.19, SP30 $0.39 and SP50 $1.56. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md 16. Hourly rates vary by region and cloud. The highest listed rates are in Azure brazilsouth: SP2 $0.0852, SP10 $0.3091, SP30 $0.6346 and SP50 $2.5383. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md 17. The pricing page gives ranges per tier: SP2 $0.06–0.08, SP5 $0.11–0.17, SP10 $0.19–0.30, SP30 $0.39–0.62 and SP50 — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#rates-aws-us-east-1-baseline` ## Facts and statements - 34. Legacy model: ASP charged per Stream Processing Instance (SPI) worker, and each worker supported up to four stream processors (blog dated 2024-09-09). https://www.mongodb.com/blog/post/atlas-stream-processing-cost-effective-way-integrate-kafka-mongodb 35. At GA (2024-05-02), MongoDB added the SP10 tier as a lower-cost option for exploratory and low-traffic workloads. SP30 had been the public-preview tier. https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-generally-available 36. The 29 October 2025 release replaced the instance model with Workspa — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#history-of-the-model` - In scope: how ASP is billed. That covers the billing unit, tier prices, metering granularity, data-transfer and networking charges, the move from the legacy worker/SPI model to per-processor pricing, and what the model means for sizing, autoscaling, failover and SLA credits. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#scope` - - C1. Atlas charges per hour per stream processor. The hourly rate depends on the processor's tier. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - C2. A processor is billed only while it is running, in one-second increments. A stopped processor costs nothing per hour. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - C3. Timeline correction to the parent ("workspaces introduced mid-2025"). The changelog entry dated 29 Oct 2025 replaced the instance model with Workspaces and added tiers SP2, SP5 and SP50. The entry dated 3 Dec 2025 moved SP10 and S — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#billing-unit-and-metering` - - **S1.** Atlas charges per hour per stream processor, and the processor's tier sets the hourly rate. {billing} [M1][E1][P C1][H] - **S2.** A processor is billed only while it is running, in one-second increments. {billing} [M2–3][E2][P C2] - **S3.** There is no storage charge, even though processors keep checkpointed state. {billing} [M5][E3][P C13] - **S4.** There are four billable line items: running processors, data transfer, VPC peering, and Private Link. {billing.md} [M4] - **S5.** No per-document or per-message charge is listed. {billing.md} [M6] - **S6.** The pricing page lists no free — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#billing-unit-and-metering` - **Out of scope:** ASP features that do not touch cost (windows, DLQ, `$validate`), cluster pricing, Kafka Connector and Flink pricing beyond MongoDB's own comparison claim, and sibling ASP concepts. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#scope` - This report does not repeat these inherited parent facts: per-processor pricing replaced a per-worker model in December 2025, and workspaces group processors. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#scope` - 9. ASP charges for all egress per GB, by transfer type and destination. The charge uses **logical data size before compression**, which the `outputMessageSize` metric tracks. Compressing the Kafka sink output therefore does not lower the egress bill. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ 10. The 3 December 2025 release changed data-transfer pricing to region-specific rates. The rate now depends on **both** the processor's region and the destination region. — https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ 11. ASP charges for every VPC peeri — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#data-transfer-and-networking-charged-outside-the-tier-price` - - The 29 October 2025 release "Replaces the previous instance model with Atlas Stream Processing Workspaces" and "Adds new stream processor tiers: SP2, SP5, and SP50". https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ - In the billing doc as of 2025-10-29, new SP2–SP50 processors were billed per processor. The same doc kept a carve-out: "SP10 and SP30 instances created before October 22nd, 2025 operate and bill users according to the legacy worker model." https://raw.githubusercontent.com/mongodb/docs/6c4739b26cc1f66dcc64232a6c58df0c89f80437/content/atlas/source/billing/str — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#phase-2-workspaces-and-per-processor-billing-oct-2025` - - A docs include set the legacy SP10/SP30 cutover date: "These processors update to the per-processor pricing model on December 3rd, 2025." https://raw.githubusercontent.com/mongodb/docs/64263322a7ebdaf64aef31675b6c327a2220ac95/content/atlas/source/includes/atlas-stream-processing/legacy-worker-model.rst - The 3 December 2025 changelog records two changes. It "Updates pricing for SP10 and SP30 tier stream processors from the legacy worker-based model to the per-processor pricing model". It also switches data transfer to "region-specific rates for both the stream processor and destination regio — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#phase-3-sp10-sp30-migration-3-dec-2025` - In scope: how Atlas Stream Processing (ASP) turns running stream processors into charges. That covers the billing unit, tiers, metering granularity, regional rates, the other billable line items, how tier selection and autoscaling feed the rate, and the move from the legacy worker model. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#scope` - Out of scope: ASP features unrelated to cost, Atlas cluster pricing, Kafka or Flink pricing, and sibling ASP concepts such as workspaces-as-architecture or autoscaling-as-operations. Those are only touched where they change the bill. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#scope` - 1. Atlas charges per hour per stream processor. The processor's tier sets the hourly rate. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ 2. ASP bills a stream processor only while it is running. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ ; https://www.mongodb.com/docs/atlas/atlas-stream-processing/architecture/ 3. Billing is recorded in one-second increments. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ 4. ASP has four billable line items: running stream processors, data transfer, VPC peering, and Private Link connections. h — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#billing-unit-and-metering` - 21. ASP charges for all egress data transfer, by transfer type and destination, per GB. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md 22. The billed GB are the logical data size before compression. The processor tracks this size in the `outputMessageSize` metric. Compression on the wire does not cut the ASP bill. https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md 23. AWS egress costs $0.01/GB in the same region, $0.02–0.138/GB to a different region, and $0.09–0.155/GB out to the internet. https://www.mongodb.com/docs/atlas/billing/stream-processing-co — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#data-transfer-and-networking` - Out of scope: ASP pipeline features, tier performance tuning (except where it changes cost), Atlas cluster pricing, and comparisons with Kafka Connect or Flink. Those are sibling or parent items. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#scope` - - **S30.** Atlas bills all egress per GB, by transfer type and destination. {billing} [M21][E9][P C14] - **S31.** The billed size is the logical size before compression, tracked by the `outputMessageSize` metric, so wire compression does not lower the bill. This note was added on 2026-07-02 (DOCSP-61667). {billing} [M22][E9][P C14, C17][H] - **S32.** Since 3 Dec 2025, the rate depends on both the processor's region and the destination region. {changelog} [M26][E10][P C15][H] - **S33.** Before 3 Dec 2025, egress was a flat rate per region: Azure $0.088/GB, GCP $0.090/GB, and AWS $0.065–0.150/GB — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#data-transfer-and-networking` - | Origin | Hosts | Role | |---|---|---| | MongoDB | mongodb.com (docs, pricing, blog, changelog, SLA, forums), plus raw.githubusercontent.com and api.github.com for the `mongodb/docs` repo and Terraform provider | Primary, and the only party that sets prices | | delbridge.solutions | — | Confirms the 4-processors-per-worker rule | | srvrlss.io | — | Confirms the current price range; contradicts on Flex | | checkthat.ai | — | Confirms the SP2–SP50 range; contradicts on Flex | | amnic.com | — | Contradicts the docs | | oneuptime.com | — | Contradicts the docs | — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#independent-origin-gate` - - billing: https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - billing.md: https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md - pricing: https://www.mongodb.com/pricing - changelog: https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ - arch: https://www.mongodb.com/docs/atlas/atlas-stream-processing/architecture/ - autoscale: https://www.mongodb.com/docs/atlas/atlas-stream-processing/autoscaling/ - limits: https://www.mongodb.com/docs/atlas/atlas-stream-processing/limitations/ - tierguide: https://www.mongodb.com/docs/atlas/atlas-stream-pr — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/rabbithole-synthesis.md#sources` - 1. Atlas charges per hour per stream processor. The processor's tier sets the hourly rate. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ 2. ASP bills a processor only while it is running. Atlas records billing in one-second increments. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ 3. "Atlas doesn't charge for storage." This holds even though processors keep checkpointed state. — https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ 4. **Edge case (open):** the docs say only "running" processors are billed. They never say whether a p — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#billing-unit-and-granularity` - - https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - https://www.mongodb.com/pricing - https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ - https://www.mongodb.com/docs/atlas/atlas-stream-processing/architecture/ - https://www.mongodb.com/docs/atlas/atlas-stream-processing/autoscaling/ - https://www.mongodb.com/docs/atlas/atlas-stream-processing/limitations/ - https://www.mongodb.com/company/blog/product-release-announcements/workspaces-and-new-tiers-for-atlas-stream-processing - https://www.mongodb.com/company/blog/product-release-announcements/atlas-stre — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/edge-cases.md#sources` - In scope: how MongoDB Atlas Stream Processing (ASP) billing changed over time. That covers the billing unit (worker, then processor), the tier set, the dates of each change, and the official documents that record them. Out of scope: ASP features, windowing, connectors, autoscaling mechanics, and comparisons with other products. Those are sibling or parent concepts. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#scope` - - MongoDB announced at the start of public preview that it "will begin charging for Atlas Stream Processing, using preview pricing (subject to change)". So the preview was not free. https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-in-public-preview - That announcement is dated February 13, 2024 and gives no price figures. It points readers to the billing documentation instead. https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-in-public-preview - SP30 was the only tier during public preview. https://www.m — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#phase-0-public-preview-feb-2024` - - https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-in-public-preview - https://www.mongodb.com/company/blog/product-release-announcements/atlas-stream-processing-now-generally-available - https://www.mongodb.com/community/forums/t/atlas-stream-processing-is-now-generally-available/278813 - https://www.mongodb.com/blog/post/atlas-stream-processing-cost-effective-way-integrate-kafka-mongodb - https://www.mongodb.com/company/blog/product-release-announcements/workspaces-and-new-tiers-for-atlas-stream-processing - https://www.mongodb.com/docs/atlas/atl — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/history.md#sources` - - https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md - https://www.mongodb.com/pricing - https://www.mongodb.com/docs/atlas/atlas-stream-processing/architecture/ - https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ - https://www.mongodb.com/docs/atlas/atlas-stream-processing/autoscaling/ - https://www.mongodb.com/docs/manual/reference/method/sp.processor.modify/ - https://www.mongodb.com/company/blog/product-release-announcements/workspaces-and-new-tiers-for-atlas-stream-processing - htt — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/mechanism.md#sources` - Researched 2026-10-02. Parent: MongoDB Atlas Stream Processing (ASP). — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md` - Method: official docs, the pricing page, the changelog, blogs and the SLA were fetched with WebFetch and WebSearch. Firecrawl, curl and Bash were denied in this non-interactive session. As a result, no historical page snapshots were available, and the legacy per-worker rates could not be retrieved. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#scope` - The gate is met on host count. There are 4 hosts: mongodb.com (primary: docs, pricing, changelog, blog, SLA), amnic.com, checkthat.ai and delbridge.solutions. Substantively, however, every load-bearing claim rests on MongoDB's own pages, and the independent sources are secondary summaries. Two of the three third-party sources conflict with official docs (gaps 2 and 3). No independent primary source, such as an audited price study, was found. — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#quality-gate` - - https://www.mongodb.com/docs/atlas/billing/stream-processing-costs/ - https://www.mongodb.com/pricing - https://www.mongodb.com/docs/atlas/atlas-stream-processing/changelog/ - https://www.mongodb.com/company/blog/product-release-announcements/workspaces-and-new-tiers-for-atlas-stream-processing - https://www.mongodb.com/blog/post/atlas-stream-processing-cost-effective-way-integrate-kafka-mongodb - https://www.mongodb.com/blog/post/atlas-stream-processing-now-generally-available - https://www.mongodb.com/docs/atlas/atlas-stream-processing/architecture/ - https://www.mongodb.com/docs/atlas/atl — source: `~/.global-ai-hub/research-tests/mongodb-full-frontier-20261002/full-frontier-run/asp-pricing-model-c67aa09ba9/reports/practice.md#sources` ## Related concepts - Pricing — is a part of ASP Pricing Model - ASP — is a part of ASP Pricing Model - Model — is a part of ASP Pricing Model