Live product · not a mockup
Every entry you just read about is running in this clip inside the real Cibotti app — same staff login, same chain, same Bitcoin anchor.
Staff Entry demo code · GM‑8T3K91
How a single entry gets locked down
You only ever do the first one — type what happened and submit. Cibotti does the rest before the page finishes loading.
The moment it's submitted, Cibotti hashes the entry together with the previous entry's hash. Change either one later and the link visibly breaks.
The latest hash is anchored via OpenTimestamps — automatically, every day. That timestamp isn't ours to alter; it's Bitcoin's.
Run Verify Chain and Cibotti recomputes every hash from scratch, right in the browser. Any edit after the fact throws a flag exactly where it happened.
Entries carry the device and rough location they were made from, so it's clear who logged what, and from where.
Not our word for it
Bitcoin's ledger is the one thing here nobody — including us — can quietly edit.
Full walkthrough
Staff entry, the chain view, Bitcoin anchoring, and the public verify portal — back to back, in the actual product.
Try it yourself →No install · no IT project
Cibotti runs entirely in-browser — staff, managers, and auditors all use the same link.
Cibotti hash-chains every entry your team logs, then anchors it to the Bitcoin blockchain — so any edit after the fact is instantly, publicly detectable. No installs. No IT department. Just a browser.
Each answer below is a real entry, linked to the one before it by its fingerprint. Tap a question to verify it and read the answer.
Email john@cibotti.app and you'll hear back from the founder, not a help desk.
Your team keeps working the way they already do. Cibotti quietly does the cryptographic work underneath every entry logged.
A team member records an event — an inspection, an incident, a delivery — from any browser, no software to install or maintain.
Cibotti generates a SHA-256 hash of the entry, folding in the hash of the entry before it. Any later edit breaks the chain visibly.
On a set schedule, the latest hash is anchored to the Bitcoin blockchain via OpenTimestamps — proof that exists outside our own database.
Everything below runs the moment you're onboarded — nothing to configure, license, or install.
Leadership sees everything. Frontline staff see only their own entries. No middle ground to misconfigure.
Photos and PDFs are folded directly into the entry's hash — tampering with a file breaks the chain the same as tampering with text.
Flags a single login credential used in two places more than fifty miles apart within thirty minutes.
Sensitive entry types require a second confirming signature before status moves from pending to confirmed.
A daily scan watches rolling activity and raises a system-authored alert the moment a threshold is crossed.
Auditors, insurers, and other outside parties can paste a hash into our public portal — no login — and confirm it exists, and exactly when it was recorded. Separate from staff entry.
Anyone outside your organization — an auditor, an insurer, an investigator — can confirm a record's existence and timestamp here, without ever touching your ledger.
Looking to log an entry as staff? Go to Staff Entry →
We'll walk you through a live demo property — no commitment, no install, fifteen minutes.
Request a walkthrough