Skip to content
Limina Labs
Start free
Intent Studio Precepta Pricing Company Contact us Start free

Precepta · In development

Every AI request your company makes, under your rules.

Precepta is the AI governance product we are building. It is designed to sit in front of every model a company uses, so each request is checked against the company's rules, stripped of anything sensitive, sent to the right model and written down. It is made to run on your own servers, so nothing leaves.

Precepta is in development, and is not available yet. This page sets out what we are building and why. Email us to hear when the first version is ready, or to tell us what your company would need from it.

The problem

Three things that stop an AI pilot becoming production.

Your data

It leaves the building

Every call to an outside AI service takes your data somewhere you cannot see.

Governance

No consistent rules across teams

Each team writes its own limits into prompts, which the AI can be talked around.

Evidence

No answer when the auditor asks

What was asked, what the rules said, what the AI saw: none of it can be pieced back together.


How it is designed

One fixed path. What happens on it is yours to set.

Every request takes the same checked path, before and after it reaches a model. There is no way round it, so a rule set once holds for every team and every tool.

Firewall → Sensitivity → Policy → Smart Route → Cache → Inference → Audit

Policy

Hard limits

Which models each team may use, and how much it may spend. The limits sit outside the model, so it cannot talk its way around them.

Data

Sensitive data hidden

Personal data is removed before a model sees the request, and the answer is checked for leaks on the way back.

Record

A record that cannot be quietly changed

Each request, the decision taken on it and the answer are written down and linked, so you can say what happened months later.

Boundary

Nothing leaves

No public route, no telemetry, no phone-home, and checks that the way out really is closed.

Models

Smart routing

Ask for auto and the request goes to the best model available for it, weighing quality, cost and speed.

Interface

Change one line

It is designed to speak the OpenAI API, so existing code would point at it by changing an address. Nothing else.


The cost side

The same place that checks a request can make it cheaper.

Anything that sees every request can do more than check it. Being in that path is what will let Precepta bring the bill down too.

Picking the model

Not every question needs your most expensive model. Auto is designed to send each one to the cheapest model that can answer it well.

Answering repeats from memory

A request answered before would be served from cache, so you do not pay to run it again.

Holding the ceiling

Every key is to carry its own scopes and spending caps. Nobody finds out about a runaway job from the invoice.


Where it runs

On your own servers.

Precepta governs the boundary, so it has to sit inside it: in your cloud account, your data centre, or a network with no outside connection at all. Nothing reaches us.

Who it is for

CIOs, CISOs and platform teams.

The people who have to answer for what the AI touched, and who already own the servers it should run on. It is designed to govern any agents a company runs, Intent Studio's included, without needing them.

Why we think limits belong outside the model →


Hear when it is ready.

Email us and we will write when the first version of Precepta is ready. If your company has a governance problem it should solve, tell us about it: it shapes what we build first.