Segal Databases
Run managed application data services with engine-specific sizing, access and recovery settings.
Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.
How the service fits.
Managed engines and plans exposed by the project. Extensions, vector capability and recovery options are engine-specific.
- 1
Choose the supported engine, version and region
- 2
Configure service size and allowed network access
- 3
Create application users and test backup recovery
Service architecture
- Relational, key-value and search engines have different service contracts
- Credentials and connection endpoints remain server-side
- Backup and maintenance policies belong to each database service
Operating boundaries
- Vector support depends on engine and extension availability
- Database plans do not share one interchangeable capacity unit
- Cross-region recovery and failover need an explicit design
Deployment & support
Segal provides the branded service experience and coordinates configuration, support and commercial scope. The infrastructure service is supplied through OVHcloud; provider eligibility and applicable service terms must be confirmed before activation.
Upstream service: Public Cloud Databases. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.
Upstream technical reference