Prove
Know what you have — and prove it was right.
A versioned model of what is running, a typed contract of what should be, and a deterministic diff between them.
NeedsRead-only on the cloud
● Where AXON is today
Artinhum builds AXON — continuous cloud operations
Clouds shouldrun themselves.Provably.
The invisible work of cloud operations — checking, reconciling, proving — done by deterministic software, on the record. Not another model to trust: an engine that earns every permission you grant it.
The problem, in one interval
The problem, in one interval
10 months
Backup retention on the main production database dropped from 35 days to 7. A console change during a cost crunch, never ticketed, never reverted — below the company's own stated policy and below what two customer contracts specify.
Found byAn auditor's evidence request, which made somebody actually look.With AXONNext scan — about 15 minutes — against the 35 days you declared.
- 9 daysA WAF rule hand-edited at midnight during a fraud spike also blocked the banking partner's webhook source. Webhooks failed silently, retried, dead-lettered.The partner's integration team escalated.
- 11 daysA firewall rule opened for a customer demo, and left open.An internal review. It reached the VP of Engineering as agenda item four of a monthly steering meeting.
- 5 weeksA contractor attached an inline IAM policy — wildcard actions, `Resource: *` — to a production service role, to unblock himself.The annual pentest. It arrived as a finding in an external PDF.
Four people described a drift they could date. Read the last column of each: a partner's integration team, an internal review, a pentest PDF, an auditor's request. Not one was found by a tool.
One data structure
Two inputs. One comparison. Nothing you have to take on faith.
RunningWhat is actually thereYour estate, read every 15 minutes through a role you create. No keys held, ever.
DeclaredWhat you said should be trueA typed contract, in your own git repository — bootstrapped from what you already run.
ProofA record nobody can quietly rewriteEvery difference, hash-chained and dated. Re-verifiable by your auditor, not by us.
AdaptersAWSGCPAzureGitHubGitLabOktaDatadogMongoDB Atlas
The identifier and the engine are provider-shaped across cloud, identity, source control, database, observability, security, endpoint and collaboration— so a second provider is an adapter, not a rewrite.2 exist today.
Deterministic end to end. No model ever touches your infrastructure.
The vision · four rungs and a surface
The vision: four rungs and a surface
I don't need a person. I need the function — the checking, the reconciling, the evidence, the boring vigilance. A person is just the only packaging I've been able to shop for.
Guard
The bad change never lands.
That same diff, run before the merge instead of after.
NeedsRead, plus a write-scoped token on one git repository
Scheduled from v2.2.0
Fix
What drifted goes back to what you declared.
That same diff, run in reverse — toward a target you already wrote down.
NeedsWrite on the cloud, bounded by the contract
The third major
Operate
The day-to-day, done: build, deploy, patch, rotate.
The same model, driven forward — new decisions, not reversions.
NeedsWrite on the cloud, unbounded, and the tools you already own
After Fix is trusted
Advise
Ask anything about your estate and get a real answer.
A query over the same model. It may reach the engine; it may never be it.
PermissionInherits whatever it fronts
The surface — begins inside Prove
The vision · four rungs and a surface
The vision: four rungs and a surface
I don't need a person. I need the function — the checking, the reconciling, the evidence, the boring vigilance. A person is just the only packaging I've been able to shop for.
Prove
Know what you have — and prove it was right.
A versioned model of what is running, a typed contract of what should be, and a deterministic diff between them.
NeedsRead-only on the cloud
● Where AXON is today
Guard
The bad change never lands.
That same diff, run before the merge instead of after.
NeedsRead, plus a write-scoped token on one git repository
Scheduled from v2.2.0
Fix
What drifted goes back to what you declared.
That same diff, run in reverse — toward a target you already wrote down.
NeedsWrite on the cloud, bounded by the contract
The third major
Operate
The day-to-day, done: build, deploy, patch, rotate.
The same model, driven forward — new decisions, not reversions.
NeedsWrite on the cloud, unbounded, and the tools you already own
After Fix is trusted
Advise
Ask anything about your estate and get a real answer.
A query over the same model. It may reach the engine; it may never be it.
PermissionInherits whatever it fronts
The surface — begins inside Prove
orange — exists in code todaybone — designed or planned, not builtthe first four are a permission ladder; Advise is the surface, and inherits whatever it fronts
The end state, and how it is reached
Autonomy is earned, not switched on.
TodayIt watchesRead-only. AXON can prove what is running — and holds write access to nothing.
NextIt proposesA prepared pull request. A human reads it, and a human merges it.
When you grant itIt actsPer task, revocable, every action ledgered — a permission you give, never a default.
The sentence the product is building toward
“You have approved this exact fix 47 times and never disputed it. Let AXON handle it from now on?”
That prompt is written by your own recorded history. A competitor who didn't keep the record cannot fake it.
In the end, cloud operations is something you grant — not something you staff.
Why it compounds
The moat is time.
Cannot be back-filled
To answer what your cloud looked like on a past date, the record had to be written at the time. A competitor can ship a change feed tomorrow. It cannot ship your last eighteen months.
Gets more valuable daily
Every scan deepens the history that audits, guardrails, remediation and day-to-day operation all draw from. One data structure; each rung is a new way to spend it.
- seq 0genesissystemorg createdprev…hash…
- seq 1provider.connectedpriya@aws · role arn:aws:iam::4471…:role/axon-readprev…hash…
- seq 2repo.connectedpriya@git · contracts/production.cueprev…hash…
- seq 3contract.compiledpriya@prev…hash…
- seq 4scan.completedsystems3.bucket · 48 read · completeprev…hash…
A hash chain is tamper-evident, not tamper-proof.
It proves the record moved to anyone who wrote down a hash earlier. It cannot prove we did not rewrite the whole thing, because anything holding our own credentials could recompute every hash exactly as that button just did. Closing that means publishing the chain head somewhere we do not control — in the design, not yet in the code.
Where we actually are · September 2026
Where we actually are
- Resource types read
- 39
- Services
- 18
- First provider: AWS
- SOC 2 controls wired
- 10
- Keys we can store
- 0
- By construction
- Customers
- 0
- Said out loud
Early, and in the open. The read path runs against real AWS accounts today; everything else is labelled exactly as built, designed, or not started.
Every capability claim, quotation and adapter on this page is checked against our repository before a deploy. It has caught us overstating, and understating, more than once. A company selling proof should be able to prove its own claims.
- Chain verified
- intact · 173 entries
- Period
- 25 – 27 August 2026
- Controls in the pack
- 9 · SOC 2, two with violations observed
- Coverage
- every segment completed, disclosed
- Resource types AXON reads
- 39 · 18 services
- Who changed it in AWS
- not read · CloudTrail absent
- This copy's hashes
- from the original · do not re-verify here
Shipping cadenceevery tagged release, from git tag -l
v0.0.1338 tags · one thing per tagv2.57.3 · 28 Sept 2026
And what does not exist.
Proof we did not rewrite the whole thing
The gap in the paragraph above, named rather than glossed. Chain verification catches an edited entry; it cannot catch a full rewrite, because anything holding our own credentials could recompute every hash consistently. Closing it means publishing the chain head somewhere we do not control, on a schedule. It is in the design, it is not in the code, and it needs a third-party service and a decision nobody has made yet.
Plainly
Four things we are not going to tell you.
A percentage.
Not “99% of drift eliminated”, not “2,000 hours saved”. Nothing has run against a customer estate, so any number we printed would be invented. When we have one it will come from a customer, with their method attached.
That we replace your team.
Two of the people we interviewed run vendor evaluations at their companies. Both volunteered, unprompted, that the replacement framing gets a product quietly killed. We are taking their word for it, because it is their building.
A wall of customer logos.
We have no customers. The people quoted here are interviews, not references, and their names are fictionalised in our transcripts. Every quote is verbatim and traceable — the only proof we have earned.
That it is hands-off today.
AXON reads and reports. It holds write access to nothing, and the ladder above is the honest shape of how that changes: proposal first, permission second, never a default.
It's not role replacement, it's toil replacement. Sell it to me that way and I'll champion it internally. Sell it as replacing my headcount and I'll quietly kill it in the eval — because that req is the only leverage I have left.
Talk to us · thirty minutes · no deck
Talk to us about your estate.
Tell us what is in it and what is inspecting you. We will tell you plainly whether AXON can see it yet — and if it cannot, we will say so on the call rather than in month three.
Design-partner slots · 3 open · September 2026
hello@artinhum.comYes — if it's genuinely thirty minutes, and you show me the evidence output, not a vision deck.