MongoDB Atlas through Squiid

What MongoDB Atlas is

MongoDB Atlas is the hosted version of MongoDB. Data is stored as documents rather than rows, which suits records whose shape changes as a product evolves, and the aggregation pipeline handles grouping, joins and transformations server side. Atlas adds Search for full-text queries and Vector Search for embeddings, so a retrieval feature can live in the same cluster as the application data instead of in a separate vector database. Change streams push document updates to your application, and time series collections handle metrics and event data without a separate store.

That combination is the reason it turns up in AI-coded apps. If your documents already live in MongoDB, adding an embedding field and a vector index is a smaller change than introducing a new service, syncing data into it and keeping the two consistent. Flexible schemas also match the way agents iterate: a generated feature that adds three fields does not require a migration before it can be tested. Atlas also runs on all three major clouds, which matters when a customer requires data to stay in a specific provider and region.

Why connect it through Squiid

MongoDB Atlas is on the Squiid roadmap. When it lands, Squiid will provision the cluster, hold the connection string and the API keys, and expose data and admin access through https://api.squiid.io/v1/mongodb-atlas/... with Authorization: Bearer $SQUIID_API_KEY, with drivers working by base URL swap (gateway convention). Cluster cost and metered usage will pass through at MongoDB's listed price on your single Squiid invoice. Atlas connection strings contain a username and password inline, which is exactly the kind of credential that should not be sitting in a repository an agent can read.

• One account, one key, one bill, one dashboard. MongoDB Atlas sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the MongoDB Atlas credentials. Your code carries SQUIID_API_KEY, so MONGODB_URI, MONGODB_DB, ATLAS_PUBLIC_KEY, ATLAS_PRIVATE_KEY never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what MongoDB Atlas costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Atlas cluster with credentials held by Squiid
• Document storage with the aggregation pipeline
• Atlas Search and Vector Search in the same cluster
• Cluster and usage cost on one invoice
• MongoDB list pricing, no markup

How to connect MongoDB Atlas

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces MONGODB_URI, MONGODB_DB, ATLAS_PUBLIC_KEY, ATLAS_PRIVATE_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/mongodb-atlas/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

MongoDB Atlas charges per hour for cluster size plus storage, backup and data transfer, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of MongoDB Atlas usage, with no markup and no per-request margin.

MongoDB Atlas has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so MongoDB Atlas usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: take a mongodump of the cluster and restore it into a cluster in your own Atlas project. Squiid never owns your code, your schema or your domain, and the gateway speaks MongoDB Atlas's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

MongoDB Atlas through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on MongoDB Atlas usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.