Wallet infrastructure · self-hosted · MIT
Monavy is Privy, but free — and the key never leaves your user's device.
Same drop-in modal, same hooks, same transfer webhooks. You host it, so it costs nothing. The key is generated in your user's browser, so there is nobody left who could hand it over.
<MonavyProvider appId="app_live_…" apiUrl="https://monavy.acme.dev">
{children}
<MonavyModal appName="Acme" />
</MonavyProvider>
// that's the integration. the key is made here, in the browser,
// and there is no code path that uploads it.Two differences
Monavy matches the developer experience — embedded wallets, email login, passkeys, React hooks, webhooks. It parts ways on custody and on price.
01
The SDK, the server, the dashboard and the webhook pipeline are one MIT repository. Clone it, point it at a SQLite file, and you are running the whole product. No seat pricing, no MAU tier that resets your budget in month four, no vendor who can raise the price of your login screen.
02
A hardware wallet is safe once it reaches you. Getting it to you is the weak part: it has to be manufactured, sold and shipped, and that distribution chain necessarily knows your name and your street address. Those customer databases have leaked. Monavy has no distribution chain. The key is generated on hardware the user already owns, sealed with their passkey, and stored encrypted in their browser.
Architecture
Everything on the left happens in the user's browser. Everything on the right is your server. Nothing crosses that line except public data.
The user's device
No code path in @monavy/core passes key material to a network call. That is the invariant the whole design rests on.
Your server
Take this server offline and users can still sign and send. They lose the dashboard and the webhooks — not their money.
Transfer webhooks
The SDK reports every ERC20, ERC721 and ERC1155 transfer it signs — submitted, confirmed, reverted. Your Monavy server stores it, signs it with the endpoint's own secret, and retries for a day if your service is down.
<MonavyProvider
appId={APP_ID}
apiUrl="https://monavy.acme.dev"
webhooks={{ endpoint: `${API}/api/v1/events` }}
>
// queued in localStorage, batched, retried with
// backoff. a closed tab still delivers on next load.import { createWebhookHandler } from "@monavy/webhooks/server";
export const POST = createWebhookHandler({
secret: process.env.MONAVY_WEBHOOK_SECRET!,
onEvent: async (event) => {
if (event.type !== "transfer.confirmed") return;
await fulfilOrder(event.data.hash, event.data.chainId);
},
});
// HMAC-SHA256 over "<timestamp>.<raw body>", constant-time
// compared, replay window enforced. throw to get a retry.Same event shape on every chain
Honest comparison
A managed provider takes real work off your plate. If you would rather buy that than run it, buy it. This table is for the teams who would rather run it.
| Monavy | Managed embedded wallets | |
|---|---|---|
| Where the private key lives | The user's device, only | Split across provider-operated shares |
| Price at 100k monthly wallets | $0 — you host it | Priced per monthly active wallet |
| Can the vendor be compelled to act? | There is no vendor | The provider holds a share |
| Runs with the vendor offline | Yes — signing is local | No |
| Source available | MIT, whole stack | Client SDKs |
| Email / passkey login | Included | Included |
| React hooks + drop-in modal | Included | Included |
| Signed transfer webhooks | Included, with retries | Included |
| Someone else runs the servers | No — that is the trade | Yes |
| Compliance paperwork handled for you | No — that is the trade | Yes |
Comparison describes the self-hosted Monavy stack in this repository against the general shape of managed embedded-wallet services. Check any specific vendor's current documentation before making a decision on it.
Pricing
There is no paid tier of Monavy and no feature held back for one. The only thing you can pay for is somebody else doing the setup.
Clone it, point it at a SQLite file, and you are running the whole product. No seat pricing, no monthly-active-wallet meter, and no vendor who can reprice your login screen later.
Installation
Want Monavy running in your stack without doing it yourself? Digital Native installs and configures it for you. The software stays free and yours — you are paying for the setup, not for a licence.
Quickstart
No account to create, no API key to wait for, no card on file.
01
One repository holds the SDK, the server, the dashboard and a working example dapp.
git clone https://github.com/hskang9/monavy
cd monavy && pnpm install && pnpm build02
SQLite by default, so there is nothing to provision. Seeding creates an operator account and a demo app.
pnpm --filter @monavy/admin db:push
pnpm --filter @monavy/admin seed
pnpm dev:admin # → localhost:300203
Wrap the tree once. The modal handles login, wallet creation, unlock and recovery.
pnpm add @monavy/react @monavy/webhooks
<MonavyProvider appId="app_…" apiUrl="https://monavy.acme.dev">
{children}
<MonavyModal appName="Acme" />
</MonavyProvider>