Inside Private Cloud
Managed Postgres, MySQL, SQL Server, and Oracle in the dedicated package: licensing, migration, and DBAs on call.
Best for: ERP and production data that cannot wait
Clear options. Clear when to use each
Self-serve clusters
Console clusters a la carte when the catalog unlocks. Engine list and sizes lock with Product.
Best for: Teams that want a database without a sales call
Who it's for
Product teams
Production data without hiring a DBA to babysit replication.
ERP and enterprise workloads
SQL Server and Oracle with licensing, homologation, and support in one package.
Teams leaving DIY
You already run Postgres on an instance and are tired of being the failover plan.
Migrations
Coming off a hyperscaler or on-premise, with an architect on the cutover.
What you get
Provisioned, not assembled
A production-shaped cluster from the start, instead of building replication on a bare instance and hoping.
Automated backups
Scheduled backups with restore points, run by the platform and not by a cron somebody wrote years ago.
Failover designed in
A standby takes over when a node fails, so a hardware event is not a company incident.
Private by default
Reachable from your VPC, not from the open internet. Encrypted in transit and at rest.
Patching and version upkeep
Minor versions and security patches applied on a maintenance window you agree to.
Scale the cluster, keep the data
Add CPU, memory, and storage as the workload grows, without a migration project.
Monitoring that reaches a human
Connections, cache hit ratio, disk, and latency watched by the 24/7 NOC.
Engines teams already run
Postgres, MySQL, SQL Server, and Oracle today, with licensing included in the package.
Managed Databases vs a database on Cloud Compute
| Managed Databases | Database on Compute | |
|---|---|---|
| Ops | Platform plus Optidata DBAs | Yours: patches, backups, HA |
| Backups | Scheduled by the platform | Whatever you configured |
| Failover | Standby designed in | You build and test it |
| Best for | Production data you should not babysit | Full control, unusual engines, dev and test |
From config to live
Pick the engine
Postgres, MySQL, SQL Server, or Oracle. Licensing handled in the Private Cloud package.
Size the cluster
CPU, memory, and storage for the workload, with a standby when you need failover.
Attach the network
The cluster joins your VPC so only your applications can reach it.
Connect and migrate
Point the app at the connection string. Optidata engineers help move the existing data.
Short answers
Can I get a managed database today?
Yes, through Private Cloud, with licensing and DBAs included. The self-serve console SKU is on the roadmap.
Which engines are supported?
Private Cloud runs Postgres, MySQL, SQL Server, and Oracle. The self-serve engine list locks with Product.
Who handles backups and patching?
Optidata. Backups run on a schedule and patches land on an agreed maintenance window.
Is the database exposed to the internet?
No. Clusters live on your private network and are reachable from your workloads.
Can I migrate an existing database?
Yes. Migration is part of the Private Cloud engagement, including ERP homologation when the app needs it.
What if I want to run it myself?
Cloud Compute with Block Storage is live today, and you keep full control of the engine.