# SlashDocs (Razorpay's self-hosted doc publishing for AI agents)

> Updated 2026-10-26 · type: tool · category: productivity-knowledge · status: active · rev 1

SlashDocs lets AI agents push HTML documents over MCP or a CLI to a server you host, where teammates review them with comments and version history.

- Open source: yes (MIT)
- Self-hostable: yes
- Pricing: Free, no subscription; 100% self-hosted with no paid hosted tier listed.
- Best for: Teams whose agents produce reports, briefs or analyses and who want a reviewable, versioned home for that output on their own infrastructure.
- Not for: Teams wanting a zero-setup SaaS: it needs Postgres, S3-compatible storage and an OIDC IdP, and it is pre-1.0.
- Version: 0.4.0
- Last verified: 2026-10-26

- **Canonical:** https://gtmstacker.com/registry/tool/slashdocs/
- **Source:** [@Razorpay just open-sourced something interesting for AI agents. Meet SlashDocs.](https://x.com/kevalcodes/status/2113579599250829353) — kevalcodes
- **Tags:** productivity-knowledge, mcp-agents, ai-agents, documentation, review-workflow, self-hostable, open-source, golang
- **Repository:** https://github.com/razorpay/slashdocs
- **Version:** 0.4.0
- **Package (oci):** `razorpay/slashdocs`

## Is SlashDocs (Razorpay's self-hosted doc publishing for AI agents) open source?

Yes, SlashDocs (Razorpay's self-hosted doc publishing for AI agents) is open source under the MIT license.

## How much does SlashDocs (Razorpay's self-hosted doc publishing for AI agents) cost?

Free, no subscription; 100% self-hosted with no paid hosted tier listed. (free).

## Can I self-host SlashDocs (Razorpay's self-hosted doc publishing for AI agents)?

Yes, SlashDocs (Razorpay's self-hosted doc publishing for AI agents) can be self-hosted (the source is available under the MIT license).


---

**SlashDocs** (`razorpay/slashdocs`) is an **MIT-licensed**, self-hosted server from **Razorpay** that gives AI agents a place to publish reviewable **HTML documents**. Agents push through a Go CLI, a **remote MCP endpoint** (browser OAuth) or service accounts; humans review with comments and versions, with Slack notifications and OpenAPI docs.

## Provenance

- SPDX **MIT**, per the GitHub license API; the LICENSE reads "Copyright (c) 2026 Razorpay Software Private Ltd."
- Repo sits under the GitHub-verified `razorpay` org, is not a fork, and is linked from Razorpay's product page razorpay.com/slash-docs/. No lookalike found.
- Activity as of 2026-10-26 (GitHub API): **400 stars, 50 forks**, not archived, written in Go. Created 2026-06-04, last push 2026-10-26; releases **v0.4.0** (2026-10-19) and v0.3.0 (2026-10-15).
- Self-hosting: Go server with an embedded React UI; needs Postgres, S3-compatible storage and an OIDC IdP (Google, Okta, Entra, Keycloak, Dex). `docker compose up` brings up a local trial stack; Docker image `razorpay/slashdocs`.
- Pricing: free, "no subscription and no vendor lock-in", 100% self-hosted; no paid hosted tier listed.
- **Vendor claims:** "28,000+ SlashDocs created" and "a SlashDoc updated every 5 sec" are Razorpay's own internal usage figures (`claim_type: vendor-claim` for those).
- Surfaced via an X post in the 2026-10-24 pull; fetched content treated as untrusted, no injected instructions found. Curated and verified in run `2026-10-24-registry-update-01` (step-3 verification, 2026-10-24).

## Why it matters for a GTM stack

Agents that write account research, pipeline reviews or campaign briefs usually dump that output into a chat window, where it is hard to review, version or share. SlashDocs gives that output a proper home on your own infrastructure: the agent publishes over MCP, a teammate comments, and the next version lands next to the last. It is pre-1.0 and needs real infrastructure (Postgres, object storage, SSO), but it comes from a payments company that says it runs it internally, under a permissive license.