Service

Sovereign Cloud and Infrastructure

Self-hosted Linux infrastructure with controlled deployment, bounded network exposure and restore routines that have been run.

Engineers in a clean room building the nadir deck of the Europa Clipper spacecraft
Image: NASA/JPL-Caltech. NASA library
On this page
  1. When this fits
  2. What the work covers
  3. What you receive
  4. How completion is decided
  5. What you provide
  6. What RJV does not promise
  7. How to start

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 because 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.

On a phone or tablet

Use the browser with a connection to the host.

See what works on your device
Find this offering
Browser (W)
Carry out every authorised operation
Client (C)
Compute on the device itself
Not supported (U)
Use a host you own
Client (C)
Work without the host or the internet
Not supported (U)

Nothing here needs a desktop because every operation that this site offers works in the browser on a screen down to 320 CSS px which is the narrowest width that we test. Where a row reads Not supported the browser is the alternative because we do not install the release on the device and no offline mode exists and the host that you control must be reachable and we do not use device sensors or accelerators.

Published
29 October 2026
Revision
2

Last reviewed 29 October 2026.