Sovereign Cloud and Infrastructure

When this fits

You want core services to run on infrastructure you operate, so that a vendor's policy or price change cannot take them away.

What the work covers

• Host hardening, infrastructure as code and a controlled release path.
• Network boundaries designed around least privilege.
• Backup design with encryption and a restore procedure.
• A recovery rehearsal.

What you receive

• The infrastructure definitions and the way to rebuild from them.
• The backup configuration and the record of the restore that was performed.
• Operating procedures, including key custody.

How completion is decided

The customer's team restores a backup onto a clean machine and brings the service up from the delivered definitions. The recorded result is the evidence that recovery works.

What you provide

• Hardware, a hosting contract or a decision to have them specified.
• The domain names and network details the services need.
• A person who will hold the keys.

What RJV does not promise

• A fixed price or duration before the scope is known.
• Regulatory approval or a certificate; the customer remains the regulated party.
• Availability the hosting provider or power supply controls.

How to start

Describe the problem on the Work with Us page. Every engagement follows the stages on the engineering page, and the commercial terms explain what determines scope and how the work is charged. Ownership at handover is described in deployment and ownership.