Multiplayer Markdown
See people, cursors, and selections as the document moves. The shared surface is live; the source remains Markdown.
presence · cursors · live syncPortable Markdown collaboration
Move a six-pager, PR/FAQ, ADR, or deep dive from any Markdown workflow into a live room—then pull the same Markdown back out.
Markdown in from
.md fileMarkdown out to anywhere.
The open loop
Markyard is the collaboration layer around the files and tools your team already trusts—not a new proprietary format to migrate into.
Upload, paste, or create from a local file. The CLI binds a document without hiding its source.
markyard create six-pager.mdWrite live, comment on exact passages, guide the read, and freeze the decision state.
Synced in real timeDownload or pull the Markdown back to your editor, repository, agent, or next workflow.
markyard pull DOC_IDBuilt for the document
A focused collaboration toolkit for documents that deserve more than comments in a pull request and less than a proprietary office suite.
See people, cursors, and selections as the document moves. The shared surface is live; the source remains Markdown.
presence · cursors · live syncAnchor discussion to the exact words under review. Resolve threads without moving the decision into a separate chat.
threads · reactions · resolutionsRun read-first meetings with a shared reading overlay, live status, and a presentation pointer when it is time to discuss.
read first · discuss togetherFreeze important states, compare revisions, and highlight what changed before a review or decision.
snapshots · diffs · restoreCreate, pull, diff, and push documents from the terminal. Local Markdown remains a first-class way to work.
create · pull · diff · pushGive AI commands and agent skills document context through customer-controlled model access. Review their work in the same room.
BYOK · commands · agent skillsDocument-led work
Markyard gives structured narrative work a home—from the first rough Markdown to the version that records what the team chose and why.
Six-pagers
Bring the narrative, run a quiet reading phase, then keep every question attached to the passage that sparked it.
PR/FAQ
Co-author the press release, challenge assumptions in comments, and snapshot the version the team aligned on.
ADRs
Draft in an editor, review with stakeholders, and pull the accepted architecture decision back into the repository.
Deep dives
Combine technical detail, tables, code, math, and images without flattening the document into a proprietary format.
Your cloud. Your boundary.
Run Markyard in your own AWS account through AWS Marketplace. Your deployment, identity, Markdown, and model credentials stay under your control.
Straightforward procurement
Collaboration should grow because more people contribute—not become more expensive because they do.
Self-hosted on AWS
Good questions
For setup details, the customer documentation stays as open and direct as the product.
Browse customer documentationNo. Markdown is the source of truth. Bring a file in, collaborate in Markyard, and download or pull Markdown back into your existing workflow.
Yes. The self-hosted deployment is designed for the customer’s AWS account and AWS Marketplace procurement, so your team controls the environment and its data boundary.
No product telemetry or document content needs to leave the deployment. External services are contacted only when your administrators configure them, such as your identity provider or your own AI provider credentials.
Each hosting uses one identity provider. Customer setup documentation is currently available for Microsoft Entra ID and Auth0.
Markyard is planned as one predictable annual license for a deployment, not a per-seat tax on collaboration. Launch pricing is provided directly.
Keep the source. Add the room.