Skip to content

A practice for production AI

Engineeringfor the terrainof production AI.

Dunes helps teams design, harden, and operate the systems that actually run — inference, platforms, retrieval, evals, and the organizations around them.

Now booking Q4 2026 and Q1 2027 · Diagnostics from $22k

Typically engaged by

  • Applied AI orgs

    who already shipped

  • Platform teams

    who own the paved path

  • Infra leads

    who feel the GPU bill

  • Engineering leads

    who need a second chair

Approach

Map, name, move, leave a trail.

  1. 01

    Map the terrain

    Current architecture, constraints, spend, failure modes, and who actually owns what. We write it down until the picture is shared.

  2. 02

    Name the ridge

    Most programs have one or two moves that change the slope. We name them, sequence them, and kill the rest of the backlog theater.

  3. 03

    Build or bind

    We implement alongside your engineers, or we sit in the reviews while they do. Either way the system moves, and ownership stays with you.

  4. 04

    Leave a trail

    Evals, runbooks, decision records, cost envelopes, named owners. The engagement is done when the path is walkable without us.

Engagement diagnostic

Describe the terrain. We’ll name the engagement.

A few sentences about the system, the pressure, and what “working” would mean. You get a recommended engagement, first moves, and what to watch. Not a sales script.

User-initiated. Kept short on purpose.0/2000

Engage

If the terrain is already real, we should talk.

A conversation, then a written proposal for one package. Diagnostics from $22k. We will say so if we are not the right fit.