Grounded AI for regulated organizations

Answers from your own documents — and an honest "I don't know."

Ansora answers from your materials, cites the source, and stops when the corpus doesn't cover the question. Built for organizations whose documents carry real consequence.

In development · early conversations underway · built in Nova Scotia

How it works

It grounds every answer — and shows its work.

The same discipline in every reply: answer from the documents, mark what carries force, and refuse when the material doesn't cover the question.

01

Answers from your documents

Every reply is drawn from your own materials and cites the source it came from — so a reader can check it, not just trust it.

02

Marks what's binding vs guidance

It distinguishes a requirement from advice and labels which is which. It points to the standard; it doesn't decide what the standard means.

03

Says "I don't know"

When the corpus doesn't cover a question, it declines and says so — rather than filling the gap with a plausible guess.

04

One corpus, two audiences

Staff and the public can be served from the same materials with different visibility — internal guidance stays internal.

How it's built

Principles you can hold it to.

The behaviour isn't a setting that can be switched off — it's how the system is built.

Behind the scenes

Everything you need to run it.

Ansora isn't just the public answer — it's the console your team runs it from. Curate what it knows, set what carries authority, see what it couldn't answer, and keep it accountable.

01

Knowledge base & authority

Curate the documents it answers from, and mark what's binding versus guidance. The authority tag isn't inferred — you set it, and it shows in every answer.

02

People & access

Role-based access with an explain endpoint and a full audit trail — see exactly who can do what, and why.

03

What it couldn't answer

Every question it declined is captured, so you can see the gaps in your own documents and fill them — the assistant tells you where it's blind.

04

Scheduled messages & spend

Schedule outbound messages, and track model spend per tenant against a budget you control.

A short walkthrough of the console. Illustrative — not a real client's tenant.

Who it's for

For organizations where a wrong answer has a cost.

Security & privacy

Built to be evidenced, not asserted.

The promise is that it doesn't overclaim — and that has to hold for how it's secured, too. Full architecture and security documentation is available on request; here's the shape of it.

  • ✓Tenant isolation. Each organization's materials and conversations are isolated at the database level. No client's corpus answers another's questions or trains any model.
  • ✓Role-based access, with an explain endpoint. Permissions are enforced and inspectable, backed by a full audit trail of who accessed and changed what.
  • ✓Encryption in transit and at rest.
  • ✓A documented data path, end to end. Including where model and embedding calls are processed — the part most vendors leave out.
  • ○No SOC 2 yet. We don't hold a SOC 2 report today, and we won't claim one. If that's a requirement for you, let's talk about the timeline honestly.

See it answer from your own documents.

A short demo on your materials — a cited answer, and an honest refusal where the documents don't reach.

Book a live demo