Skip to Content

Corvus Cloud for Odoo · Dedicated, managed hosting

Dedicated Odoo hosting.
A clear path to live.

An Odoo environment for your business, with room to test changes before they reach your team.

Choose the resources and location you need. Bring your modules, review changes in staging, and agree how your live system is managed.

New Odoo projects and existing systems · Community or Enterprise

YOUR PROJECT01 / Dedicated environment
Your managed virtual serverResources allocated to your project
COMPUTEvCPU + RAM
DATAStorage
NETWORKDedicated IPv4
01DevelopBuild the change
02StageReview the result
03LiveRun the business
Location selected with your configuration

Environment illustration. Your proposal defines the final setup.

Built around your project

More control over the way you run Odoo.

01

An environment of your own

A dedicated virtual server keeps your project separate from other customers’ Odoo installations. Agree CPU, memory and storage for your workload.

02

A location that fits your team

Request a supported region close to your users. Your proposal confirms the available location and a dedicated IPv4 address for the environment.

03

Changes with a review step

Keep development, testing and everyday work separate. Your team can review a change before it reaches the live business system.

Dedicated environment means a virtual server assigned to your project. Shared or dedicated CPU capacity depends on the configuration agreed in your proposal.

A controlled route to production

Test the change. Then change the live system.

Connect your selected GitHub repository through a GitHub App during onboarding. Keep your own modules and choose the branches used for review and release.

REVIEW LANE

From your repository to staging

  1. 1Push your changeUse the agreed review branch.
  2. 2Build and stagePrepare that revision in an isolated environment.
  3. 3Review the workCheck real workflows and permissions with your team.
LIVE RELEASE LANE

A checked release, with a recovery point

  1. 1Select the live revisionStart from the agreed live branch.
  2. 2Back up liveKeep the database and its files together.
  3. 3Test a cloneRestore an isolated copy and test the selected change.
  4. 4Approve and promoteProceed with the checked revision after passing review.
  5. 5Close the releaseReview the result and clean up the temporary clone.

Release workflow illustration. The agreed service scope identifies automated steps and steps handled by Corvus.

Your project, in view

Understand what is running.
See what happens next.

Use the customer console to follow your project’s environments, deployment jobs and backup records. Access is limited to the operations agreed for your account.

EnvironmentsDevelopment, staging and live
DeploymentsSelected revision and job progress
BackupsRecovery records and agreed operations
AccessYour project and permitted actions

Console capability overview, not a live dashboard.

WHEN YOUR WORKFLOW NEEDS MORE

Bring your modules.
Or plan the missing one.

Include existing custom modules in the repository review. If you need a new workflow, Module Studio helps turn the requirement into a scoped module request.

Agree compatibility, access rules and acceptance first. Review the result in staging before adding it to live.

Explore Module Studio

Module development is scoped separately from hosting.

Know what you are choosing

One proposal. Clear responsibilities.

Your proposal separates the environment, ongoing care and any additional work. Enterprise licensing and third-party app licences are confirmed separately.

CORE HOSTING SCOPE

Your managed environment

  • Virtual server, resource profile and selected location
  • Dedicated IPv4 and agreed Odoo setup
  • Environment and repository configuration
  • Controlled releases with a matched safety backup
  • Customer console access within agreed permissions
OPTIONS TO QUOTE

Care that fits your needs

  • Scheduled backups, retention and storage destination
  • Migration of your existing Odoo system
  • Additional environments or capacity
  • Custom modules and integrations
  • Ongoing support and upgrade work
YOUR PART OF THE SETUP

Ownership and acceptance

  • Company details and an authorised contact
  • Enterprise and third-party licence entitlements
  • Approval to access the selected repository
  • Domain and migration information when needed
  • Review of business workflows before go-live
Release safety and recurring backups serve different purposes.

The live-release safety backup stays part of the release process. Scheduled backups cover ongoing recovery needs; frequency, retention, destination and restore support are agreed in your proposal.

A useful starting point

Plan an environment around your work.

Choose your hosting mode, edition and version, then sign in to review current plans. For an existing system or advice on your setup, request a hosting proposal.

01 Your Odoo setup

Managed hosting combines the Corvus service with a separately charged server. BYO covers the same service on a host you provide, with no bundled server charge. For BYO, paid activation and approved host enrollment are required before bootstrap. Existing Odoo systems still require migration review.

02 Resources and location

Know your requirements? Add preferred resources below. Leave them blank for a recommendation.

Choose location and capacity from the current plans after sign-in. Use Request a proposal for a custom resource configuration.

03 Delivery and care

Repository authorisation happens during onboarding. No access tokens or credentials are needed here.

From proposal to your first login

A clear route from agreement to access.

Today, start with a configuration enquiry and guided onboarding. Online ordering is being prepared; this is the planned order sequence.

  1. 01

    Agree & order

    Confirm resources, scope, price and terms.

  2. 02

    Payment

    Complete the agreed payment step.

  3. 03

    Company review

    Provide the required business details.

  4. 04

    Corvus approval

    An authorised person approves provisioning.

  5. 05

    Set up & access

    Provision the agreed environment and open your console.

Payment alone does not authorise provisioning in the planned flow. Access follows verification, explicit approval and successful setup.

Before you decide

A few practical questions.

The offer is a dedicated virtual environment for your project. CPU allocation can be shared or dedicated at the provider level; the agreed configuration states which. A dedicated IPv4 address is included in the proposed environment scope.

You can request either edition. Odoo 20 is the starting point here; existing versions, modules and migration requirements are reviewed before acceptance. Enterprise requires a valid licence and is priced separately from hosting.

Yes. Identify the selected repository during onboarding and authorise the GitHub App for the agreed access. The delivery review covers branches, modules and dependencies. Do not send passwords or access tokens through the enquiry form.

Your quote states the schedule, retention, destination and restore support. Recurring backup options are separate from the matched database-and-files backup used to protect a live release. No offsite retention or recovery-time promise is implied by this page.

Request a migration review. We assess version, edition, database size, custom modules, licences and a suitable cutover plan before quoting the work.

The proposal confirms available resources and location, recurring charges, any one-time work, tax treatment and the agreed start. This form requests a proposal; it does not create a subscription or reserve capacity.

Your environment is not ready for business use until setup is completed and access is provided. Verification questions or configuration changes are resolved with you. Payment, cancellation and refund terms must be agreed before an order.

Start with your setup. We’ll help shape the rest.

Plan my setup → Read the Cloud enquiry guide →