The platform

The whole platform fits under a desk.

Dura OS™ is the software the appliance runs. It reads your documents where they live and answers with citations. It builds workflows in conversation. Every exchange stays on the record. The models inside are tuned for the work of your industry, and they are kept current for as long as the box runs. All of it installed inside your network.

What ships in the box

The full manifest, row by row. Everything on it runs behind your firewall.

Your team asks in plain language, and the answer comes back with its sources attached, drawn from your documents at the moment of the question and cited down to the section. Anyone can check the work, because the citation is sitting right there.

Point the appliance at decades of paper: contracts, filings, scans. Everything is read on arrival, and every file comes out the other side with a summary, the names involved, and the dates that matter.

A query that touches a name raising a conflict of interest draws a warning before the work goes further.

Describe a recurring job the way you would to a colleague. The Architect turns the conversation into a saved workflow, run on a schedule or triggered by events, and nothing goes live until you approve a dry run.

The appliance indexes the systems you already run, in place, wherever the files already live. There is no migration project, and no second copy of the record to govern.

What the appliance remembers is scoped to each user alone. Material tagged sensitive is never remembered at all, and nothing becomes shared knowledge until an administrator has reviewed it.

Your team signs in through the identity provider you already run (OIDC), or with local accounts kept on the appliance itself. Access is isolated down to the database row.

The hardware is ours to keep current. A refresh arrives on a managed cycle, included in the subscription, with no capital event on your side. Obsolescence is our problem.

See it answer.

A three-exchange demonstration of the product surface: a question about client work by name, an answer cited to the section, and a workflow built in conversation.

  • 01 CitedCitations arrive inline, so anyone can check the answer against the record.
  • 02 Permission-awareWho may see what is enforced in the database itself, not in a prompt.
  • 03 On the recordThe audit chain takes every question, answer, and tool call.
Dura OS On your hardware
You
Summarize the termination terms across the three Meridian supply agreements. Do any of them conflict with the 2024 master terms?
Stella
All three agreements allow termination for convenience on 60 days’ notice, but the 2023 renewal adds an early-termination fee.1 That fee conflicts with §11.2 of the 2024 master terms, which bars termination charges of any kind.2 The remaining two agreements incorporate the master terms by reference.3
1Meridian Supply Renewal (2023), §8.4 2Master Services Terms (2024), §11.2 3Meridian Supply Agreements A and B, §7.1
134 tok/s · 6.8s
You
This is the second renewal that has slipped past us. Can you build a workflow that reviews new agreements against the master terms before anyone signs?
Stella
I can. When a new agreement lands in the contracts library, I would check its termination and fee provisions against the current master terms and write up anything that conflicts, cited to the section. Should the check cover every new agreement, or only the supply contracts? And do you want flags as they are found, or in a weekly digest?
You
Every agreement, and flag them as they come in.
Stella
Saved. The workflow runs under your permissions, and nothing goes live until you approve a dry run. I’ve queued one against last quarter’s agreements.
WorkflowMaster-terms review TriggerNew agreement in the contracts library StatusDry run queued for review

The transcript above is staged. Request a private demo to watch a live one.

One number.

One flat monthly subscription, and it is the whole of it. The number moves with the size of the machine you need.

Covered
Everything.
  • The appliance itself
  • The software, with every update
  • Unlimited users on the machine
  • Support, from the people who built it
  • Hardware refresh on a managed cycle
Billed separately
Nothing.
  • No per-seat metering
  • No hardware invoice
  • No refresh charge
  • No capital event, at any point

From delivery to first question

01

Installed inside

The box arrives as preconfigured as you want, from plug-in ready to a bare install your IT completes on site. Dura OS then guides the first run: identity provider, then document sources, nothing routed through us.

02

The record, indexed

Ingestion follows your schedule, and source permissions hold from the very first file. A document can be found only by someone who could already open it.

03

Ask

Your team signs in with the credentials they already carry and starts asking.

Request a private demo