dataonaws
— How we work

Forward deployed, from the first day.

We don't advise from a distance. We join your team, work in your AWS account and your repositories, and stay until what we built runs in production and your engineers own it.

Who's behind dataonaws

Ex-AWS. Deep experts.

Data architects, AI engineers, DevOps engineers and solutions architects. We spent years at AWS with its most demanding customers, on critical systems running at scale, where security was never optional. We now do the same work from the customer's side, accelerated by the blueprints and artefacts we built along the way.

50+projects shipped
100%hands-on: everyone on an engagement builds
9industries, from banking to energy
  • Banking
  • Insurance
  • Payments
  • Media
  • Luxury
  • Retail
  • Energy
  • Manufacturing
  • Software

Data architects

Data platforms on AWS, Snowflake and Databricks, from the lake to the warehouse.

  • Lakehouse, Iceberg, Lake Formation
  • Glue, EMR, Redshift, Athena
  • Data cost optimisation & performance

AI engineers

Agents and generative AI in production, evaluated and guarded.

  • Amazon Bedrock, AgentCore
  • RAG, evaluation, guardrails
  • Coding agents at scale

DevOps engineers

Delivery that holds at scale: pipelines, observability, on-call that sleeps.

  • CI/CD, infrastructure as code
  • Observability, incident response
  • Automation of the run

Solutions architects

The foundation underneath, designed for scale and security first.

  • Landing zones, IAM, networking
  • Security & compliance by design
  • Multi-account, regulated environments
Accelerated byBlueprints and artefacts built from what worked, and what broke, across our customer projects. We don't start from a blank page.
The model

Three rules we never bend.

01

Inside your team

We join your rituals, your channels and your code reviews. Your engineers work next to us, not after us.

02

In your account

Everything is built in your AWS account and your repositories from day one. Nothing to migrate when we leave.

03

Remote or on site

We work fully remote or embedded with your team, in English or French. Most engagements mix both.

An engagement, step by step

From first call to handover.

1Day 0

Discovery call

30 minutes on your context and what is blocking.

2Days 1–3

Discovery

Stack, code, data and the people who use them. A first-impressions memo within 24h.

3Week 1

Architecture proposal

Costed, argued, trade-offs written down. You decide what we build.

4Then

Build

Short fixed-scope iterations, demoed every week, by the people who did the discovery.

5At the end

Handover

Runbooks, a recorded walkthrough, and your team running it without us.

What you keep

Everything we build is yours.

The code

In your repositories, under your licence, from the first commit.

The platform

Infrastructure as code in your account. No dependency on us to run it.

The decisions

Architecture records explaining why each choice was made.

The know-how

Pairing and walkthroughs, so your engineers can extend it.

Questions buyers ask

Before you book a call.

How long is a typical engagement?

Most start with a one-week discovery and architecture proposal, then a build of four to twelve weeks. Some clients keep one of us afterwards for a few days a month.

Fixed price or time and materials?

Discovery is a fixed price. The build is either fixed-scope per iteration or time and materials, depending on how well the scope is known. We tell you which one fits after the discovery.

Who owns the code?

You do, from the first commit. Everything lives in your repositories and your AWS account.

Do you only work on AWS?

AWS is where we are deepest. We also work with Databricks, Snowflake, dbt and the coding agents your teams already use, as long as they run on or next to AWS.

Do you resell licences or take commissions?

No. We are independent and paid only for our work, so our recommendations are not tied to a vendor.

Can you work with our security constraints?

Yes. We work with least-privilege access in your accounts, follow your review and change processes, and are used to regulated environments.

Let's look at your context. 30 minutes.

Book a discovery call →