CERVOX
FREN
Describe my situation

Infrastructure, Cloud & AI. A scoped engagement, a deliverable you keep.

Servers, virtualisation, cloud: we diagnose, modernise, migrate and put AI into production — then hand back the keys.

Describe my situation

Remote engagements in France and the Benelux. On-site work can be considered depending on the engagement.

Written estimate within 24 business hours, after a first 20-minute conversation.

An emergency? Call +33 4 44 05 07 68.

Environments

Linux, Windows, VMware, Hyper-V, Proxmox, KVM. In the cloud, mainly AWS; Azure and Google Cloud case by case.

  • AWS
  • Microsoft Azure
  • Google Cloud

Most of our engagements are delivered remotely.

We support our clients in France and the Benelux, directly on their environment. On-site work can be considered depending on the engagement.

What is your situation?

Infrastructure & systems

Your servers and virtualisation are ageing, with no clear view of the whole setup?

Infrastructure & virtualisation

We assess your servers, virtualisation, network and storage, then carry out the changes defined in the scope.

You receive
  • An assessment of servers, virtualisation, network and storage
  • Risks and weak points identified
  • A reasoned evolution path
  • The changes planned in the scope, carried out and checked
  • Documentation and handover
Done when

The assessment and evolution path are handed over to you, and the changes planned in the scope are carried out and checked.

Linux · Windows Server · VMware · Hyper-V · Proxmox · KVM

Describe my situation
AI in production

You want to put AI into production in an environment you control?

AI in production

We put your AI use case into production in an environment you control — for example Claude, Anthropic’s AI model, through Amazon Bedrock on your AWS account — with the access rights, cost limits and traceability defined in the scope.

You receive
  • The AI model enabled on your environment (e.g. Claude in Amazon Bedrock)
  • Access limited to the intended people and applications
  • Usage logging
  • Cost alerts and caps
  • A first use case connected, defined in the scope
  • Documentation and handover
Done when

The AI model can be used on your environment under the conditions defined in the scope, and the first planned use case works.

Amazon Bedrock · IAM · CloudWatch · AWS Budgets

Describe my situation
Cloud & migration

Keep your infrastructure, evolve your cloud, go hybrid or switch provider: not sure which?

Keep, evolve or migrate

You receive
  • Three costed options over 12 months
  • A written and reasoned recommendation
  • The assumptions and main trade-offs of each option
Done when

The three 12-month options and the written recommendation are handed over to you, based on the agreed scope and assumptions.

Describe my situation
Cloud & migration

Your application or server has to leave its current hosting?

Cloud migration

We migrate your application and its data to your AWS account, from a physical server, a virtualised environment or another provider, preserving the behaviour defined in the scope. The cutover takes place on the date agreed with you.

You receive
  • Your application migrated to AWS
  • Your data migrated according to the scope
  • The required AWS configuration
  • Functional checks
  • Documentation and handover
  • An estimate of your monthly AWS bill
Done when

The migration defined in the scope is completed on your AWS account, the planned checks are carried out and the handover items are delivered to you.

From a physical or virtual server, OVH, Heroku or Azure

Describe my situation
Cloud & migration

Has your AWS infrastructure become too expensive or too dependent on a single provider?

Migration to a European cloud

We audit your AWS infrastructure, identify migration possibilities and transfer compatible resources to a French or European hosting provider suited to your needs.

You receive
  • An audit of your existing AWS infrastructure
  • An analysis of dependencies, costs and portability
  • A migration plan to the target hosting provider
  • Migration of the resources included in the validated scope
  • Documentation and handover
Done when

The planned resources are migrated and checked on the target infrastructure, and the recovery documentation is handed over to your team.

OVHcloud · Scaleway · Outscale · Terraform · Infrastructure as Code

Describe my situation
Performance & reliability

Your AWS bill keeps rising and you don’t really know why?

AWS cost optimisation

We analyse your AWS bill over the last 90 days, identify what drives it and propose optimisation options. Only the ones you approve are applied.

You receive
  • Analysis of your AWS bill over 90 days
  • The main cost items and their origin
  • Possible corrections, with their trade-offs
  • The corrections you approved, applied
  • Alerts and a budget configured according to the agreed scope
  • Documentation and handover
Done when

The analysis is handed over to you, the corrections you approved are applied and the planned alerts and budget are in place.

AWS Cost Explorer · AWS Budgets

Describe my situation
Performance & reliability

Learning about outages from your customers, or unsure about your backups?

Backup & recovery

We configure the planned alerts, set up or check the backups, on your servers or in the cloud, then run an actual restore, in an environment and on resources agreed with you.

You receive
  • The alerts planned in the scope, configured
  • The planned backups, set up or checked
  • A restore actually run on the agreed resources
  • The restore procedure and its results documented
  • Documentation and handover
Done when

A restore has been run and checked on the agreed resources and environment, and the procedure is documented.

AWS Backup · Amazon CloudWatch · monitoring

Describe my situation
Performance & reliability

Are your deployments manual, risky or dependent on a single person?

DevOps & deployments

We set up in your repository an automated deployment process, with the checks and rollback mechanism defined in the scope. If the application is not live yet, its first go-live can be part of it.

You receive
  • A deployment pipeline
  • Its configuration in your repository
  • The planned checks
  • Rollback executed once with you
  • A demonstration of how it works
  • Documentation
