TRUSS Binari Digital

Software you describe, instead of software you rebuild

Write down how your business works. TRUSS runs it.

Think of a board game where the rules are printed on a card, not glued inside the box. Swap the card, and the same box plays a whole new game.

TRUSS is the box. You write a short description of your world — the things you keep track of, and who is allowed to see or change them. TRUSS reads it and starts working. No new software. And from that moment, everything anyone does is written down, for good.

  • 7rules we never break
  • 1way anything can be changed
  • 1computer runs the whole thing

01  /  How it works

You change the description. You never change the software.

  1. Write it down

    List the things you care about — customers, orders, cases, vehicles, whatever your work is made of. Say what facts each one holds, who may look, and who may change. It is a file you can read, not a program.

  2. Publish it

    TRUSS takes a fingerprint of that file. From then on, that version can never be quietly edited — change one letter and the fingerprint no longer matches.

  3. Switch it on

    Choose which version your team works with. That choice is written down for ever. If you need to go back, you switch forward to the older version — so the history shows you changed your mind, instead of pretending it never happened.

  4. That is the whole job

    Nothing was rebuilt. Nothing was redeployed. A second team, or a second customer, is just a second description — not a second system to look after.

02  /  The seven rules

These are the product. Not the small print.

“If a change breaks one of these rules, it is wrong — even if it works, and even if someone asks for it.”

  1. One door in

    There is exactly one way to change anything. Not a main way and a quiet back way. One. So there is only ever one place to look.

  2. Your world is a document, not code

    Your things and rules live in a file anyone can read. The software itself knows nothing about your business, which is exactly why it can run anyone's.

  3. One place decides who may do what

    Every look and every change asks the same question to the same referee — whether it is a person, another program, or a robot. Nobody gets a special pass.

  4. Nothing happens quietly

    Every change announces itself at the very moment it is saved. The record of what happened and the thing that happened cannot drift apart.

  5. You can always rebuild the answer

    Everything you see is worked out from the original record of what happened. Delete the summaries and TRUSS rebuilds them. The history is the truth.

  6. Every fact remembers where it came from

    Each piece of information carries who put it there, when, and where it came from. So “why does it say this?” always has an answer.

  7. Robots suggest. People decide.

    An AI can propose a change but cannot approve its own. The database itself refuses — which is what makes pointing a robot at real work a plan rather than a gamble.

03  /  Three things nobody else publishes

Where we go further than the system we learned from.

TRUSS is our own build of the same idea behind Palantir Foundry, and we will say the honest thing first: they have far more features than we do. But three parts of TRUSS have no equal anywhere in their public documentation, which we read end to end.

i

A history that cannot be rewritten without showing it

Every event is chained to the one before it, like links you cannot re-forge. Change an old link and every link after it stops matching.

Here is the part that matters. Your auditor writes down where the chain had reached last March and keeps that note themselves. Later they ask TRUSS: is my note still true? Someone with full control of our database could delete history and tidy up perfectly after themselves — and still fail that question, because they cannot reach into your auditor's pocket.

ii

“Two people must agree” — enforced by the database

Whoever suggests a change cannot be the one who approves it. That is not a setting, a checkbox, or a rule written in our software that a clever person could route around.

The database itself rejects it, and names who tried. Turning it off would mean rebuilding part of the database on purpose — something you cannot do by accident at two in the morning.

iii

It tells you what will break, before it breaks

When you change your description, a machine compares old and new and says plainly: this is safe to add, or this will break things.

Not a colleague's opinion at six o'clock on a Friday. And permissions only ever tighten: you can add a restriction, never quietly remove one — so a change can never accidentally show people more than before.

04  /  While it is running

What TRUSS is doing every second.

It asks permission first

Before doing any work, TRUSS checks whether you are allowed. Not afterwards — so a refusal never accidentally reveals that the thing you asked about exists at all.

You are shown only your rows

Your permissions are part of the question we ask the database, not a filter we apply to the answer. And where something is hidden, the gap is shaped so you cannot work out what was in it.

Approvals can wait for days

Some work needs a human to say yes. That step can wait as long as it needs to, and survives restarts, upgrades and everything else. It picks up exactly where it left off.

Your own code, still under the rules

You can plug in your own logic. It runs outside TRUSS — but it is checked and recorded like everything else. Your code does not get to stand outside the rules.

05  /  Ways to work with us

Five shapes, smallest first.

T0 Foundation
One team, one description, one computer. Try the whole idea on your own work before anyone signs anything.
T1 Team
For a team past its first description: a place to practise and a place that is real, kept apart, and someone to call.
T2 Enterprise
More machines, each customer kept properly apart, log in with your company account, a promise about uptime, and an engineer who knows your world by name.
T3 Sovereign
Runs in your building, even with no internet at all. Priced per site, because a meter that phones home is not an option here. What you are really buying is proof: an outside auditor can check the history themselves.
T4 ISV
Put TRUSS underneath your own product and ship your world as descriptions.

No prices on this page. We have not settled them, and a number we would have to take back is worse than no number. One promise we will make now: looking at your own data will be near-free, and being told “no” will cost nothing at all. Nobody should ever have a money reason to weaken a safety rule.

06  /  Getting in

There is no sign-up button, on purpose.

TRUSS is early. Every deployment so far started as a conversation about one specific problem. So tell us what you keep track of and what keeps going wrong — that is a far better first message than a form.

Talk to us legal@binari.digital