Software Pre-Reality
Don’t just test the software.
Let a world happen to it.
ReadyForUsers puts your application through reality before your customers do. Realistic users browse, buy, cancel, collide, retry and abandon, and push your software into conditions ordinary tests never reach.
You don’t get another test report. You get proof of what breaks.
- Signed receipt
- Read-only witness
- Invented evidence: 0
An illustration of the method, not a live run. Every real figure on this site comes from a signed receipt.
Three solved runs
Real collisions, real verdicts, every figure from a signed receipt or a proof file.
Two sessions of one wallet owner charge the same last credit at once.
A 0→56 ms, B 1→60 ms, both HTTP 200. available_cents 2000 → -2000. 5 executed · 3 CONFIRMED · 2 REFUTED.
Two buyers check out the last unit of one listing at once.
Two buyers, one unit. inventory 1 → -1. 1/1 confirmed, signed and verifiable in your browser.
ERC721Consecutive, advisory GHSA-878m-3g6q-594q: broken on v4.8.1, held on v4.8.2.
balanceOf = 0 while ownerOf names one token; after transfers the balance wraps past 4 tokens. Broken on v4.8.1, held on v4.8.2.
How it works
One app in. A world hits it. Proof comes out.
State changes. Transactions overlap. Unexpected behaviour meets real software.
- Recording
- Logs
- Network
- Actor Timeline
- State
- Reproduction
Here is why it matters.
Here is how to reproduce it.
Watch · 1 min 51
What “ready for users” actually means.
Some bugs require a crowd
One user can pass every test.
Two users can break the system.
A single testing agent tests a path.
ReadyForUsers tests a world.
What you get
Failures with proof attached, ranked by what they would cost you.
Every incident arrives with the recording, the network calls, the logs and the actor's own timeline. Nothing asks you to take our word for it.
Ranked by users at risk and money exposed, not by how loudly they failed. A cosmetic break never outranks a duplicate charge.
Two buyers on one listing. A seller editing stock mid-checkout. Failures that need several users at once, which a single test session can never produce.
The exact failure replayed many times with conditions held constant, so an intermittent bug stops being a matter of opinion.
Reproduction, evidence, likely root cause and regression risks, packaged for Claude Code, Codex, Cursor or GitHub. Provider-neutral, so switching costs you nothing.
We rerun the original failure, its neighbours and the regression set before anything is called fixed, and tell you plainly when it isn’t.
Not every failure matters. These do.
- Duplicate payments.
- Oversold inventory.
- Double bookings.
- Permission leaks.
- Lost state.
- Broken critical workflows.
For the guided first pass we run a copy of your app, from your repository or a container image you give us access to, in our own isolated environment. Production is never touched. Pointing runs at your hosted staging URL is on the roadmap, and will require proving you own the environment.
The copy of your app runs with its own seeded database, and an independent witness reads that database before and after. It never writes. If it cannot read what it needs, the verdict is UNVERIFIABLE, not a guess. A read-only witness on your own staging database is on the roadmap.
The population signs in as test identities created for the run, each with its own session. No real user's session or data is touched.
Before a guided pass we agree the starting state together, for example "listing X has one unit left", and seed the copy with it. The witness records before-state, the run happens, the witness records after-state, and you get the difference in the receipt. The copy and its database are thrown away after the run.
We build a model of how your application works: screens, workflows, shared resources, invariants. It aims collisions at the places two users can actually compete. It never clones your code, data, or environment.
The copy of your app and its database are destroyed when the run ends. Our hosted runs add a dedicated machine with deny-by-default egress; hosting your app that way is on the roadmap.
Hosted runs against your own application are guided by our team today. Self-serve connect is on the roadmap. ROADMAP
The hard boundary
Live payment keys are rejected by the executor even if present in your configuration.
Destructive verbs are unavailable on production regardless of the credentials supplied.
Concurrency on production is capped far below your capacity and is not configurable upward.
Now auditing smart contracts
The same method, pointed at a contract. ROADMAP
A contract is deployed to a local development chain that ReadyForUsers starts and destroys, never a live network or a public testnet. Throwaway test wallets send the transactions, including two in the same block, and a read-only witness takes a ledger snapshot after each step. Invariants drawn from the standards, ERC-20, ERC-721 and access control, are checked against every snapshot, and a second fresh node must give the same answer before anything is called confirmed.
- Local development chain on loopback only
- Read-only witness; the audit never writes to a contract
- Invariants from EIP-20, EIP-721 and OpenZeppelin AccessControl
- Reproduced on a second fresh node before a verdict
Contract targets are not part of Founding Access yet, and auditing a deployment you do not own needs written authorisation.
Known answer · advisory GHSA-878m-3g6q-594q
Validated against a published OpenZeppelin advisory: broken on v4.8.1, held on v4.8.2. Play it on the reality run page.
Built for the AI software era
Don’t give your coding AI a bug report. Give it the failure. ROADMAP
Repair
ReadyForUsers turns incidents into evidence-backed repair packages your coding AI can act on. Claude Code. Codex. Cursor. Your own engineering agent.
Models reason. Reality decides.
Prove
Your AI says it’s fixed. We make it prove it: the failure is recreated and the repair is tested against the conditions that exposed it.
Execution is the proof.
FOUNDING ACCESS · on sale now
Put your app through reality now.
Guided early access: our team runs your first reality pass with you within 2 business days. Founding pricing locked for 12 months.
Billed at $499/month through Stripe. Cancel anytime. Full refund of the first month within 14 days if no reality pass was delivered. Nothing on the roadmap is billed as live.
Your AI can build it.
Make it survive us.
Connect your application. We’ll bring the users, the collisions and the evidence. Your coding AI repairs what matters, and ReadyForUsers proves whether it worked.
Before your customers ever have to.
