I built the home my agents' workdeserved.
Why I'm building Wovo, and where it's going. I keep this page current.
I build a lot of things. An idea on a Tuesday, a working product by the weekend. These days I make most of it with AI.
Claude Code, Cursor, v0, ChatGPT. They hand me single-file HTML all day: reports, dashboards, prototypes, little explainers. Good work that vanishes. It ends up buried in a tool's sidebar, or pasted into a Slack thread nobody can find a week later.
So I gave it somewhere to live. Wovo takes any HTML your agents make and turns it into a live, versioned page you can share, then files it in a library you and your team can actually search.
I'm not building Wovo to be the next unicorn. No growth charts, no exit plan. I'm building the tool I needed, for people who work the way I do.
I look up to Cloudflare and Basecamp. They got big without turning into something you'd resent. That's the bar I hold myself to. And it really is just me here. This page runs on Wovo, because I won't ship you anything I don't use myself.
Building Wovo, solo
Shipped
what's live nowThe product works end to end today. The notable drops, newest first.
Invite your team by email
Real invites from workspace settings — your teammate gets a signed link, joins your library, and private gating just works for them.
Fair-use limits that protect the free tier
Page-size and page-count budgets plus exact, self-expiring rate limits, so one runaway script can't spoil it for everyone.
Deploy from any AI tool, one command
The npx @gowovo/wovo CLI and MCP server are published — your agent ships to Wovo from inside the tool you already live in.
One-click version rollback
Every version was already saved; now the page panel shows the history and restores any of them in a click.
A ground-up design system + a warmer look
Rebuilt the whole interface on one small set of primitives. Cleaner, calmer, consistent in light and dark. (Yes, including this page.)
Kept — the canon of pages worth keeping
Add a public page to a shared, curated canon when you choose to. Off by default; sharing a link never means adding it.
Per-page access control
Public, team-only, private, or password, set per page and enforced everywhere. Plus private, unlisted, and public workspaces.
Teams, workspaces & deploy tokens
Your library lives at a shareable URL, organized by spaces and the tool that made each page. Rotate a deploy token and the old one dies instantly.
Passwordless sign-in & a 5-minute onboarding
Email-code sign-in, then a guided “deploy your first page” path. No passwords to forget.
Deploy any HTML → a live, versioned page
From your terminal (wovo deploy), your AI agent (MCP), the browser, or the API. Every deploy snapshots a new version, so a bad change is never one step from gone.
Up next
what I'm buildingRoughly in order. The dates are estimates, not promises. I'm one person.
On my radar
ideas I'm weighingLikely candidates for the list above. Tell me which of these you actually need — that's what moves one up.
.md file and have Wovo render it beautifully.Tell me and it goes on this list. I read every one, and the things people need most are what I build next. shashank@wovo.dev
P.S. Have an idea, a bug, or just want to say hi? I read everything. shashank@wovo.dev. Thanks for building the way you do.