Done when

A member of your team has re-run the pipeline.

GitHub Actions · GitLab CI · AWS CodePipeline · Ansible

Describe my situation
Infrastructure & systems

Your infrastructure exists, but nobody really knows what’s in it anymore?

Infrastructure audit

We analyse your infrastructure read-only, on your servers or in the cloud, to establish what is in place, identify the main points of attention (architecture, costs, security) and propose an evolution path. The same framework can be used to validate an architecture before building it.

You receive
  • An inventory of the analysed resources
  • The main points of attention
  • A structured analysis
  • Recommendations and an evolution path
  • Debrief and documentation
Done when

The defined scope has been analysed and the audit report is handed over to you.

Servers or cloud · read-only · inventory · architecture

Describe my situation

Your situation is different? ↓

You are investing in a company, acquiring it or preparing its sale, and you need to know what its technology is really worth?

Technical due diligence

We analyse read-only the infrastructure, code and technical organisation of the company concerned, wherever it is hosted, to establish the risks, their severity and the cost of addressing them.

You receive
  • An assessment of the analysed infrastructure and code
  • Risks ranked by severity
  • An estimate of the cost and effort of remediation
  • Critical dependencies identified (people, providers, licences)
  • The points to address before or after the transaction
  • An oral debrief and the written report
Done when

The defined scope has been analysed and the report is handed over to you within the timeframe agreed for the transaction.

AWS · Azure · Google Cloud · OVH · Scaleway · code · security · costs

Describe my transaction

What stays in your hands

Everything stays with you.

Your environment and your code remain yours: resources are created on your side and the delivered code goes into your repository. We only have access to what the engagement requires, and that access is removed at the end.

Assessment before work.

We look first, we propose next, you decide. Nothing sensitive is changed without your agreement.

One engagement, one end.

You know from the start what you will receive and when it is finished. Documentation and handover are part of the engagement, according to the scope. No subscription.

Your situation is different?

We also work on other situations, on your servers or in the cloud, when the scope can be clearly defined.

  • We put it live on your own AWS account, with its domain, the services it needs and the backup of its data.

    You receive
    • Your application deployed on your AWS account
    • Its domain configured
    • The AWS services it needs, configured
    • Backup of its data in place
    • Documentation and handover
    Done when

    The go-live defined in the scope works on your AWS account and the planned items are delivered.

    Depending on the application: S3 · CloudFront · ECS · RDS

    Describe my situation

  • We identify the cause of the problem within the agreed scope, step in to fix it and check that everything works with you.

    You receive
    • The problem identified and its origin documented
    • The fix applied
    • Functional check
    • Documentation of the recovery
    • Remaining actions documented, if needed
    Done when

    The problem defined in the scope is solved or its origin is clearly established, with the remaining actions documented.

    If the cause is out of scope, it is written down and the engagement stops. An amendment decides what happens next.

    AWS · Linux · Windows · networking · configuration · Docker

    Describe my situation

  • We rebuild in your repository the definition of your existing infrastructure so that it can be reviewed, versioned and reproduced.

    You receive
    • The infrastructure defined in your repository
    • Existing resources documented
    • Structured, versioned code
    • A recovery procedure
    • Documentation and handover
    Done when

    The infrastructure defined in the scope can be reproduced from the delivered code and the recovery procedure is documented.

    Terraform · AWS CDK · Pulumi · Ansible

    Describe my situation
  • You have a process to automate without managing a server?Serverless automation
  • You already have an audit or an action plan?Implementing the action plan
  • Another situation? Describe it: we’ll tell you whether we can help.Describe your situation

How it works

  1. Describe your situation.

    A few lines are enough. We tell you whether we can help, and how.

  2. We define the scope.

    What will be done, what won’t, what you will receive.

  3. We carry out the work.

    On your environment, with access limited to the engagement. In validated stages for longer projects.

  4. You receive the deliverable.

    Deliverable, documentation and handover, then we remove our access.

Frequently asked questions

How much does an engagement cost?

The price depends on the scope. After a 20-minute conversation, you receive a written estimate within 24 business hours. The final price is set in a written proposal, before any work begins. No subscription.

Do we need to give you access to our environment?

Yes, with access limited to what the engagement requires. An audit is carried out read-only. Access is removed at the end of the engagement.

Where do our code and infrastructure stay?

With you. Resources are created in your own environment and the delivered code goes into your repository.

Do you work on site?

Most of our engagements are delivered remotely, in France and the Benelux. On-site work can be considered depending on the engagement.

Which environments do you work on?

Linux and Windows servers, virtualisation (VMware, Hyper-V, Proxmox, KVM) and the cloud, mainly AWS. Azure and Google Cloud depending on the engagement.

What do we receive at the end?

The deliverable defined in the scope, its documentation and the handover to your team. You know from the start when the engagement is complete.

How do we get started?

Describe your situation in a few lines using the form. We tell you whether we can help, and how, then we write the scope with you.

Describe your situation.

A few lines are enough. We tell you whether we can help, and how.

Written estimate within 24 business hours, after a first 20-minute conversation.

Prefer to talk? Call +33 4 44 05 07 68 or book a meeting.

Reply by email. No commitment.

This information is used to respond to your request. Privacy policy

Remote engagements in France and the Benelux. On-site work can be considered depending on the engagement.