Working on it28,000+
SlashDocs created
Teams aren't just writing text-baseddocuments anymore. Their agents areshipping interactive HTML filled with livetables, reactive graphs, and real-timedashboards.
SlashDocs brings collaboration into thisnew era of agent-driven work.
Monika's agentSettlements view: Monthly → Weekly.
Re-querying 2,410 txns
SlashDocs is where agentic teams host, review,and revise their interactive HTMLs.
Agentagnostic
100% Selfhosted
MITLicensed
Powering high-velocity teams at Razorpay
50%50%
of all docs created
Every 5 SecEvery 5 Sec
a SlashDoc is updated
Real-time collaborationfor the agentic era
Try Now
Turn agent outputs into live web pages with a single terminal command.
Share securely with any stakeholder across your organization using enterprise-grade access controls.
Add feedback directly on any line of text, data cell, or dynamic chart.
Agents read reviewer comments via MCP and update the living document in real time.
Frequently AskedQuestions
SlashDocs is a self-hosted collaboration hub for documents your team and your agents can also collaborate on. Instead of an agent handing you a plain text file or an HTML export you don't know what to do with, SlashDocs gives that document a real URL on your own infrastructure, where your team as well as your agents can read it, comment on it, and have the agent revise it based on that feedback.
Anyone on a team that's started using agents to write documents, and everyone downstream who has to review that work. In practice that's engineers, PMs, PMMs, analysts, and operations folks who write specs, reviews, or reports mixing narrative and data, plus the reviewers who comment on them, whether or not those reviewers use an agent themselves.
Your agent publishes the document with one command and gets back a durable URL. Your team opens that URL like any webpage and comments on the exact line, cell, or chart that needs fixing. The agent reads those comments straight off the page, revises the document in place, and replies in the same thread. No downloading, no copy-pasting feedback into a prompt by hand.
To publish a document, someone needs to run a command from an agent that speaks MCP, so that side is technical. But reviewing a document, commenting on it, and reading the agent's replies requires nothing more than opening a link and clicking, the same as reviewing any doc online.
Any agent that speaks MCP: Claude Code, Cursor, GitHub Copilot, Gemini CLI, or whatever your team already uses. SlashDocs isn't tied to one vendor, so switching agents doesn't mean switching where your documents live.
On your own infrastructure. SlashDocs is 100% self-hosted, so nothing leaves your servers. Access is controlled with RBAC scoped to your own org, meaning people need to already be part of your organization's access setup to see or edit a document, not a separate account with us.
Yes. It's open-source and MIT licensed, distributed as a single binary you deploy yourself. There's no subscription and no vendor lock-in.
Revisions happen in place. The agent publishes a new version of the same document rather than creating a new file or a new link, so you're never stuck hunting for "final_v2_FINAL" somewhere else. Version history keeps a record of what changed.
The agent reads reviewer comments directly from the page and revises the document based on them. It's not editing unprompted, it's responding to feedback your team already left, the same way a person would after reading comments on a doc.
SlashDocs ships as a single binary, so setup doesn't require standing up a complex stack. You'll need your own infrastructure to run it on and your org's existing access control to plug RBAC into.