Pilots for engineering teams
Working code.
Or no code.
Your team ships AI-written code every day. Pinull proves each piece against your real environment before it lands. What can't be proven never reaches your codebase.
The first ten teams: a free pilot, then half price for as long as you stay.
Real AI code behind. Real Pinull verdicts in the lens.
One real run
Watch it say no.
Then watch it work.
A model was asked for one small function. Its first try imported a name that doesn't exist. Pinull refused it, sent it back with the reason, and handed over the next try only once every check held.
A replay of a real run. The model's first attempt imported pathlib_module, which does not exist, and Pinull refused it. The second attempt passed every gate and every case of the approved specification, and was handed over.
The problem
It looks perfect.
That's the problem.
AI writes calls and imports that never existed — with total confidence. No reviewer can check every name by eye.
refuted module 'pathlib' has no attribute or submodule 'pathlib_module' — Pinull
How it works
Every line has to prove itself.
Where it fits
Where your team
already works.
- In the editorInside Claude Code, Cursor, VS Code and any tool that speaks MCP. Developers keep their assistant; Pinull checks what it writes.
- In CIOne command in your pipeline. Python that can't be proven fails the check — and the log says exactly why.
- In your productBuilding an AI coding tool? Put Pinull's checks behind it, through MCP or the command line, so your users get code that runs.
Security
Built for code
that can't leave.
- Runs on your machinesPinull runs where your code lives. Your code never reaches Krydia.
- Your models, your keysThe model accounts your team already has — or a model you host yourself, behind an OpenAI-compatible API.
- Untrusted code stays boxedCode under check can run in a locked-down container: no network, a read-only disk, an image pinned by digest.
- No leaks by designA data-flow check stops outside input from reaching a file path or a SQL query, and secrets from reaching a log.
- A passport with every fileWhat was proved, against which interpreter, by which checks — ready for review and audit.
Proof
Measured,
not promised.
323 invented names, planted in real Python code. Not one was passed as real.
0passed as real
- 267 refuted, with the reason
- 54 flagged as unproven
- 2 safely guarded in the code
Each square is one invented name.
false alarms per 1,000 references in Python's standard library
automated tests, each tied to a promise
Real bugs it found in software everyone uses.
Filed by us. Confirmed by their maintainers.
Founding teams
Be one of
the first ten teams.
We're starting with a few teams, side by side with the people who build Pinull.
- A free pilotOn your own code, with your own models. Together we measure what it caught — and what it refused that it shouldn't have.
- Half price, for goodWhen paid plans begin, founding teams pay half for as long as they stay.
- Your roadmapWhat your team needs decides what we build next.
- The founders, directlyNo ticket queue. You talk to the people who build it.
Python today. Tell us what your team writes — it decides what comes next.
Questions
Questions.
What is Pinull?
A checker for AI-written code. A model writes Python; Pinull checks every import, name, attribute and call against the real interpreter your team runs, then the types, the data flow, and tests written from the plan you approved. If something can't be proven, your team gets the reason instead of the code.
What does “working” mean?
That Pinull showed it — not that a model said so. When Pinull writes a file, every import, name, attribute and call has to exist in the Python that will run it, the types have to hold under a strict checker, and every case of the plan you approved has to run and pass. If any of that fails, there is no file. There is the reason.
Does our code leave our network?
No. Pinull runs on your machines and your code never reaches Krydia. When Pinull asks a model to write code, it uses your own model account and key — or a model you host yourself.
How does a pilot work?
We start with one team and one place — the editor, CI, or your product. Pinull runs on your machines, with your models. Each week we look together at what it stopped, and at anything it refused that it shouldn't have. At the end you decide whether it stays.
Which AI models and tools does it work with?
Any model behind an OpenAI-compatible API — we use Gemini, Mistral and open models on Groq every day. Pinull works inside Claude Code, Claude Desktop, Cursor and VS Code, and from the command line, so it fits a CI pipeline too.
Which languages?
Python, done properly, first. Tell us what your team writes: it decides what comes next.
How much will it cost?
Pilots are free. When paid plans begin, founding teams pay half the regular price for as long as they stay. We'll agree prices with you before anyone pays anything.
Can I use Pinull on my own?
Yes. The developer beta goes on, in small waves. Leave your email and we'll invite you.
Who makes Pinull?
Krydia. Wisdom and Wonder.