One commercial cloud family
Managed Public Cloud groups four practical service families under one commercial and operational boundary: protected object-storage backups, Linux cloud instances, high-availability PostgreSQL or MySQL, and managed Kubernetes with a private container registry. Each order names the exact bounded package; it does not expose an unrestricted provider-consumption account. AI inference budgets and single-node Essential databases are not offered for new sale because their commercial or operational boundary is not strong enough.
Current catalogue and private mappings
Silurian checks the current OVHcloud Spanish Public Cloud catalogue and applies the configured commercial margin to deterministic infrastructure costs. Customer-facing plans use stable Silurian references. Provider plan codes, project identifiers, resource identifiers, component costs and account credentials remain private OC/CIA evidence.
European location
Locations are plan-specific. Protected 3-AZ backup currently offers France; cloud instances and high-availability databases offer France, Germany and Poland; Kubernetes with its included private registry offers France and Germany. The chosen commercial region is recorded in the cart, order and product, revalidated during provisioning and cannot change without review.
Bounded monthly price
Every published amount is a net monthly Silurian price before applicable tax. Backup capacity has an explicit limit. Hourly General Purpose compute and MKS Standard components are converted to a fixed package using the maximum 744 hours in a calendar month. Database and Kubernetes packages state their complete included topology. Additional resources or architectural changes require a reviewed plan change instead of creating an open-ended charge silently.
Provisioning and Workspace
Payment creates a manual-review provisioning job and never launches an unattended provider purchase. Silurian verifies current cost, availability, location, intended use, abuse and compliance boundaries, then creates or associates the resource. Workspace shows the contracted plan, Silurian reference, resource name, location, infrastructure usage and forecast, budget-alert count, quota summary and support path without revealing provider references.
Routine operations
Workspace exposes only bounded day-to-day controls appropriate to the contracted module: instance power, reboot, rescue, rename and temporary console; logical database and user administration; Kubernetes maintenance, update policy and one-time kubeconfig controls; and private backup-storage recovery credentials. Every write requires ownership, exact confirmation and the independent customer write gate. Cost, capacity, resource creation/deletion and recovery-scope changes remain reviewed commercial operations.
Backup and object storage
Protected capacity uses S3-compatible object storage distributed across three availability zones. The package includes a daily workflow, stated retention and restore assistance, but the protected source, credentials and successful backup execution must still be configured. Capacity, retention and restoration scope are the values stated in the order.
Cloud instances
Every offered instance includes basic public IPv4 and IPv6. Development plans use Discovery instances with shared resources and are for tests, sandboxes and development. Production plans use General Purpose instances with guaranteed resources. Floating IPs, snapshots, block volumes, load balancers, Windows licences and operating-system administration are not included unless the order says so. A VPS remains the preferred recommendation for one simple economical server.
High-availability databases
New managed MySQL and PostgreSQL sales start with a two-node Business topology. It includes automatic failover, a 99.9 percent SLA, daily encrypted backups retained for 14 days and point-in-time recovery. Storage, flavour and service plan can be upgraded, but plan downgrade is not supported. Hosting or a self-managed VPS is normally more economical for a small or non-critical database.
Managed Kubernetes
The production packages include an MKS Standard control plane, General Purpose worker instances and a private registry. MKS Standard provides dedicated etcd and a 99.9 percent SLA in 1-AZ or 99.99 percent in supported 3-AZ regions. Load balancers, persistent volumes, application deployment, monitoring and backup are separate resources or services and are never implied by the package.
Infrastructure supplier and support
Silurian supplies, invoices and supports the managed service. The underlying Public Cloud infrastructure is operated by OVHcloud and contracted through OVH HISPANO, S.L., calle Alcalá 21, 5ª, 28014 Madrid, Spain. Silurian coordinates provider incidents; the customer receives no access to Silurian's provider account.
Acceptable use, abuse and compliance
The customer is responsible for lawful workloads, authorised users, content, credentials, security controls and timely response to abuse or compromise notices. Silurian may investigate, restrict or suspend affected resources for non-payment, prohibited activity, incident containment or legal risk. Higher-risk workloads must be disclosed before activation.
Official sources
This Silurian guide uses the following provider documentation as its technical source. Product availability still depends on the managed account and plan.
OVHcloudPublic Cloud↗ OVHcloudPublic Cloud pricing↗ OVHcloudObject Storage↗ OVHcloudManaged Kubernetes Service↗ OVHcloudContracts and service-specific conditions↗