Skip to main content

General reversibility policy

Objective​

Reversibility is a fundamental commitment of Numspot. We promote an open and interoperable ecosystem to guarantee our customers' freedom of choice. As such, we comply with the principles of the SWIPO (SWItching and POrting) code of conduct for cloud providers, designed with the European Commission.

Our reversibility principles are as follows: an open and standard environment in which our customers have extensive control over their systems and their data; detailed customer documentation to facilitate inbound and outbound migration as much as possible.

General reversibility model for Numspot​

Infrastructure control by our customers​

Our model as a sovereign cloud infrastructure provider is to give customers extensive administration rights over their infrastructures. In particular, a customer must have the freedom to carry out a migration autonomously, for example to import elements, or to export their data to the infrastructures of other providers.

As a result, we consider that our responsibility is to offer a stable and standardized technical environment, and that the effective implementation of reversibility largely falls within the customer's area of responsibility. Customer-responsibility actions include planning, volume forecasting, the actual export and import of data, and securing data transfers.

In addition, we do not involve third parties in the provision of our services; this provision and the technical responsibilities that follow from it (the ability to access or operate on customer infrastructures, maintenance in operational condition) remain Numspot's responsibility.

Standard formats and tools​

The widespread use of standard tools and formats is a key point for reversibility. Our infrastructures are aligned with standard market building blocks, either open, or created and maintained by a recognized vendor. As such, it must always be possible to migrate the core functionality of an architecture.

However, we do not guarantee the ability to migrate the entirety of the functionality of Numspot products. Indeed, some additional functionality is built based on the specific characteristics of the Numspot environment and cannot be migrated as is; it will be necessary to rebuild equivalents where applicable. Reproducing some of the functionality developed by Numspot may be difficult and require a dedicated project team.

We therefore distinguish:

  • The core functionality of a product (for example, hosting a database, running virtual machines and storage spaces), for which we guarantee the ability to migrate.
  • The Numspot implementation (for example the Numspot API, the configuration of network equipment), the migration of which will require adaptations to a new environment.
  • The specific functionality (for example the advanced functionality of the Numspot console, the integrations specific to the Numspot ecosystem), the migration of which as is cannot be guaranteed.

Documentation of migration procedures​

Reversibility-oriented documentation must meet two objectives: first, the documentation must remove any blocking obstacles to a migration: for example, making explicit any particular configurations or implicit prerequisites. Second, the documentation makes it possible to lower the skills required to carry out a migration, to make it accessible to more customers and to reduce the human investment needed for it to proceed smoothly. In other words, the role of the documentation is to ensure that a migration that is technically possible is also possible to carry out in practice within a concrete project.

The documentation must, in the same way as the other reversibility functions, consider all migration scenarios:

  • From Numspot to another cloud provider.
  • From Numspot to the customer's own infrastructures.
  • From another cloud provider to Numspot.
  • From the customer's own infrastructures to Numspot.

Our role is also to document:

  • The distinction between the functionality that belongs to the core, to the implementation or to the Numspot-specific layer.
  • Any implementation specificities, dependencies on an environment or a technology implemented at Numspot.

Reversibility per service​

The reversibility policies specific to each managed service are detailed in the following pages:

Cette page vous a-t-elle été utile ?