renza

Your agent makes the deck.
Renza is where you share it.

One command turns an HTML deck into a hosted document — presentable, commentable, versioned, and shared with one link.

or drop an HTML deck / .zip
npx renza publish
○ Reading artifact...
Detected deck · 12 slides
Hosted at renza.io/try/gim_fgqweiuhg
Live
Present mode + thumbnails ready
Comments enabled · anchored to slides
Version v1 saved
○ Creating share link...
Shared
Anyone with the link · renza.io/v/X3k9z

Making a deck got fast.
Sharing one didn't.

Agents write decks, reports, and one-pagers as HTML — the format they're fluent in. Then the file is stranded: an attachment in a chat, a blob in a repo.

A document needs what Drive gave documents — a link, comments, versions, the right people. Renza gives that home to HTML, and every step is one command.

Key commands

Teach your agent the format

renza init

Print the slide contract

renza guide

Publish to a shareable link

renza publish deck.html

Share it with people

renza shares create <deck>

Read the feedback

renza comments list --deck <deck>

How it works

Publish, review, update

01 · Publish

One command, one link

Point the CLI at the file your agent wrote. Renza reads the slide structure and hosts it as-is — before you've made an account.

Uploading

02 · Review

Send the link, get comments

Anyone can open it, present it, and pin comments to a slide. Viewers and commenters are free — no seat, no account.

03 · Update

Publish again — same link, new version

The next publish becomes version 2. Comments stay anchored to their slides, history reads like a ledger, and you can roll back.

A published deck in the Renza viewer — thumbnail rail, presence, present mode

Use cases

What it's for

Claude made you a deck

Ask your agent for a deck and you get an HTML file. One command later it's hosted, presentable, and shareable — no account needed.

Your agent runs the lifecycle

The CLI acts as you. Your agent reads the feedback, replies in your name, and ships the fix as a new version at the same link.

Reports and docs, from any pipeline

Anything that emits HTML can publish here — weekly reports, client one-pagers, board decks — each with a link, comments, and history.

npx renza grants create q3-deck
○ Granting access...
Shared
jane@rocko.io added as commenter
Invite email sent
Link · renza.io/v/X3k9z

Share, read feedback, reply, ship a version, upload assets — every app action is a command, with the same permissions you have.

Where Renza fits

GitHub gave code a home. Drive gave documents one.

What agents make needs both — an artifact they can edit, and a document people can review.

Capability
GitHub
Home for source code
Drive
Home for office documents
Renza
Home for what agents make
The artifact agents makeGitHub's strength
Hosts the open HTML artifact, live
GitHub Pages
hosting retired
served as-is
Agents can edit the asset directly
its home turf
API, not native format
open HTML, BYO-AI
Version history with rollback
git, the standard
limited
artifact ledger
A document everyone can reviewDrive's strength
Built for non-technical reviewers
developer tooling
Comments on the rendered document
on code diffs
in context
anchored pins
Sharing & permissions for everyone
repo-level
people, roles, links
people, roles, links
Present mode & a document viewer
serves a website
native formats only
present, thumbnails, nav

The surfaces

Everything a hosted document needs

Present mode

Full-bleed presenting with keyboard and clicker nav — zero chrome, one clean link.

Anchored comments

Pins dropped on the slide, threads, resolve — and comments survive new versions.

Version history

Every publish is kept. See who changed what, when — and roll back.

Sharing and roles

Drive's share dialog: people, link access, viewer / commenter / editor roles.

Any model, any tool

Claude, GPT, Gemini, a pipeline, or by hand. Your exact HTML, hosted as-is.

BYO-AI over MCP

Edit with your own model on your own subscription. Renza sells no inference.

Sandboxed by origin

Untrusted HTML renders on a separate content domain, in a sandboxed frame — never on Renza's origin.

Governed when it matters

SSO, SCIM, audit logs, and BYO storage on Enterprise — the estate IT asks for.

No models hosted

Neutrality is the design, not a policy. Renza can't favour a lab it doesn't depend on.

Read the security approach

Pricing

Collaboration is free

You pay for seats and governance when a team forms — never for the AI, never for the sharing. Every new workspace starts with 30 days of Renza Pro, no card required.

Free

$0forever

Make it real, share it anywhere.

  • Up to 3 workspace editors
  • Unlimited viewers & commenters
  • Unlimited decks & sharing
  • Present mode, import, version history
  • BYO-AI via MCP

Renza Pro

Most popular
$15per editor / month

When a team forms around the work.

  • Everything in Free
  • Unlimited editors
  • Custom domain — your brand on every link
  • Your logo & colors on the deck viewer
  • Remove the “Shared with Renza” badge
  • Password-protected & expiring links
  • Email support

Enterprise

Customcontact us

The full governance estate.

  • Everything in Renza Pro
  • SAML SSO + SCIM directory sync
  • Audit logs + log streaming
  • BYO storage + encryption controls
  • Trust centre, diligence pack, DPA

Prices are proposed and may change before general availability. See the full feature matrix.

Publish your first deck

One command, no account. Sign in when you want to keep it.

Read the docs
Renza — where your agent's documents live