VolkanaDEV

Sanguis 3.0 · Iteration:Determinism

AI that feels alive.

VolkanaDEV is building AI that remembers everything it learns, and gives the same answer every time. It's written in Sanguis, the language we built for it.

Early Access begins
--Days
:
--Hours
:
--Minutes
:
--Seconds
November 28, 2026

Be patient while we tinker. More info and sign-ups soon.

6.2e-14
how exact its math is, down to the very last digit
30
programs checked. Run any of them again, and the exact same thing comes back.
4.5 ms
how long one whole thought takes, start to finish
0.2 s
one finished answer, about as fast as you react to a surprise

Most software gives you the same answer twice by luck. We do it by design.

The field's answer

Take the same program to a second computer and you can get a second answer. Almost all software has this problem, and it's unsolved across the whole industry. Most tools settle for looking the same.

Ours

We mean answering the same. The same program gives back the same answer on the graphics card, on the software, and on the compiler that builds itself. Every number is a real run you can check.

Sanguis has a twin, meet BloodCode.

BloodCode: 29 instructions. Fixed numbers, fixed spellings, fixed meanings.

Frozen forever

Assigned slots never change. Deprecated ops keep their number. Changing a slot's spelling fails the build.

Any machine can join

A new executor (another GPU, an FPGA, a microcontroller) is admitted by passing one public per-operation test suite. Adding hardware never splits the language.

It's all just text

Artifacts are text. Open one in an editor and read exactly what your program became.

A running program is a file.

Write it out. Pick it back up somewhere else. It comes back bit-identical.

Unplug it

A core writes itself to a small package: its wiring, its weights, its clock. Insert it into a fresh process and it resumes where it was, the same program.

Replay it

Because the settle is deterministic, any behaviour re-runs bit-for-bit years later, on hardware that didn't exist when it was written.

Ask it why

Every result has a computed cause. Debugging stops being an anecdote and becomes a measurement.

If you have to trust it, you should be able to check it.

Check it once, trust it everywhere

Prove a behavior on one machine and the proof stands on all of them, so a single audit covers every deployment.

Software that keeps its word

What passed your tests last year passes them next year, on machines that didn't exist yet.

Move it anywhere

The program is the file. Same sentient instance, desk to bench to rack, nothing lost in transit.

We could sell this to anyone. We wrote a license so we can't.

VPL-1.0

Autonomous weapons, mass surveillance, facial recognition without consent, tools built to exploit people. All forbidden. Break the rule and your license dies on the spot.

Read it, test it, build on it

Open and inspectable for individuals, students, and researchers, and commercial deployment is a conversation.