Databases

A managed database is a database Forte runs for you. It belongs to a Project, and every Service in that Project can connect to it. You don't provision a server, install a database engine, hand around credentials, or configure TLS.

Managed databases are not covered by GA service commitments unless a written order form says otherwise. Review feature maturity before using them for a production dependency.

What Forte manages for you

• Provisioning: shared-tier databases are ready in under 30 seconds.
• Credentials: Forte manages credentials and token rotation automatically for each Service that you connect to the database.
• Connection wiring: connecting a database to a Service sets the environment variables your code already reads, then redeploys the Service.
• Encryption: your data is encrypted at rest and in transit.
• Daily backups: Forte backs up every database once a day. Backup frequency and PITR (point in time recovery) are customizable for dedicated clusters.
• Monitoring: storage, connection, and query metrics, plus a slow-query list, in the console.

Which engines are available

• PostgreSQL — relational, full SQL, the default.
• MongoDB-compatible (closed alpha) — a document database that speaks the MongoDB wire protocol, so mongosh, Compass and every MongoDB driver work unchanged. Request access from the engine tile when you create a database.

Both engines run on the shared tier with the same storage sizes, the same connection limits and the same prices. A few MongoDB features aren't available yet: multi-document transactions, sharding commands, change streams, and server-side roles (every database user has full access to its own database). The aggregation pipeline and TTL indexes work; expired documents are removed about once a minute.

Choose a tier

Forte offers two tiers. You create a shared database yourself in the console. A dedicated database is set up with the Forte team.

When to choose shared

Choose shared when:

• You're prototyping, building, or running a production app with steady, low load.
• You'd rather pay for the storage you provision and the query time you use than reserve capacity up front.

On the shared tier your database runs on a cluster alongside other Forte customers. The storage is yours alone, but the compute is shared. Forte rate-limits and throttles noisy neighbors, but the performance of your queries can still be inconsistent due to traffic from other Forte customers.

When to choose dedicated

Choose dedicated when:

• Your workload needs predictable performance under heavy or spiky load.
• You need isolated capacity rather than a shared cluster.
• You need a backup schedule and retention period set to your own requirements.
• Compliance rules out shared infrastructure.

Dedicated clusters are sized and configured with the Forte team rather than in the console. Contact support to talk through your workload and get a quote.

What it costs

Shared databases — PostgreSQL or MongoDB-compatible — bill on the same two rates:

• Storage: $0.50 per provisioned GB, per month. You pay for the size provisioned, not the bytes you wrote.
• Active compute: $0.20 per vCPU, per hour, charged only while the database processes queries.

Bulk discounts apply when active compute exceeds 30% of monthly capacity. Contact us for pricing.

Dedicated databases are quoted per workload. See Pricing and quotas for worked examples and per-account limits.

Next steps