# Your living operating model

AI-native operations

The future of work is humans + agents. DNA is the structure and engine behind it.

[Join the waitlist](https://dna.codes/waitlist)

[Playground](https://dna.codes/playground)

Operations

## One core. Every surface it reaches.

Operational DNA

Live demo

Model it

### [Knowledge in. Operating model out.](https://dna.codes/operations)

Meeting notes, docs and tribal knowledge compile into a living spec, and the runbooks, SOPs and agents your team actually runs on. Every surface below runs on it.

The Operational DNA output panel showing a generated process flow: welcome email sent, intro call booked, product walkthrough and a 30-day check-in, each with its owning team and timing.

[Try the demo](https://dna.codes/operations)

UI Operations

Early access

Govern it

### [Operational controls, in your app.](https://dna.codes/ui-operations)

The same model, reaching into your product. Every button carries the operation it performs, so who may press it, whether it is on, and everything it has done are answered on the control itself.

The Overlay panel docked beside a running application, answering for a refund button with its address, the operation it performs, who may press it, and a note that every refund is now recorded.

[Open the Overlay](https://dna.codes/ui-operations)

API Operations

In design

Govern it

### [Add operational controls to your API.](https://dna.codes/api-operations)

The same model, at your API edge. Every endpoint carries the operation it performs, so who may call it, whether it is on, and what it recorded are answered from your own OpenAPI document.

[Read your own spec](https://dna.codes/api-operations)

Agent Operations

In build

Run it

### [An agent is an actor. Govern it like one.](https://dna.codes/agent-operations)

The same model, handed to your agents. Each holds the operations you granted it, under the policies you already wrote — and what it may not do, it hands to a person instead.

[See it run](https://dna.codes/agent-operations)

CLI Operations — the same controls around the commands your team runs — is planned.

Partners

## Working with design partners across three domains

Legal

Media & content

Fractional ownership

Building at the intersection of operations and engineering. One shared model across disciplines.

## Bring order to your ops.

Encode your processes. Give your team a single source of truth.

[Join the waitlist](https://dna.codes/waitlist)

[Explore the products](https://dna.codes/operations)

## Also on this site

- [dna.codes](https://dna.codes/)
- [Pricing](https://dna.codes/pricing)
- [SOP Software](https://dna.codes/sop-software)
- [Target Operating Model](https://dna.codes/operating-model)
- [Business Process Software](https://dna.codes/business-process-software)
- [Documentation](https://dna.codes/docs)
- [Blog](https://dna.codes/blog)
- [Building With AI](https://dna.codes/building-with-ai)
- [About](https://dna.codes/about)
- [Contact](https://dna.codes/contact)
- [Terms](https://dna.codes/terms)
- [Privacy Policy](https://dna.codes/privacy)
- [Getting started](https://dna.codes/docs/getting-started)

## For agents

- [llms.txt](https://dna.codes/llms.txt): index of docs, products, genomes, and the pages below.
- [SOP Software](https://dna.codes/sop-software): procedures that stay tied to the work, including a small team that has outgrown a wiki. The page shows the procedure as a running SOP.
- [Target Operating Model](https://dna.codes/operating-model): roles, processes, rules, and systems on one board.
- [Business Process Software](https://dna.codes/business-process-software): living business processes, as a diagram of steps, roles, and work. DNA is not a BPM engine.
- [Business Process Modeling with DNA](https://dna.codes/blog/business-process-modeling): a workflow of states, operations, and policies. Notation leaves it in a diagram. Management leaves it in slides.

Your business has a unique DNA. Time to run on it.