We put AI into production
Building AI is the easy part.
The hard part is your systems. We build inside your own code, on your real data, and we stay on call for what runs. First working system in four to six weeks.
We ship the tests with the system, and every number on this site maps to the run that produced it. How it is measured
Three separate pieces of work, each measured
Each of these comes from a different piece of work: a live system we still run, one cloud estate we audited, and our own security research. None of them is an average across clients. One of them went down. We re-measured the source and published the correction.
The work
Six parts of one system. Only checked work reaches production
- AI agentsSoftware that does a whole job, not one step of it.
- Knowledge and answersAnswers from your own documents, with the source attached.
- AutomationThe same steps every time, done without a person.
- Testing and reliabilityChecks that catch a wrong answer before you do.
- AI securityAI that tries to break code before an attacker does.
- InfrastructureThe cloud it all runs on.
That is the work. Four ways to buy it, each priced before we start.See the four
How it works
It looks the answer up instead of inventing one
Ask a general model what it does not know and it answers anyway. This one looks it up first, and stops when there is nothing there.
- 01
Reads your sources first
Your documents, databases and systems, not what a model picked up in training.
- 02
Answers only from what it found
Every line links to the document behind it, or it says it does not have one.
- 03
Checked before it reaches you
A verifier blocks any claim it cannot trace to a source.
Honest about the limits. Grounding does not make mistakes impossible. It makes them visible instead of silent.
What an answer looks like
Two outputs. One is a refusal, and that is the point
Illustrations of the shape, not client screenshots. The figures are withheld because they would be a client's. The shape is the same whatever the records are.
What did we commit to on renewal terms last quarter?
A figure for every agreement. Each one carries the record it came from. The ones outside the usual range are named, with the reason.
Every figure links to the row it came from.
What will those terms be next quarter?
I do not have that. Nothing in the records is a forecast.
No source, so no number.
The refusal is the harder problem, and the one most systems skip.
Your stack
It runs on the stack you already have.
We build on the models, data and cloud you already pay for. Nothing gets ripped out.
- ClaudeModel
- AWS BedrockRuntime
- OpenAI embeddingsSearch
- Voyage rerankerSearch
- AWSCloud
- PostgreSQLData
- pgvectorData
- FastAPIFramework
No endorsement implied.
Selected work
Real systems, real numbers
Anonymized by default.
Straight terms
What you can count on
We tell you when AI is the wrong tool
You hear it before you spend. Where this shape does not fit is written down, not implied.
You know the price before we start
One price for the build, agreed before it starts, then a flat monthly rate.
You own everything we build
Your code, your license, runnable without us. The test is whether you can end the monthly rate and keep the system running.
Questions
What buyers ask first
What does Ilayer do?
We take one workflow that costs your team real hours and get it running inside your own systems. Then we keep it running. Same engineer, same tests, and a gate that blocks a change that makes the system worse.
How long does a first project take?
A fixed-scope first piece runs 4 to 6 weeks, kickoff to something working on your real data.
What does an engagement cost?
Fixed-scope build, priced before we start, then a flat monthly rate. No open-ended retainers.
How do you stop AI from making things up?
It answers from your documents rather than from memory, shows the source, and says so when the answer is not there. On one live system, every time it said it did not know, it was right to: a score of 1.000.



