VORYNINTELLIGENCE Start a conversation→
Scroll
Australian-built · Australian-operated

AI systems built for your domain, running on your hardware.

Voryn Intelligence writes down how your work is actually done, builds a system to that model, and proves it against your own records before anything goes live. Your data stays on your machine. Nothing is committed without a person.

Start a conversation→ See the method
Runs onHardware you own
ModelsOpen-weight, pinned by hash
Goes liveOnce your acceptance bar is met
How every build is held to account
ONTOLOGY FIRST EVIDENCE-GATED NO OUTBOUND DATA AT RUN TIME HUMAN COMMITS
01 · Method

Ontology first. Evidence at every gate. Hardware last.

Most AI projects start with a model and bend the work to fit it. We start with the work. The model is fitted to your domain; your domain is never bent to fit a model.

Entities · operations · refusal rules
Every gate is scored against the same frozen set of your real records. A step that does not pass goes back into the build, and the errors that remain choose what changes next. Model size and hardware are decided only once the scores have settled.
→ ONTOLOGY

Write the domain down

Every build starts with your vocabulary, rules and decisions, written as a formal model: the entities you deal with, the operations performed on them, and the cases where the answer must be no. It is confirmed line by line with the people who do the work.

→ GATES

Score every step

We build a frozen, labelled scoring set from your own records. Work moves through gates, and each gate is scored against that set. What the scores show decides the next build step, not a roadmap written in advance.

→ HARDWARE

Size it from the evidence

Model size and hardware are the last decision. They are sized from the errors that remain once the method has done its work, so the machine fits the problem rather than the other way round.

02 · Guarantees

What the system will not do.

These are commitments, not settings. They are tested at every gate, and a build that breaks one does not pass.

The system proposes · a person confirms
01

It will not guess.

Where an input is ambiguous, conflicting or missing a value, the system stops and asks a specific question. It does not fill the gap.

02

It will not act on the wrong target.

Attaching work to the wrong record, or missing a request altogether, are hard gates. A build that does either is not released.

03

It will not apply your standards on its own.

Your firm's standards can be offered as suggestions. They are never applied without a person confirming them.

04

It will not commit without a person.

The system proposes. A named person confirms with one action. Anything that carries a compliance obligation always needs a human tick.

05

It will not write to your systems unseen.

Nothing reaches your systems until a person has confirmed it, and every confirmation is logged against the person who made it.

03 · Deployment
RUNS ON · YOUR HARDWARE
Your data stays on the machine you own.

Every system we build runs on hardware the client owns, using open-weight models. No client data is sent to an outside model at run time. There is no shared service in the middle, and no other client's data anywhere near yours.

◆ NO OUTBOUND DATA AT RUN TIME
01

Client-owned hardware

The system runs on a machine you own and control, on your premises or inside your own environment.

02

Open-weight models, pinned by hash

Every model is identified by the hash of its files. What was tested is exactly what runs, and any change is a deliberate, recorded event.

03

A data boundary per client

Each client's data sits inside its own boundary. Client records are never used to train or fine-tune a model, and are never placed in a searchable index.

04

A logged approval for every new source

A new data source enters the boundary only with an approval that is recorded, dated and attributable to a person.

05

Mapped to the ISM

Controls are mapped to the Information Security Manual, with an IRAP pathway for engagements that need one.

04 · Where it applies

One method. Different domains.

Anywhere the work arrives as documents and correspondence, and a person has to decide what it means. The method does not change between sectors. The ontology does.

A

Professional services correspondence

Drafting and construction amendments.

B

Finance and mortgage broking

Applications, lender requests and supporting documents.

C

Real estate and property management

Tenancy, maintenance and sales correspondence.

D

Shipping and freight logistics

Bookings, amendments, manifests and customs paperwork.

E

Public-sector operational intelligence

Records and recorded speech, on the agency's own terms.

F

Secure-facility call transcription

Single-tenant, on agency-owned hardware.

Also suited to
Insurance claims Legal practice Accounting and bookkeeping Trades and field service Strata and body corporate Recruitment Healthcare administration
05 · Engagement

Scoped, gated, and live only when it has earned it.

You see the scores at every gate. You decide whether the bar has been met.

→ SCOPE

Agree the build up front

We agree the domain, the gates and the acceptance bar before any build work starts.

→ SCORING SET

Draw it from your history

We assemble and label a set of your real past records, then freeze it, so every gate is measured on the same ground.

→ GATES

Build in the open

Each step is scored and reported to you: what passed, what did not, and what changes next.

→ GO-LIVE

After the bar is met

The system goes live once it meets the acceptance bar you agreed, on your own records. Not before.

◆ THE ACCEPTANCE BAR

Set with you at the start, measured on your records, and not moved to suit the build.

Get in touch

Tell us about the work you want a system for.

Five questions to start. If it looks like a fit, ten more help us scope it before we first speak.

→ Each question maps to a step in the gated method
→ We will tell you plainly whether the method fits
→ No obligation, and treated in confidence
Step 1 of 2The essentials
About you
The problem
Roughly how many items a month? * Emails, calls, documents or forms
Your data
Where do the records live? * Tick all that apply
Constraints
Must the data stay on your own premises or hardware? *

By submitting, you agree to our Terms and consent to your details being handled per our Privacy Policy. Submissions are treated in confidence and never shared with third parties.

✓

Enquiry received

Thank you. We will reply by email to arrange a conversation.