Back to the overview

AI-native product engineering · How VM8 works

The method and the platform.

One model, short iterations, agents and people. What happens between an idea and a product in production.

01The cycle

Six stages. Every iteration.

DiscoverModelSpecifyBuildReleaseLearn

02One connected model

Knowledge is the source. Documents are views.

  • Domain

    Events, commands, policies and boundaries from Event Storming, one concept each.

  • Specs and decisions

    Every capability specified, every decision recorded with its reason and its alternatives.

  • Traceability

    Issue, spec, code, release: each one points to the next. Nothing is tracked twice.

03Agents and people

Agents do the bulk. People decide.

  • Your product owner

    Owns the why and the what. Approves specs, decisions and releases.
  • Your domain experts

    Bring the language and the rules. Validate the model.
  • VM8 lead consultant

    Runs the method end to end. Facilitates, keeps knowledge consistent, keeps decisions moving.
  • VM8 engineers

    Build with agents on the blocks and the reference architecture. Review every output.
  • Agents

    Propose, model, specify, build, test, review, summarize. Never approve.

04Validated by use

You see it working before it is built.

  • Prototype first

    A functional, high-fidelity prototype of the experience, approved by the people it is for.

  • Validation environment

    Every increment is tried in a real environment against its acceptance criteria.

  • No tools to learn

    You read the knowledge site, review in a browser, approve decisions and releases. No Git, no console.

05The platform

What VM8 brings to every product.

  • 01

    Framework

    The method: domain-first, versioned specs, human approval where it matters.

  • 02

    Knowledge and agents

    The connected model, agents specialized by stage, workflows from discovery to release.

  • 03

    Building blocks

    Identity and access, multi-tenancy, billing, notifications, audit, integrations, observability.

  • 04

    Reference architecture

    A serverless skeleton on AWS: scales to zero, near-zero cost when idle.

  • 05

    Integrations

    MCP, APIs, webhooks, Git, connectors to the tools your team already uses.

  • 06

    Console

    Where your team and ours see the same model, the same progress, the same decisions.

06Where it runs

In your name, from day one.

  • VM8-managed cloud

    WhereVM8's account
    Who operatesVM8 operates
    WhenEarly-stage ventures, teams without infrastructure
  • Your own account, operated by VM8

    WhereA dedicated AWS account inside your organization
    Who operatesVM8, with access you can revoke
    WhenRegulation, data sovereignty, audits, investor due diligence
  • Self-managed

    WhereYour AWS account
    Who operatesYour team
    WhenTeams with their own operations, or after the engagement

Building blocks are delivered as deployable software, infrastructure as code and versioned packages. Nothing at runtime depends on VM8; the product leaves with you.