What Is It?
MongoDB is the IONOS CLOUD Database as a Service (DBaaS) offering for MongoDB, a fully managed hosting service for the open-source, document-based NoSQL database. IONOS CLOUD handles provisioning, backups, patching, and node monitoring, while you connect with standard MongoDB tools (mongosh, MongoDB Compass, or an application driver) and the native MongoDB Query Language. The service comes in three editions: Playground for testing, Business for production workloads on a single replica set, and Enterprise for dedicated cores, larger resources, sharding, and the BI Connector.
Quick Facts
| Aspect | Details |
|---|---|
| Type | Managed NoSQL document database (DBaaS) |
| Editions | Playground, Business, Enterprise |
| Versions | MongoDB 6.0 and 7.0 (all editions) |
| Hosting | Playground on a single small Cube instance; Business on Cubes; Enterprise on Dedicated Core Servers |
| Deployment types | Replica set (all editions); sharded cluster (Enterprise only) |
| Enterprise storage types | HDD, SSD Standard, SSD Premium |
| Shards (Enterprise) | Minimum 2; up to 32 when created in the DCD, up to 100 through the API |
| Sharding config servers | 3 extra config-server instances (2 cores, 4 GB RAM, 40 GB storage each) created automatically |
| Backup retention | 7 days (Business and Enterprise) |
| Point-in-time recovery | Enterprise only; 1 to 24 hours in the past (default 24 hours) |
| Offsite backup locations | Enterprise only: de, eu-south-2, eu-central-3 |
| Log retention | 30 days |
| Maintenance window | 4 hours, on a weekly day and start time (UTC) you choose |
| Scaling | Customer-triggered (manual) |
| Max users per cluster | 100 |
| BI Connector port | 27015 (Enterprise only) |
| Connection string | mongodb+srv://m-<id>.mongodb.<region>.ionos.com |
| Compliance | GDPR, ISO-27001, SOC 2 |
| Default contract quota | 16 CPU cores, 32 GB RAM, 5 database clusters, 1500 GB disk space (increase through IONOS CLOUD Support) |
Resources Based on MongoDB Editions
| Resources | MongoDB Playground | MongoDB Business | MongoDB Enterprise |
|---|---|---|---|
| Storage | 50 GB | 50 - 1280 GB | 50 - 4000 GB |
| RAM | 2 GB | 2 - 128 GB | 2 - 230 GB |
| CPU | 1 vCPU | 1 - 32 vCPU | 1 - 31 Core |
| Instances | 1 | 1, 3 | 1, 3, 5, 7 |
CPU and RAM limits apply per instance. The Enterprise storage maximum (4 TB) applies per cluster.
Business Edition Templates
| Business Edition | vCPU | RAM | Storage |
|---|---|---|---|
| XS | 1 | 2 GB | 50 GB |
| S | 2 | 4 GB | 80 GB |
| M | 4 | 8 GB | 160 GB |
| L | 6 | 16 GB | 320 GB |
| XL | 8 | 32 GB | 640 GB |
| XXL | 16 | 64 GB | 960 GB |
| 4XL | 32 | 128 GB | 1280 GB |
| 4XL_S | 32 | 128 GB | 2000 GB |
Choosing Your Edition
| If you need | Choose |
|---|---|
| Free sandbox for development | MongoDB Playground |
| Production workloads up to 128 GB RAM and 1.28 TB storage | MongoDB Business |
| Sharding, dedicated cores, up to 230 GB RAM, or up to 4 TB storage | MongoDB Enterprise |
Formula for Maximum Connections
The platform enforces connection limits from the instance RAM: (RAM in GB − 2 GB system reserve) / 2 = max connections (in thousands). A 230 GB instance supports about 114,000 connections.
| Cluster RAM | Calculation | Maximum Connections | Notes |
|---|---|---|---|
| 2 GB | (2 − 2)/2 = 0 | ≈ 500 | Sandbox cluster to test the product. |
| 4 GB | (4 − 2)/2 = 1 | 1000 | Small development environment cluster. |
| 6 GB | (6 − 2)/2 = 2 | 2000 | Staging cluster. |
| 8 GB | (8 − 2)/2 = 3 | 3000 | Small production cluster. |
| 12 GB | (12 − 2)/2 = 5 | 5000 | Medium production cluster. |
| 16 GB | (16 − 2)/2 = 7 | 7000 | Medium cluster with a higher demand for the number of connections. |
| 24 GB | (24 − 2)/2 = 11 | 11000 | Large production. |
| 32 GB | (32 − 2)/2 = 15 | 15000 | High concurrency setup. |
| 48 GB | (48 − 2)/2 = 23 | 23000 | High concurrency setup. |
| 64 GB | (64 − 2)/2 = 31 | 31000 | High concurrency setup. |
Enterprise Volume Performance
| Volume size | Read IOPS | Write IOPS | Note |
|---|---|---|---|
| 100 GB | 7,500 | 5,000 | Low performance |
| 200 GB | 15,000 | 10,000 | |
| 400 GB | 30,000 | 20,000 | |
| 600 GB | 45,000 | 30,000 | Platform threshold reached (maximum) |
| 1000 GB | 45,000 | 30,000 | Adding more GB only adds capacity, not speed |
A single volume cannot exceed 600 MB/s sequential throughput.
Locations
| Data Center | Region | Playground | Business | Enterprise |
|---|---|---|---|---|
| Berlin, Germany | de/txl | Yes | Yes | Yes |
| Frankfurt am Main, Germany | de/fra | Yes | Yes | Yes |
| Frankfurt am Main, Germany | de/fra/2 | Yes | ||
| Paris, France | fr/par | Yes | Yes | Yes |
| Logroño, Spain | es/vit | Yes | Yes | Yes |
| London, United Kingdom | gb/lhr | Yes | Yes | Yes |
| Worcester, United Kingdom | gb/bhx | Yes | Yes | Yes |
| Las Vegas, USA | us-las | Yes | ||
| Lenexa, USA | us-mci | Yes | Yes | Yes |
| Newark, USA | us-ewr | Yes | Yes | Yes |
Service Level Agreement
| Setup | Monthly uptime SLA |
|---|---|
| Business or Enterprise, high-availability setup with at least 3 nodes | 99.95% |
| Business or Enterprise, fewer than 3 nodes | 99.9% |
| Playground | Excluded from any SLA |
What You Can Do
Run Replica Sets for High Availability
A replica set has a primary node, where data is written, and secondary nodes, where data is copied. If the primary fails, a secondary takes over. Business and Enterprise run multi-instance clusters across different physical hosts with automatic data replication and failure handling.
Scale Horizontally with Sharding (Enterprise)
A sharded cluster splits your data across multiple replica sets, each with its own primary, so writes and IOPS are spread across shards. Consider sharding when your working set no longer fits in the RAM of one instance, when peaks push a single node's IOPS too hard, or when you need to scale write throughput with a good shard key. Only users with the enableSharding role can shard a collection.
Scale Your Cluster
- Business: Change the template (scale up or down) with a PATCH request, and switch the instance count between 1 and 3.
- Enterprise: Increase the instance count to 3, 5, or 7 in the DCD and increase the shard count through the API; neither can be decreased. To change CPU, RAM, or storage, contact IONOS CLOUD Support.
Back Up and Restore
Business and Enterprise take snapshots when a cluster is created, after a restore, every 24 hours (base snapshot), and every Sunday (full snapshot). Snapshots are stored in an IONOS Cloud Object Storage bucket in the same region as the database; regions without it back up to eu-central-2. Restores run in place into the same cluster, from a snapshot ID or (Enterprise) from an exact Oplog timestamp. Enterprise can also store backups offsite in another location, set at cluster creation.
Note: Only one restore job can run at a time, and the cluster is BUSY and must not receive connections during a restore.
Manage Users and Roles
Create users in the DCD or through the IONOS CLOUD API with a username, password, target database, and roles. All users are created in the admin database. You can assign only these built-in roles: read, readWrite, readAnyDatabase, readWriteAnyDatabase, dbAdmin, dbAdminAnyDatabase, clusterMonitor.
Note: You cannot create or modify users from within MongoDB itself.
Query with SQL Tools (Enterprise)
The MongoDB Connector for BI lets you query MongoDB data with SQL using tools such as Tableau, Power BI, and Excel. Enable it per cluster at creation or through the API.
Secure Connections
All instance-to-instance and client-to-cluster communication uses TLS with Let's Encrypt certificates. Business data sits on directly attached NVMe devices encrypted at rest; Enterprise data volumes are encrypted at rest. Clusters attach to a private LAN in your data center, and you can reach them from a VM or from Managed Kubernetes node pools connected to the same LAN.
Upgrade and Maintain
IONOS CLOUD keeps the MongoDB patch version up to date within the current major version during your maintenance window. You trigger major version upgrades yourself, which causes a brief cluster downtime.
Access Logs
Every instance collects MongoD logs and ships them to central storage. Retrieve them through the API with the cluster ID.
You monitor cluster health yourself; IONOS CLOUD provides the monitoring data.
Migrate Data
Move databases between clusters with mongodump and mongorestore. Both clusters must run the same major version, and users and roles must be recreated through the API because mongorestore cannot restore them.
Best For
| Scenario | Why It Fits |
|---|---|
| Testing and prototyping | Playground offers a free sandbox to explore MongoDB and test code |
| Production apps with flexible schemas | Business gives a managed replica set with backups and fixed templates |
| Workloads beyond one instance's RAM, IOPS, or connections | Enterprise sharding distributes data, writes, and connections |
| Analytics on document data | Enterprise BI Connector exposes data to SQL-based BI tools |
| Recovery to an exact moment | Enterprise point-in-time recovery restores to an Oplog timestamp |
| Infrastructure as code | Clusters and users are manageable through Terraform and Ansible |
Consider Alternatives If
| If You Need... | Consider | Why |
|---|---|---|
| A relational database with MySQL compatibility | DBaaS for MariaDB | Open-source engine with MySQL compatibility |
| A relational database or a vector store with pgvector | DBaaS for PostgreSQL | PostgreSQL with the pgvector extension is the recommended self-managed vector store |
| Very fast in-memory data retrieval | DBaaS for In-Memory DB | In-memory data structure store for quick retrieval |
Key Considerations
Billing & Costs
Prices below are from the IONOS CLOUD (EUR) price list; other contract entities bill in their own currency.
- Playground: The first instance is free of charge; each further instance costs 0,035 € per hour.
- Business: Billed per instance per hour by template:
| Template | Price per hour |
|---|---|
| XS | 0,035 € |
| S | 0,070 € |
| M | 0,140 € |
| L | 0,280 € |
| XL | 0,560 € |
| XXL | 1,130 € |
| 4XL | 2,270 € |
| 4XL_S | 2,470 € |
- Enterprise: 0,06 € per core per hour and 0,0353 € per GB RAM per hour; storage per GB per 30 days costs 0,15 € (SSD Premium), 0,07 € (SSD), or 0,04 € (HDD). Total billed resources are the per-instance values multiplied by the number of instances and the number of shards. Sharding config servers are not billed.
- Additional costs: Backup storage costs 0,007 € per GB per 30 days. The estimated price in the DCD excludes traffic and backup.
Limitations
- Scaling is never automatic: you monitor cluster health and trigger scaling yourself.
- Single-instance clusters cannot change instance size or storage size; create a new cluster instead.
- Moving from Business to Enterprise is a manual platform migration (new cluster plus data move), not a resize. Downgrading an edition is not supported.
- Enterprise instance counts and shard counts cannot be decreased.
- MongoDB versions cannot be downgraded, and upgrades go one major version at a time. After an upgrade, restores work only from snapshots of the same or the previous major version.
- Restores use snapshots created with the same or an older MongoDB patch version, and only from the same cluster.
- Deleting a cluster immediately deletes all of its backups.
- Playground: single instance only, no backups, no sharding, and clusters are deleted automatically 30 days after creation.
- Business: no sharding and no BI Connector.
- Offsite backup location can be set only at cluster creation.
- Total CPU and RAM depend on your contract quota (see Quick Facts).
- The cluster subnet must be a /24. Choose cluster IPs from x.x.x.3 to x.x.x.10 in the /24, a range IONOS Cloud DHCP never assigns. These ranges cannot be used: 172.16.0.0/12, 192.168.230.0/24, 10.208.0.0/12.
- There is no managed connection pooler; reuse connections and keep client pools within the enforced limit (for example 10 to 20 connections per application process).
- IONOS CLOUD does not give full access to the cluster: only the listed roles are assignable, AnyDatabase roles are granted only on the admin database, and read, readWrite, and dbAdmin cannot be granted on the config and local databases.
- Log collection settings cannot be changed.
- Sizing guidance: WiredTiger uses the larger of 50% of (RAM - 1 GB) or 256 MB for its internal cache. Size the Oplog to hold at least 24 hours of history; it can be resized later without downtime. For SSD Standard and SSD Premium, use at least 100 GB for optimal performance.
Management Options
- Data Center Designer (DCD): Menu > Databases > MongoDB (requires contract owner or administrator rights, or the "Access and manage DBaaS" privilege)
- MongoDB v1 API at
https://api.ionos.com/databases/mongodb - Terraform:
ionoscloud_mongo_clusterandionoscloud_mongo_user - Ansible