Managed Add-ons

Deploy and manage fully-managed database and service instances with automated backups, scheduling, and monitoring.

Supported Add-on Types

Type	Versions	Cluster Support	Use Cases	Features
MongoDB	8.2, 8.0, 7.0	Yes	Document databases, JSON storage	Auto-backups, replica sets
PostgreSQL	18, 17.6, 16.10	No	Relational data, analytics, ACID compliance	Extensions, backups, full-text search
MySQL	8.4, 8.0, 5.7	No	Relational data, web applications, OLTP	Backups, InnoDB engine
Greenplum	7.1.0, 6.27.1	Yes	MPP data warehouse, large-scale analytics	Distributed queries, PostgreSQL-compatible, MADlib in-database ML
Milvus	2.6.3, 2.5.19, 2.4.11	Yes	Vector databases, AI embeddings, semantic search	Similarity search, indexing
Redis	8, 7.4, 7.2	No	Caching, sessions, real-time data	Persistence, pub/sub, data structures
Neo4j	2025.08, 2025.07, 5.26	No	Graph databases, relationships, networks	Cypher queries, graph algorithms
RabbitMQ	4.1.4, 4.1.0, 4.0	No	Message queuing, async tasks	AMQP messaging, routing
SurrealDB	2.1, 2.0, 1.5	No	Multi-model database, modern applications	Document, graph, and relational in one

Cluster Deployments

MongoDB, Milvus, and Greenplum support cluster mode for high availability and horizontal scaling. Select Cluster (High Availability) as the deployment mode during add-on creation to configure multi-node deployments.

How to Create an Add-on

Step 1: Navigate

• Go to Add-ons in main navigation
• Click Create Add-on to open the Create New Add-on page

Step 2: Basic Information

• Add-on Label (required): a unique label to identify this add-on (e.g., "main-database", "cache-server")
• Type: MongoDB, PostgreSQL, MySQL, Greenplum, Milvus, Redis, Neo4j, RabbitMQ, or SurrealDB
• Version: pick from the versions offered for the selected type
• Description (optional): purpose and notes

Step 3: Deployment Mode (MongoDB, Milvus, Greenplum only)

• Single Node: single node deployment for development and testing
• Cluster (High Availability): cluster deployment with multiple nodes for high availability and scalability
  • Data Nodes: 3-10
  • Replication Factor: replicas per data node (1-10)
  • MongoDB only: optional arbiter node for tie-breaking in elections
  • Greenplum only: coordinator nodes (1-5)

Step 4: Resources

Setting	Options	Default
CPU (vCPU)	Free entry (e.g., 0.5, 1, 2)	0.5
Memory	1GB, 2GB, 4GB, 8GB, 16GB	1GB
Disk Space	1GB, 5GB, 10GB, 20GB, 50GB, 100GB	10GB
GPU Count	0-8 (0 for CPU-only)	0

When GPU Count is greater than 0, a GPU type selector appears to choose the GPU model.

Step 5: Backup Configuration

• Enable automatic backups: off by default
• Backup Schedule: Hourly, Daily, Weekly, or Monthly
• Retention: number of backups to keep (1-30, default 7)

Step 6: Deploy

1. Review the Add-on Information summary in the sidebar
2. Click Create Add-on
3. Watch the status move from DEPLOYING to RUNNING on the add-on details page
4. Get connection credentials from the Connection tab once the add-on is running

Using Add-ons in Your Apps

Add-ons your apps use are exposed through the STRONGLY_SERVICES environment variable. Add-ons are grouped by type, and each entry is one provisioned instance:

# Python Example
import os
import json
from pymongo import MongoClient

# Parse STRONGLY_SERVICES
services = json.loads(os.environ['STRONGLY_SERVICES'])

# Add-ons are grouped by type; pick yours by name (the label you gave it)
mongo = next(
    a for a in services['services']['addons']['mongodb']
    if a['name'] == 'main-database'
)

client = MongoClient(mongo['connection']['connection_string'])
db = client[mongo['connection']['database']]

# Use the database
users = db.users.find({'active': True})

Each add-on entry has this shape:

{
  "id": "addon-abc123defg",
  "name": "main-database",
  "type": "mongodb",
  "category": "add-on",
  "status": "running",
  "version": "8.2",
  "internal": false,
  "connection": {
    "connection_string": "mongodb://user_ab12cd34:<password>@<internal-host>:27017/admin",
    "uri": "mongodb://user_ab12cd34:<password>@<internal-host>:27017/admin",
    "host": "<internal-host>",
    "port": 27017,
    "database": "admin"
  },
  "auth": {
    "method": "username_password",
    "credentials": {
      "username": "user_ab12cd34",
      "password": "<password>"
    }
  },
  "limits": {
    "max_connections": 100,
    "storage_gb": 10
  },
  "metadata": {
    "cpu": "0.5",
    "memory": "1GB",
    "disk": "10GB",
    "backup_enabled": false
  }
}

The host is a private address that is only reachable from apps running on the platform, inside your organization's private space.

Add-on Management

The add-on details page has tabs for Overview, Connection, Metrics, Backup, Logs, Schedule, and Permissions.

Start/Stop

• Stop a running add-on to reduce costs when not in use; data persists while stopped
• Start a stopped add-on to bring it back
• Recover appears when an add-on is in an error state and redeploys it

Scheduled Start/Stop (Cost Savings)

The Schedule tab lets you automatically start and stop the add-on during specific hours:

• Enable the scheduled window and pick a timezone
• Set a start time, stop time, and days of the week
• Optionally skip US Federal or UK Bank holidays
• Data is preserved while the add-on is stopped

Backups

• Manual backup: Create Manual Backup on the Backup tab (add-on must be running), or Backup Now in the header when automatic backups are enabled
• Automatic backups run on your configured schedule (Hourly, Daily, Weekly, Monthly)
• Retention on the Backup tab: keep 3, 7, 14, or 30 backups
• The Backup tab shows current status, last backup, and next scheduled backup

Monitoring

The Metrics tab shows, with an optional auto-refresh:

• CPU, memory, and disk utilization
• Network I/O
• Connections per minute and average response time
• Instance count and uptime

Permissions

The Permissions tab controls which other users can access the add-on.

Backup Methods by Database Type

Backups are stored in the platform's S3 backup storage and use database-native tools for data integrity:

Database	Backup Tool	Format
MongoDB	mongodump	.archive
PostgreSQL	pg_dump	.sql
MySQL	mysqldump	.sql
Greenplum	pg_dump	.sql
Redis	redis-cli --rdb	.rdb
RabbitMQ	rabbitmqctl export_definitions	.json
Neo4j	neo4j-admin dump	.dump
Milvus	milvus-backup	.tar.gz
SurrealDB	surreal export	.surql

Backup Best Practices

• Production workloads: enable daily automated backups at minimum
• Critical data: use hourly backups with a larger retention count
• Before major changes: create a manual backup first