Your activity,
your starting point.
A sales history is what makes repayment capacity estimable. The proposal starts with CSV files and the business's own books.
Turn your sales into working capital. Take the financing, and pay it back little by little with every new sale.
Built for Solana · Settled in USDC · Powered by real cash flow

Try how a business's data turns into financing, and how its sales carry it back to the pool.
INTERACTIVE PROTOTYPE · NO REAL FUNDSYour next chapter starts with your sales.
See how much capital this business could receive from its sales history.
Pick a tranche and simulate your contribution to the pool.
You don't have a simulated position yet.
These rates are presentational assumptions, not observed or guaranteed returns. Senior can lose capital too.
Liquidity available in the pool
The business's repayments update the liquidity and the fees earned in this simulation.
A standalone scenario: a 7,000 USDC-dev loss hits Junior first, then the reserve, and finally Senior if that is not enough.
Capital that absorbs the first loss.
An extra backstop, represented here in the demo.
Touched only once the other layers are exhausted.
An illustrative reserve; there are no real RWA assets held in custody.

Buying inventory. Getting the next order ready. Keeping the business moving.
Caudal ties that growth to what your business already produces: its sales.
Explore the business example ↗A sales history is what makes repayment capacity estimable. The proposal starts with CSV files and the business's own books.
Revenue, variation and trend inform a conservative limit. The proposed AI normalises the data; the rules bound the result.
A pool funds the advance in USDC. Two tranches spread the risk and the payment priority among those providing the liquidity.
A fraction of each payment repays principal and fee. The rest stays with the business, and the capital goes back to the pool.
Your repayment share is set by what actually moves through your button. Sustain the flow you were underwritten on and it stays where you agreed. Divert it, and it adjusts — on its own, inside limits fixed the day you drew.
AUTOMATIC · BOUNDED · ON THE RECORDThe rate you agreed. Nothing moves while your button carries the sales your limit was written against.
Sales stop arriving through the button. The share steps up once per period — never further than the ceiling frozen at disbursement.
A thermostat, not a ratchet. When the flow comes back, the rate walks down again to where it started.
What is being protected is not a good month — it is the stream itself. A merchant who routes sales to a rail Caudal cannot see has quietly removed the collateral. That is what the covenant answers, and it is why it measures transactions through the button rather than revenue in general.
A ceiling on the share, a ceiling on how far it can move in one period, a grace window after disbursement, and a floor on what you keep: never less than 65% of any sale. The ceiling is frozen the day you draw, so a later policy change cannot reach a loan already written.
No call, no renegotiation, no discretion. The same deterministic curve runs for everyone, and the ceiling is enforced by the contract and the database as well as the code — three independent statements of the same limit.
Each adjustment is written with the period it measured, the flow it observed and the baseline it compared against, to a record neither side can edit afterwards. A price that changes by itself has to be one you can check.
Walk the whole journey with a sample business.