Your MongoDB as a replica set: installed, backed up, monitored.

We run your document database as a three-node replica set, back it up and monitor it. As you grow, we plan sharding and index strategy together.

Resources scale from the panel; prices are in the cmdbcnn.com panel.

Replica set · rs03 / 3 nodes
Pmg-1
PRIMARY
oplog →
Smg-2
SECONDARY
oplog →
Smg-3
SECONDARY
Snapshot + oplog PITR Automatic election
connectionmongodb+srv://app:•••@mg-prod.cmdbcnn.com/app?tls=true
PLANS

The right size for MongoDB.

Managed MongoDB replica set: setup, backups, monitoring and scaling.

PlanvCPU / nodeRAM / nodeStorageNodesBackup retention
MG-DEV2 vCPU4 GB40 GB17 daysChoose in the panel ↗
MG-M4 vCPU16 GB250 GB330 daysChoose in the panel ↗
MG-L8 vCPU32 GB600 GB330 daysChoose in the panel ↗

All production plans are 3-node replica sets; a single node is available for development. Prices in the panel.

WHY MANAGED MONGODB?

Beyond setup, we run it.

Replica set as standard

Three nodes with automatic election; if the primary goes down, your application carries on without noticing.

Point-in-time recovery via oplog

Scheduled snapshots plus oplog; roll back to before an accidental delete.

WiredTiger tuning

Cache size, compression and journal settings matched to the workload.

Index & schema advisory

Index suggestions from profiler data; document design review.

Sharding plan

When data outgrows a single cluster, the shard key and distribution are planned together.

SCRAM + TLS + IP restriction

Authentication, encrypted connections and allow-list from the panel.

VERSIONS

Current version, planned upgrades.

MongoDB 8.0MongoDB 7.0MongoDB 6.0
FEATURES

What you need, ready.

3-node replica setShardingChange streamsCompass accessPITR via oplogSCRAM + TLS
MIGRATION

Let’s move your existing MongoDB without downtime.

  1. 01

    Discovery

    Version, collection sizes, indexes and read/write profile are mapped out.

  2. 02

    Transfer

    Initial copy with mongodump/mongorestore, or zero-downtime sync by adding new nodes to your existing replica set.

  3. 03

    Cutover

    The primary moves to the new cluster and the connection string is switched; old nodes are kept for 7 days.

WHAT DO WE MANAGE?

What we take on for you.

WHO IS IT FOR?

Typical use cases.

Mobile & web applications

For fast-moving products with a flexible schema.

IoT & event data

Streams that demand high write throughput.

Content & catalogs

For rich document structures.

QUESTIONS ON YOUR MIND

Before we start.

Can I get a single node?+

Yes, for development environments; for production we recommend a replica set.

Can you migrate my existing data?+

We migrate with zero downtime using mongodump/mongorestore or by adding replicas.

Which versions?+

The currently supported major versions; upgrades are planned gradually.

MANAGED DATABASES

Other engines.

All infrastructure services
NEXT STEP

Tell us about your business.
Let’s build it together.

Let’s talk about your project