A specific project or problem on AWS? A scoped engagement, a deliverable you keep.

We work on your cloud to execute, verify, or plug in AI — on your account, with a deliverable, then we hand back the keys.

Describe my situation

Remote engagements in France and the Benelux. On site when the situation requires it.

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

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

Cloud environments

We work mainly on AWS. Azure and Google Cloud environments can also be considered depending on the engagement.

  • AWS
  • Microsoft Azure
  • Google Cloud

99% of our engagements are carried out remotely.

We support our clients throughout France and the Benelux, directly on their environment. On site when the situation requires it.

What is your situation?

You want to use generative AI on your own AWS environment, with your own access and security rules?

Claude on your AWS account

We set up Claude, Anthropic’s AI model, on your own AWS account through Amazon Bedrock, with the access rights, cost limits and traceability defined in the scope.

You receive
  • Claude enabled in Amazon Bedrock on your AWS account
  • 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

Claude can be used on your AWS account under the conditions defined in the scope, and the first planned use case works.

Amazon Bedrock · IAM · CloudWatch · AWS Budgets

Your application is ready, but not yet in production?

Going live with an AWS application

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

Torn between AWS and a French or European hosting provider, or want to check whether your current infrastructure is still the right fit?

Move to AWS, stay, or leave

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.

Your production application has to leave its current hosting?

AWS migration

We migrate your existing application to your AWS account, preserving its data and 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 OVH, a dedicated server, Heroku or Azure

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

Automated deployments

We set up in your repository an automated deployment process, with the checks and rollback mechanism defined in the scope.

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

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

AWS account audit

We analyse your AWS account read-only to establish what is in place, identify the main points of attention and give you an actionable view of the existing setup.

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

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

AWS · read-only · inventory · architecture

Your AWS infrastructure has a problem you can’t solve?

Intervention on an AWS problem

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.

EC2 · S3 · RDS · ECS · Lightsail · networking · configuration · Docker · deployment

Your AWS infrastructure was built by hand and nobody really knows how to rebuild it?

AWS infrastructure as code

We rebuild in your repository the definition of the existing AWS 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 · Infrastructure as Code

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

AWS 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

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

What stays in your hands

Everything stays with you.

Your AWS account and your code remain yours: resources are created in your account 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 AWS situations when the scope can be clearly defined.

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 AWS account, 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 AWS account?

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 AWS account and the delivered code goes into your repository.

Do you work on site?

99% of our engagements are carried out remotely, throughout France and the Benelux. We travel when the situation requires it.

Do you also work on Azure or Google Cloud?

We work mainly on AWS. Azure and Google Cloud environments can be considered 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.