Planned

Era Scale

Databases in one click.

Era Scale

The Era Scale provides one-click database provisioning and lifecycle management. Deploy production-ready database clusters with replication, backups, and monitoring — all managed through Dragon’s Eye.

Features

FeatureDescriptionStatus
1-Click ProvisioningDeploy a production-ready database instance in seconds. PostgreSQL, MySQL, Redis.Planned
SnapshotsInstant database snapshots via the Storage Scale. Point-in-time recovery.Planned
CloningClone a production database for development or testing in seconds. Copy-on-write, no additional storage until data diverges.Planned
Automated PatchingSchedule database engine patches with automatic rollback on failure.Planned
ReplicationConfigure primary-replica topologies through the UI. Automatic failover with the HA Scale.Planned
Connection PoolingBuilt-in connection pooling. No external pooler to deploy and manage.Planned
MonitoringPer-database metrics: queries per second, latency, connections, replication lag. Integrated with the Monitoring Scale.Planned
Backup IntegrationAutomatic backup schedules with the Backup Scale. Application-aware snapshots for consistency.Planned
Resource ManagementCPU, memory, and I/O limits per database instance. No noisy neighbours.Planned
Template LibrariesPre-configured database templates for common workloads. Tuned for OLTP, OLAP, or mixed.Planned

Why This Matters

Database operations consume a disproportionate amount of infrastructure team time. Provisioning, patching, backup, replication, failover — each requires specialist knowledge and careful execution.

Era makes these operations routine. A developer requests a PostgreSQL instance, gets it in seconds, and it comes with replication, backups, and monitoring already configured. The infrastructure team sets the policies; Era enforces them automatically.

Cloning for Development

One of Era’s most powerful features is instant database cloning. Need a copy of production for testing? Clone it. The clone is created instantly using copy-on-write — no data is physically copied until it’s modified. A 500GB production database clones in under a second and initially consumes zero additional storage.

This eliminates the “we can’t test against real data” problem without the “we can’t afford to copy production” constraint.