Private AI for regulated industries

Own your Intelligence.

An AI appliance installed on your premises, answering from your own documents. Your files never leave your network, and that includes the questions you ask about them.

Ask by name.

Because the appliance runs inside your network, your team can ask about actual client work, by name, with the documents on the table. No anonymizing first, and no cloud provider’s terms of service in the way.

  • 01 CitedAnswers are pulled from your documents at the moment you ask, with inline citations so anyone can check them.
  • 02 Permission-awareRetrieval respects who may see what, enforced in the database itself, not in a prompt.
  • 03 On the recordEvery question, answer, and tool call lands in an audit chain your compliance officer can read.
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.

What ships in the box

One appliance running Dura OS™, delivered and installed. Everything below stays behind your firewall.

Ask in plain language across everything you’ve connected. Every answer cites the documents it drew from, down to the section.

Contracts, filings, and decades of scanned paper. Everything is read as it arrives. Each file gets a summary, the names involved, and the dates that matter.

When a query touches a name that raises a conflict of interest, a warning surfaces before the work goes further.

Describe a recurring job in conversation. The Architect builds it as a saved workflow, scheduled or triggered by events, and shows you a dry run before anything goes live.

Point the appliance at the systems you already run. Files are indexed in place. No migration project, and no second copy of the record.

Memory is scoped to each user alone. Material tagged sensitive is never remembered, and nothing becomes shared knowledge without an administrator’s review.

Single sign-on through the identity provider you already run (OIDC), or local accounts kept on the appliance. Every user’s access is isolated down to the database row.

Hardware is refreshed on a managed cycle as models and machines advance, included in the subscription. The appliance you install is not the appliance you are stuck with.

The boundary is the product.

Instead of promising privacy in a policy document, we build it into the hardware.

Stays on your hardware
Everything.
  • Document text, indexes, and embeddings
  • Models and every inference they run
  • Conversations and memory
  • Identities and access rules
  • The audit chain itself
Leaves your network
Telemetry.
  • Usage totals and latency figures
  • Error rates and version info
  • License status and update checks
  • Never content, a document name, or who asked

And you can prove it. The management plane is pull-only: Dura OS calls out for licenses and updates, and nothing outside can call in. The audit chain is hash-linked and tamper-evident. You can anchor it in write-once storage and export it to your SIEM. Updates arrive signed, on your review terms. Support sessions happen only when you start them, and they land in your audit chain.

From delivery to first question

01

Installed inside

The appliance ships as preconfigured as you want, from plug-in ready to a bare install your IT completes on site. Dura OS guides the first run, connecting your identity provider and document sources without routing anything through us.

02

The record, indexed

Ingestion runs on your schedule. Source permissions hold from the first file, so a document can only be found by someone who could already open it.

03

Ask

Your team signs in with the accounts they already use and starts asking.

Request a private demo

Built where confidentiality is law

At home wherever the files cannot be sent away.

01

Law firms

A matter file that answers questions, with privilege intact and conflicts checked.
02

Financial services & accounting

Client financials and portfolio strategy stay where the engagement letter says they will.
03

Healthcare & life sciences

Clinical documentation, PHI, and trial data never leave the premises.
04

Insurance carriers

Claim files and underwriting notes that stay inside the carrier.
05

Energy & natural resources

Survey data, well logs, and lease terms a competitor would pay to read.
06

Municipal government

Resident records and closed-session files that never leave the county.

One number.

A flat monthly subscription covers the whole of it. The number tracks 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

See it work.

A person replies to schedule it.