MongoDB Atlas Platform Services
Atlas Platform Services is the data services on top of Atlas — Stream Processing (real-time, GA 2024), Data Federation (query Atlas + S3 in one query), Charts & Edge Server. Stream, federate and visualise — on the same Atlas data, without separate systems.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
The MongoDB platform family
This page covers Atlas Platform Services — streaming, federation & data services. The rest of the MongoDB platform:
Quick facts
30-second orientation- Product
- Atlas Platform Services — data services on Atlas
- Vendor
- MongoDB (founded 2007 · New York)
- The category
- Streaming, federation & data services
- What it does
- Stream, federate, visualise — on your Atlas data
- Stream Processing
- GA 2024 — real-time streams via aggregation
- Data Federation
- Query across Atlas + S3/object storage
- Also
- Atlas Charts (viz) · Edge Server (IoT/edge)
- Note
- Realm/Device Sync deprecated (EOL Sep 2025)
- Vs
- Confluent/Kafka+Flink, Kinesis, Trino, Athena, Tableau/Power BI
- In India via
- TechBag — scoping, honest compare, GST
Understand streaming, federation & data services before you buy
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What is Atlas Platform Services?
The data services on top of Atlas — Stream Processing (real-time, GA 2024), Data Federation (query Atlas + S3 in one query), Charts (dashboards) and Edge Server (edge/IoT) — all on the same Atlas data.
Separate systems vs Atlas Platform Services (on one data) — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | Unprotected / signature email | Atlas Platform Services (MongoDB) |
|---|---|---|
| Streaming | Separate Kafka+Flink stack | Stream Processing (aggregation) |
| Skills | New streaming language | The aggregation framework you know |
| Cross-source query | ETL into one place first | Federate Atlas + S3 in one query |
| Cold data | Copied or unqueryable | Online Archive, still queryable |
| Visualisation | Export to a BI tool | Atlas Charts on live data |
| Edge / IoT | Deprecated Device Sync | Edge Server (the newer story) |
| Systems to run | Many, to sync | One platform, same data |
| Best fit | (varies) | Teams on Atlas wanting fewer systems |
Atlas Platform Services is the set of data services on top of Atlas — Stream Processing (real-time streams via the aggregation framework, GA 2024), Data Federation (query across Atlas and S3 in one query), Charts (dashboards) and Edge Server (edge/IoT) — on the same Atlas data. Honest: each competes with a deeper specialist (Confluent/Kafka+Flink or Kinesis for streaming, Trino/Athena for federation, Tableau/Power BI for BI), and Realm/Device Sync mobile sync is deprecated (EOL Sep 2025). TechBag scopes it & adds GST.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Atlas Stream Processing
Process Kafka topics or Atlas change streams with the aggregation framework — transform, filter and react, then write results to collections. GA in 2024.
Data Federation
Run one MongoDB query across Atlas clusters and object storage such as Amazon S3, combining hot and archived data without moving or copying it.
Atlas Charts
Build dashboards and embed charts directly on your Atlas data — no export, no separate BI connector, no sync to maintain.
Edge Server
Extends MongoDB to edge and IoT with a local data tier that syncs with Atlas. Realm/Device Sync mobile sync is deprecated.
One Platform, Same Data
Stream Processing, Data Federation, Charts and Edge Server all run on the same Atlas data, with no separate streaming, query or BI system to sync.
One platform around the data — stream processing, federated queries, charts and edge sync against the same documents.
Twelve capabilities. Stream, federate, visualise.
Atlas Platform Services lets teams stream, federate and visualise on the same data — the data services of the MongoDB portfolio.
Real-Time Stream Processing
Continuously process event streams from Kafka or Atlas change streams — transform, filter, window and react. GA 2024.
The Aggregation Framework
Write stream processing in the MongoDB aggregation framework your team already knows — no new streaming language.
Kafka & Change-Stream Sources
Ingest from Apache Kafka topics or Atlas change streams and materialise results back into collections.
Continuous Processing
Long-running processors handle streams continuously — windowing, joins and transformations, materialised for downstream use.
Cross-Source Federated Query
Query Atlas clusters and object storage (Amazon S3) in one MongoDB query — no ETL, no copying data in first.
Query Object Storage In Place
Analyse cold, archived or bulk data in S3-style storage directly, combined with hot Atlas data without moving either.
Online Archive & Data Tiering
Tier ageing data out of hot clusters to lower-cost storage while keeping it queryable via federation.
Data Lake Pipelines & Export
Land Atlas data in object storage on a schedule for analytics and archival, bridging operational and analytical stores.
Charts & Dashboards
Build interactive dashboards on your Atlas data with Atlas Charts — no export, no separate BI connector, no sync pipeline.
Embedded & Shared Charts
Embed charts into your own apps and share dashboards — put operational insight in front of users where they work. Insight in your app. Share or embed.
Edge Server (IoT / Edge)
Extends MongoDB to edge and IoT with a local tier that syncs to Atlas. Realm/Device Sync is deprecated, EOL Sept 2025.
All-In-One — But Specialists Go Deeper
Fewer systems for Atlas teams, but specialists go deeper: Confluent or Kinesis for streams, Trino/Athena for query, Tableau/Power BI.
Watch Atlas Platform Services in action
The overview, getting started, and the core workflows.
Atlas Stream Processing — Demo
Real-time streams with the aggregation framework.
Introducing Atlas Stream Processing
Process data in motion, on Atlas.
MongoDB .local — Keynote
The platform vision, including the data services.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Data is everywhere. Answers, in one place.
Here’s what genuinely sets Atlas Platform Services apart (and where a specialist fits better).
Stream, federate and visualise — on the same data, no separate systems
Platform Services lets you stream, federate and visualise on the same Atlas data: Stream Processing for real-time events, Data Federation across Atlas and S3, Atlas Charts for dashboards and Edge Server for IoT. That replaces a streaming engine, a query layer and a BI tool you would otherwise sync.
Stream processing with the aggregation framework your team already knows
Atlas Stream Processing (GA in 2024) processes Kafka topics or change streams with the aggregation framework your developers know — windowing, joins and transforms, written back to collections. No new engine or language. For high-throughput streaming, Confluent/Kafka+Flink and Kinesis go deeper.
Federated query — combine hot operational data and cold archive in one query
Data Federation runs one MongoDB query across Atlas clusters and object storage like Amazon S3, with no ETL. Online Archive tiers ageing data to cheaper storage while keeping it queryable. For large-scale federated analytics, Trino/Presto and Amazon Athena go deeper.
Visualisation and the edge — dashboards in place, data where connectivity is spotty
Atlas Charts builds and embeds dashboards on live Atlas data with no export or BI sync, and Edge Server gives edge and IoT sites a local tier that syncs to Atlas. The older Realm Device Sync mobile product is deprecated (end-of-life September 2025). For rich BI, Tableau/Power BI go deeper.
From the category leader — and TechBag adds honest comparison and India support
MongoDB (NASDAQ: MDB) reports ~$2.5B revenue in FY2026, with Atlas ~75% of it, and runs one of its largest hubs in Gurugram, plus Bengaluru. Each service competes with a specialist, so TechBag scopes what you need, compares Confluent, Kinesis, Trino, Athena, Tableau and Power BI, and adds INR/GST (18%).
The honest scope
Platform Services suits teams already on Atlas that want fewer systems. Each piece has a deeper specialist: Confluent/Kafka + Flink or Kinesis for streaming, Trino/Presto or Athena for federated query, Tableau or Power BI for BI. Realm Device Sync is deprecated (EOL September 2025).
The numbers behind the platform
What your Atlas Platform Services journey looks like
Scoping (& which services)
Your workload — streams, cross-source query, dashboards, edge — and whether you’re already on Atlas, the sweet spot.
Turn on the services you need
Enable Stream Processing, Data Federation (Atlas + S3 in one query), Atlas Charts and/or Edge Server, all on your Atlas data.
Stream, federate, visualise
Process Kafka or change streams, query hot and cold data with no ETL, tier data with Online Archive, and build dashboards in place.
Right-size cost & compare
These bill as Atlas usage. TechBag scopes what you need and flags where Confluent, Kinesis, Trino, Athena or Power BI is worth it.
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“We already ran on Atlas, so processing streams with the aggregation framework, no Kafka+Flink stack to run, simplified a lot.”
“Data Federation let us query hot Atlas data and cold S3 archive in one query, no ETL. Tiering cut cost without losing access.”
“Atlas Charts gave us dashboards on our operational data, with no export or BI connector. For internal insight it was enough.”
“Edge Server suits our patchy IoT sites. TechBag confirmed the old Realm mobile sync was deprecated, so we planned on Edge Server.”
“For our highest-throughput streaming we still use Confluent. TechBag was candid: Atlas Stream Processing is convenient, not deepest.”
“MongoDB’s big Gurugram hub gave us confidence, and TechBag scoped the services we needed against the specialists and added INR/GST.”
“Reusing aggregation pipelines for streams collapsed the learning curve. Our MongoDB developers were productive fast, no hiring needed.”
“Billed as Atlas usage, these add up. TechBag scoped exactly what we needed, flagged where a specialist was worth it, and added INR/GST.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and review-site grids score satisfaction, not fit for your estate. So here’s TechBag’s synthesis of the data-services market — tap any vendor to see why it sits where it does.
TechBag Data & Observability Grid
Execution strength vs product vision — the classic market map, minus the paywall.
Data services on Atlas (all-in-one). This page.
Specialist Depth × Data Locality
The grid nobody publishes — specialist-tool depth vs convenience & same-data locality.
Convenience + same-data locality.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Atlas Platform Services vs the specialists
Confluent/Kafka+Flink, Kinesis, Trino, Athena and Tableau/Power BI — honest lanes; the edge is data locality & simplicity for teams already on Atlas, not out-depthing each specialist. Serious streaming? Confluent. Large federation? Trino/Athena. Rich BI? Tableau/Power BI. We say so.
| Dimension | MongoDB Atlas | Confluent/Kafka+Flink | AWS Kinesis | Trino/Presto | Athena | Tableau/Power BI |
|---|---|---|---|---|---|---|
| Position | Data services on Atlas (all-in-one) | Deep streaming platform | AWS-native streaming | Federated query engine | Serverless query on S3 (AWS) | Enterprise BI / visualisation |
| Streaming depth | Aggregation framework (GA 2024) | Deepest (Kafka + Flink) | Solid, AWS-native | Not streaming | Not streaming | Not streaming |
| Federated / cross-source query | Atlas + object storage | Not its job | Not its job | Deep, many sources | Serverless on S3 | Not its job |
| Visualisation / BI | Atlas Charts (on Atlas data) | Not its job | Not its job | Not its job | Not its job | Deepest enterprise BI |
| Convenience for Atlas teams | Same data, same skills, one platform | Separate stack to run | Separate AWS service | Separate engine to run | AWS-tied | Separate BI tool + sync |
| Best fit | Teams on Atlas wanting fewer systems | Serious, high-throughput streaming | AWS-native streaming | Large-scale federated analytics | Serverless query on S3 (AWS) | Rich enterprise BI |
Which data, analytics & observability approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Atlas Platform Services if…
- You’re already on Atlas and want to STREAM, FEDERATE and VISUALISE on the same data — without separate systems
- You want real-time stream processing in the MongoDB AGGREGATION FRAMEWORK your team already knows (GA 2024)
- You want to query across Atlas and S3-style storage in ONE query (Data Federation) and dashboards in place (Charts)
- You want fewer systems and less glue code — with TechBag scoping which services you need & adding GST
Confluent / Kafka + Flink if…
- You need SERIOUS, high-throughput, complex stream processing — the deepest streaming platform
AWS Kinesis if…
- You want AWS-NATIVE streaming, tightly integrated with the rest of your AWS stack
Trino/Presto or Athena if…
- You need large-scale FEDERATED analytics across many sources (Trino/Presto), or serverless query on S3 (Athena)
Tableau / Power BI if…
- You need rich, enterprise BUSINESS INTELLIGENCE and visualisation beyond in-place operational dashboards
What could this save you?
Drag the sliders (data services needed; hour cost as loaded rate). Estimates contrast running separate streaming, federated-query and BI systems (each provisioned, secured, paid for and kept in sync) vs Atlas Platform Services (stream, federate and visualise on the same Atlas data — fewer systems, less glue code) — the wins are systems eliminated, glue-code avoided and ops time saved. Illustrative — remember each service competes with a deeper specialist, so TechBag models the full picture for your workload.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Three ways to consume it
Atlas Platform Services bill as Atlas usage — Stream Processing, Data Federation, Charts and Edge Server are metered by use on top of your Atlas clusters. Buy direct or via the AWS/Azure/GCP marketplace to draw down committed cloud spend. Honest: each competes with a deeper specialist, so scope what you need. TechBag scopes it and handles INR/GST (18%) — quote current figures.
Atlas Platform Services (usage-based)
Best for teams already on Atlas
- Stream Processing — real-time streams via the aggregation framework (GA 2024)
- Data Federation — query across Atlas & S3 in one query, no ETL
- Charts (dashboards) & Edge Server (edge/IoT) on the same data
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
+ scoping & local support
Best value with TechBag
- Scoping + honest Confluent/Kinesis, Trino/Athena, Tableau/Power BI comparison
- Deprecation guidance (Realm/Device Sync EOL Sep 2025 — Edge Server is newer); Gurugram R&D
- TechBag adds INR/GST (18%) invoicing & local support
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your requirements and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Already standardised on Atlas? These services run on your Atlas data, which is where they cut systems and glue code.
Need real-time streams? Stream Processing (GA 2024) uses aggregation; at heavy throughput, Confluent or Kinesis?
Need to query across Atlas and S3 in one query, no ETL? For large-scale federation, do Trino/Presto or Athena fit better?
Are in-place Atlas Charts dashboards enough, or do you need rich enterprise BI from Tableau or Power BI?
Need the edge? Edge Server is the newer route; Realm/Device Sync is deprecated (EOL Sept 2025), so don’t plan around it.
Each service competes with a deeper specialist — the trade is convenience/locality for depth. TechBag scopes honestly per need.
Does local depth matter? MongoDB runs one of its largest hubs in Gurugram, plus Bengaluru; TechBag supports it locally.
These bill as Atlas usage — TechBag scopes what you need, handles marketplace draw-down, and adds INR/GST (18%) invoicing.
Questions buyers ask
Ready to stream, federate and visualise on Atlas?
Scope Atlas Platform Services (the data services on Atlas — Stream Processing, Data Federation, Charts and Edge Server — stream, federate and visualise on the same data) — and let a TechBag advisor scope which services you need, compare honestly vs Confluent/Kinesis, Trino/Athena and Tableau/Power BI, flag the Realm/Device Sync deprecation, and add INR/GST and local support.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.