Germany
Eligible Falkenstein and Nuremberg locations are grouped clearly while the exact city and country remain visible in catalog evidence.
Managed Odoo, clearly operated
Your Odoo environments, releases and health—in one console.
See what is running, why a release stopped, and which safe action is available without learning Linux or receiving root access.
Community and Enterprise 15–20 hosting requests are open. Pricing and applicable tax must be confirmed before payment and provisioning. Enterprise licences are customer-owned; Odoo 15–17 requires legacy hosting-only consent. Manage your order and billing in Odoo.
Entitlement active
acme-operationsDevelopmentReady19.0-dev
StagingHealthy19.0-staging
LiveHealthy19.0
exact commitprivate buildimage digestenvironment
Latest observed state · freshness timestamped
Observed provider catalog
Review region and compute profiles without treating them as orderable capacity.
Corvus records curated CX, CPX and dedicated-CPU CCX profiles across Hetzner's EU Central, US East and US West network zones. Catalog availability is timestamped provider evidence only: the current controlled beta does not authorize a new VM or make a profile purchasable.
Ashburn, Virginia
Regional CPX and CCX profiles appear only when the provider's observed catalog reports the exact server type as available.
Hillsboro, Oregon
Pricing, capacity, architecture, source revision and availability are snapshotted as evidence instead of trusted from browser fields.
A console with boundaries
Useful operational clarity, without a hidden terminal.
Every screen starts from the exact customer, project and environment authorized by the server.
Three environments
One configured branch each for development, staging and live, with distinct runtime and data boundaries.
Exact releases
Follow a source commit through the private build and immutable image digest recorded for an environment.
Typed operations
Request status, doctor, bounded logs, restart or a local matched backup—never an arbitrary command.
Environment intent
Development, staging and live are not interchangeable.
Development is for iteration. Staging is for review away from live. Later live updates use the accepted matched-backup and isolated clone-test path before an exact digest is promoted.
Tour the environment cardsDevelopment
Fast source feedback with conservative non-production defaults.
Staging
Protected customer review away from live data and routes.
Live
Customer-facing Odoo with guarded later-update evidence.
Safe operations
Ask for the outcome—not a shell command.
StatusDoctorBounded Odoo logsRestart OdooMatched backup
Every operation uses a fixed project, environment and validated request shape, with a durable outcome you can review.
Observed health
See pressure before it becomes an outage.
Fresh guest measurements, provider observations and route probes keep CPU, available memory, storage, inodes, network, reboot and Odoo environment state in context. Gaps stay visible, and deployment success is never reused as a runtime-health claim.
Explore monitoring and alertsManaged foundation
Specific enough to trust.
- One dedicated project VM
- Separate development, staging and live environments
- Read-only selected-repository GitHub connection
- Exact commit, private image and digest correlation
- Matched PostgreSQL-plus-filestore backup evidence
Operational clarity
See the state behind every release.
- Health and deployment outcomes stay attached to the exact environment
- Guarded live updates retain backup and clone-test evidence
- Notifications remain tied to the correct customer and project
- Commercial records stay connected through your Odoo account
Already a Corvus Cloud customer?
Open your project from the Corvus Nexus Odoo account.
The one-use handoff keeps your Odoo commercial session separate from the technical console session.