A publishing and collaboration tool for HTML documents, with shareable links, comments, version history and access controls.
I found coding agents unreasonably good at making things in HTML. I’d had much less success getting them to build PowerPoint decks through MCP tools. Letting them write code directly seemed like a better starting point for documents, too.
But once I had an HTML file, I missed all the things I took for granted in a shared document: somewhere to host it, inviting people by link or email, seeing their cursors, and getting comments on the work.
That was the starting point for Renza. I wanted the flexibility of a document made with code, with the sharing and collaboration workflows I liked in Loom and Google Drive.
From a file to a shared document
Renza turns an HTML file into a hosted document. Publish from the CLI, share a link, and review it together in the browser. Comments stay anchored to individual slides, older versions can be restored, and presentation mode is built in.
The document can come from any agent, model or editor. Renza handles publishing, permissions and the audit trail, so people can use whichever tools they prefer to create the work.
Agent native
A design principle from the start was that anything a person could do in the UI, an agent should be able to do through the CLI or MCP tools. I wanted full feature parity so an agent could carry a document through the whole workflow: author it, publish it, share it, read the feedback and resolve comments.
That also shaped the first experience. Run npx renza publish deck.html and get
back a link you can share with anyone. That moment, going from a local file to
something another person can open and respond to, is what I wanted people to
reach as quickly as possible.