Skip to the content

Client knowledge, kept in your hands

The latest with every client. With the source for every statement.

AscertAIn reads what your company already knows about a client, across mail, meetings, tickets and code, and answers one question: what is the latest? It runs on your own machine, and your content never leaves it.

Acme Corp

What is the latest? As of 16 Nov 2026, 09:40.

Call on 11 Nov. Agreed: a revised statement of work by 18 Nov, and testing moved to 24 Nov.

Meeting

A follow-up on 12 Nov asks to confirm the test environment. No reply is recorded.

MailExternal author

Two high-priority issues are open. One has been unassigned for three days.

Tickets

Three changes for the next release are waiting on review or merge.

Code

Built from 14 items in 4 systems. Mail and meetings from 5 of 6 team members; one is not connected. An illustration, with invented data.

The answer

One question. One answer you can check.

Ask about a client and get a situation report: the latest contact, what was agreed, what is open and what is waiting. Nobody has to go looking, and nobody has to take it on trust.

The whole relationship

Mail, meetings, tickets and code are read together, so the report reflects everything your company knows and not one person's inbox.

Cited, or not said

Every statement carries a reference to the item it came from. A statement that cannot be traced to a source is left out.

One step to the original

A reference opens the original in its own system, under that system's own permissions.

Clear about its coverage

Each report says what it was built from and who is not connected, so you know what it could and could not see.

Your machine

Your content stays where it already is.

A tool that reads your mail usually asks you to send your mail to it. AscertAIn is built the other way round: it comes to your content, and stays there with it.

  • It runs where you run it.The whole product runs on a machine you control, inside your own network.
  • We never see your content.We look after licences, releases and the health of installations. Content, summaries, questions, answers and names never reach us, in any form.
  • Nothing listens to the internet.Your installation makes one outbound connection to us and accepts none. It is reached from your network, through whatever you already use.
  • Nothing about your usage leaves.What comes back to us is a short list of fixed health codes. There is no field in it that could carry a sentence.

Your content

Built to keep less.

The safest copy of a sensitive message is the one that was never made. AscertAIn is designed around what it does not keep.

Read-only, permanently

AscertAIn reads your systems and cannot change them. It asks for read access only and has no operation that writes.

No original text is kept

It keeps short summaries, facts and events, each tied to its source. Original text is not stored, and neither is any quotation from it, however short.

Screened on your machine first

Every item is screened locally, with no outside call, before anything else is done with it. What your policy excludes is discarded, not hidden.

A policy you can only tighten

A default policy defines what counts as sensitive. You can add to it, and nothing can loosen it. Legally privileged content is always discarded.

People see what they may see

Access is decided in the database, before any model sees a row. An answer is built only from what the person asking is allowed to read.

Every question on the record

Who asked, what was asked and which items were used are written to an audit log on your machine that can be added to and never changed.

Your model

Your model, your key.

AscertAIn calls only the model endpoint you choose, with a key you hold. We never see the key or the traffic.

  • Hosted, or entirely your own.Use a hosted model under your own contract, or a model on your own hardware, where content goes nowhere at all.
  • The right model for each job.Sorting, extracting and writing can each use a different model, so most of the work goes through the least expensive one.
  • The groundwork stays local.Screening, indexing for search and ranking run on your machine, on ordinary processors, whichever model you choose.
  • Tested before it is trusted.A model is run against an evaluation set before it is given a job, and one that fails cannot be put in charge of sorting sensitive content.

Getting started

Adopt it at your own pace.

You decide what is read, see what would be kept before anything is, and switch each source on when you are satisfied.

  1. Connect a source, read-only

    Start with the least sensitive systems. Each source has its own credential and can reach that system and nothing else.

  2. Watch it in shadow mode

    A new source runs with nothing made searchable. You see how much would be kept and discarded, with samples of each to review.

  3. Set scope and policy

    Narrow what is read and add to what is excluded until the samples look right to you.

  4. Switch it on, and ask

    Your people ask about a client and get a cited report, built only from what each of them may see.

Updates

No surprises in what runs on your machine.

Software that sits beside your client knowledge should not change without you knowing. Here it cannot.

Signed, or refused

Every release and every change of configuration is signed. Anything unsigned, altered or out of date is refused by your installation.

A window to look first

A new release is staged, not applied. You have a window to review it, seven days by default, and we cannot skip it or force an update.

Withdrawn or rolled back

A release withdrawn during the window never runs. One that fails its health check after it is applied is rolled back.

In development, and built to be trusted.

Early access will be by conversation.

AscertAIn is being built now. If this is how you would want your client knowledge handled, this page is where the way to reach us will be published.