.png)
Why this matters: MongoDB Atlas usage is billed on its own schedule, separate from any cloud provider invoice — cluster tiers, storage, data transfer all accrue independently of whatever's running in AWS, Azure, or GCP. Without connecting it here, Atlas spend either lives in a spreadsheet someone updates manually, or doesn't get reviewed until the invoice lands. Connecting it means Atlas costs show up in Mavvrik's SaaS dashboards, with the same allocation and reporting tools available for your cloud spend.
This shows up differently depending on your role:
-
FinOps managers use this to catch Atlas cost growth (cluster upsizing, storage growth) before it's a surprise line item.
-
Data/platform teams do the actual onboarding — creating the service account and scoping its access correctly.
-
Finance leaders use this for chargeback when Atlas clusters are shared across multiple teams or projects.
Step 1: Log in to MongoDB Atlas console and capture the Organization ID
-
Log in to the MongoDB console as organization owner (https://account.mongodb.com/account/login )
-
Click on the settings icon
-
Capture the Organization ID
Step 2: Create a Service Account
-
Create a service account
-
Click on Access Manager
-
Click on Add new > Click on Service Account
-
Fill in the details and select roles as "
Organization Read Only" and "Organization Billing Viewer."
We recommend selecting Client Secret Expiration as 365 days
-
Click on create
-
Capture the Client ID and Client Secret, which are used on Mavvrik for onboarding.
Step 3: Integrate into Mavvrik portal
-
Go to Mavvrik portal and click on admin and then SaaS
-
Click on +account and then select MongoDB
-
Enter the details captured above and click connect
-
Organization id
-
Client id
-
Client Secret
-
