Inside your own cloud.

The draft never leaves your account. Here is how the design works.

How Enterprise works. Enterprise is delivered through a paid scoping study and pilot, and set up for each client. This page shows the design you would be scoping.

Your cloud accountAWS or Google Cloud, in the region you choose

Pramanex engineSigned container. Reads the draft, runs the checks, the challenge pass and the 99% gate.

Your AI model accountClaude through Amazon Bedrock or Google Vertex AI, in your account. We never see prompts or responses.

Document storeYour draft and the outputs, encrypted with your own key.

Review workbookBehind your single sign-on. Every observation, response and sign-off.

Your finance team, CFO and audit committee chairUpload the draft, respond to each point, receive the report.

Our reviewerGuest access through your VPN or virtual desktop, on your insider list under UK MAR, time-limited.

Law packs, public evidence and engine updates, signed. Your environment asks; nothing is pushed in.

Licence check, run count and the report's fingerprint. Never document content.

Pramanex hubPublic material only

Law packsThe rules for your market, updated monthly.

Public evidenceFilings, announcements and published reports for your licensed entities.

Licence and fingerprint registerWhich entities are licensed; the fingerprint of each released report, for verification.

What stays in your account

The draft annual report, the financial statements, board papers, every observation and the final report. All personal data in them.

What leaves it

A licence check, the number of runs, the engine version and the fingerprint of each released report. Nothing else.

What you keep control of

The region, the encryption key, who can sign in, the model version you enable, and when updates are applied.

A run, step by step

From upload to report, inside your account

Upload. Your team loads the draft into the document store. It does not leave your account.
Evidence. The engine fetches the public filings and the law pack for your entity from our hub.
Read and challenge. The engine proposes observations through your own AI account, then argues the company's side; only points that pass the gate go forward.
Review. Our reviewer checks every point inside your environment; your team responds in the workbook.
Release. The report goes to the CFO and the audit committee chair together; only its fingerprint is registered with us.

Controls

Designed so the result stays independent

Locked method

The engine image is signed and checked before each run; its rules, prompts and thresholds cannot be edited by anyone in your account.

Licensed entities only

The licence names the entities and the term; runs on anything else are refused.

Observations stay on record

Your team can respond to or dispute any point; the workbook keeps every observation and its outcome.

Before a scoping study

What your team would provide

A dedicated cloud account or project in your chosen region, with Claude access enabled in Bedrock or Vertex AI
Your own encryption key, cloud audit logging, and outbound access to two Pramanex addresses only
Single sign-on with multi-factor authentication for the workbook, and a guest route for our reviewer
The NDA, our reviewer on your insider list under UK MAR, and the list of entities to license

Discuss a scoping study

Model availability and data residency differ by region and model, and are confirmed at scoping. Each run records the model and the region used.

Your annual report will be in draft before the year-end audit.
Have it read before it is published.

Under NDA, with our reviewer on your insider list under UK MAR.

Request a proposal Talk to us