Databases
Managed databases on Forgeon (MDX), plans, and provisioning.
Last updated: 2026-03-17
Forgeon ships with managed databases (MDX) for Postgres, MySQL, MariaDB, and more.
When to use managed databases
Use Forgeon-managed databases when you want:
- Provisioning and credentials managed from one platform
- Built-in backups and restoration workflows
- Runtime + database observability in one place
- Predictable billing tied to the same tenant/project model
Eligibility
Database provisioning is available on Pro and Enterprise plans.
Quickstart
Plans
Database plans define:
- CPU / RAM / Storage
- Pricing (hourly + overage)
- Quotas (connections, backups)
Recommended setup flow
- Create cluster from Database Engine quickstart.
- Save credentials and inject
DATABASE_URLto environment vars. - Deploy app to staging and run connection sanity checks.
- Configure backup policy before production cutover.
- Add DB metrics alerts for saturation/error spikes.
Credentials
You can issue:
- Admin credentials (rotate on demand)
- Ephemeral credentials (time‑boxed)
Billing
Usage is rolled up hourly and priced by plan. See:
Operational checklist (before go-live)
- Network route from runtime to database verified.
- Connection pooling configured for your framework.
- Backup schedule and retention validated.
- Restore drill tested at least once in non-prod.
- Alert thresholds set for CPU, memory, and disk growth.
Troubleshooting
Cannot create cluster
- Check plan eligibility and quota.
- Confirm region capacity and account-level limits.
Credentials fail
- Rotate admin credentials and retry.
- Ensure app uses latest secret values after rotation.
App deploy succeeds but DB requests timeout
- Verify allowed network path and correct host/port from cluster detail.
- Validate TLS/SSL mode expected by your driver.