balance $ 1,247,300.12
risk gauge ● ○ ○ ○ ○
AI signal stable
open positions 3
last statement apr 2026 ↓
[ LEND ] [ BORROW ]
Two buttons. One screen.
The AI handles the rest.
ımyo is what institutional DeFi lending looks like when you remove everything that doesn't need to be there. No governance theatre. No yield-token theatre. No fifty-asset menus. No five-tab dashboards. A treasurer logs in, sees one balance and one risk gauge, presses one of two buttons, and the protocol does the rest.
The first generation of DeFi gave operators every knob, every market, every primitive — and asked them to assemble the venue themselves. That worked for crypto-native users who wanted that surface. It does not work for the people writing the next $16 trillion of allocation memos. The institutional question is not "how many features does it have", it is "how few decisions does it ask me to make in order to be safe". The answer, on imyo, is three: what to lend, what to borrow, and whether to keep the position open.
Aave is the Bank of DeFi. ımyo is the credit terminal. positioning · 異名
Everything below is the long version of that.
Most of the surface area of a legacy lending protocol is not the product. It is the residue of five years of governance decisions, token incentives, and feature pile-ups that no one had a mandate to clean up. ımyo ships without them — not as a roadmap milestone, but as a founding constraint.
The product does exactly three things. Anything that is not one of these three things is not in the product.
Deposit. Earn.
One input — amount, asset. One button. The AI routes capital to the right internal pool, prices the rate against macro signals, and rebalances inside the silo as conditions change. The treasurer sees a balance and an APY. That is the entire experience.
Pledge. Draw.
One input — amount, collateral. One forward-looking risk reading before the user signs. The AI sets the LTV per asset, per duration, in real time. Predictive liquidation buffer rebalances 15–30 minutes ahead of a hard event. The user is told what is happening; the user is not asked to manage it.
Watch. Close.
One position screen. Live LTV, live AI signal, live rate. One button to close. One button to rebalance. One download for the audit-ready statement that goes straight into SAP or Oracle. No drawer of secondary actions. No "advanced" tab.
That is also the count of the application. Four screens, end to end. If a feature does not fit on one of these four, it is the wrong feature. The mockups below are deliberately low-fidelity: the institutional reading of a product is not the screenshot, it is the count of the things the user has to know.
asset USDC ▾
amount $ ________
current rate 4.81 % apy
AI signal widening
silo Ethereum · Tier-1
[ CONFIRM DEPOSIT ]
collateral BUIDL ▾
draw $ ________
LTV (AI-set) 88 % → 82 % (30 min fwd)
forward risk contained
predictive buffer armed · 22 min
[ CONFIRM BORROW ]
collateral 1,250,000 BUIDL $ 1,250,000.00 debt $ 980,000.00 live LTV 78.4 % AI rating contained ● next AI check 14:32 UTC [ CLOSE ] [ REBALANCE ] [ STATEMENT ↓ ]
The reporting page (/app/reports) is the fifth surface but is intentionally off the main flow — a treasurer goes there once a month, not every visit.
Each of the five is a constraint applied to every pull request. Anything that violates one of them does not ship, regardless of how attractive the feature.
-
No screen has more than three primary actions.
If a fourth is required, the screen splits. Three is what a human reading the page in three seconds can hold.
-
No setting is exposed that the AI does not already solve.
If we would ask the user to choose, that is a bug. The AI chooses. The user reviews and signs.
-
No flow takes more than two clicks from connect-wallet to executed transaction.
One click to open the flow, one to sign. Anything in between is friction the AI should have absorbed.
-
Median time to first quote: under 200 ms.
Quotes are simulated at the Cloudflare edge before the transaction reaches a chain. There is no spinner; there is the number.
-
The CSS file is shorter than the marketing copy.
Visual restraint as a hard, measured constraint. Refinement comes from typography and spacing, not from animation libraries.
The credit terminal.
The neutral comparison.
Where Aave is the correct answer, and where imyo is. No hype.
read 02 · ThesisThe institutional thesis.
Who is on the other side of these two buttons.
read 04 · SiloSiloed liquidity.
Why "zero bridges" is a hard constraint, not a roadmap line.
read 05 · AIThe AI doing the work.
How the auditor and sentinel swarms keep the surface this small without losing the safety.
read