Portable Markdown collaboration

Markdown is the meeting room.

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 stays the source
  • Live multiplayer
  • Self-hosted in your AWS
Project Juniper · Six-pager4 here
One document. Everyone present. Every decision in context.

Markdown in from

  • Obsidian
  • VS Code
  • Claude
  • ChatGPT
  • Git
  • any .md file

Markdown out to anywhere.

The open loop

Bring the Markdown. Keep the Markdown.

Markyard is the collaboration layer around the files and tools your team already trusts—not a new proprietary format to migrate into.

  1. 01

    Bring it in

    Upload, paste, or create from a local file. The CLI binds a document without hiding its source.

    markyard create six-pager.md
  2. 02

    Shape it together

    Write live, comment on exact passages, guide the read, and freeze the decision state.

    Synced in real time
  3. 03

    Take it with you

    Download or pull the Markdown back to your editor, repository, agent, or next workflow.

    markyard pull DOC_ID

Built for the document

Everything the conversation needs. Nothing between you and the source.

A focused collaboration toolkit for documents that deserve more than comments in a pull request and less than a proprietary office suite.

01

Multiplayer Markdown

See people, cursors, and selections as the document moves. The shared surface is live; the source remains Markdown.

presence · cursors · live sync
02

Comments with context

Anchor discussion to the exact words under review. Resolve threads without moving the decision into a separate chat.

threads · reactions · resolutions
03

Guided reading

Run read-first meetings with a shared reading overlay, live status, and a presentation pointer when it is time to discuss.

read first · discuss together
04

Snapshots and changes

Freeze important states, compare revisions, and highlight what changed before a review or decision.

snapshots · diffs · restore
05

CLI round-trips

Create, pull, diff, and push documents from the terminal. Local Markdown remains a first-class way to work.

create · pull · diff · push
06

Agent-ready work

Give AI commands and agent skills document context through customer-controlled model access. Review their work in the same room.

BYOK · commands · agent skills

Document-led work

The room reads first. The decision gets better.

Markyard gives structured narrative work a home—from the first rough Markdown to the version that records what the team chose and why.

readdiscussdecide
01

Six-pagers

Read deeply before the room talks.

Bring the narrative, run a quiet reading phase, then keep every question attached to the passage that sparked it.

02

PR/FAQ

Pressure-test the future in writing.

Co-author the press release, challenge assumptions in comments, and snapshot the version the team aligned on.

03

ADRs

Keep the why beside the code.

Draft in an editor, review with stakeholders, and pull the accepted architecture decision back into the repository.

04

Deep dives

Turn dense analysis into a shared decision.

Combine technical detail, tables, code, math, and images without flattening the document into a proprietary format.

Your cloud. Your boundary.

Customer control is part of the product.

Run Markyard in your own AWS account through AWS Marketplace. Your deployment, identity, Markdown, and model credentials stay under your control.

  • No product telemetry or document content sent to Markyard
  • Enterprise SSO with one identity provider per hosting
  • Direct and group-based document permissions
  • Bring your own AI provider keys
  • Predictable fixed annual licensing—not per seat
Your AWS account
Your peopleYour IdP
Markyardcollaboration service
private
MarkdownDynamoDB + S3IdentityEntra ID or Auth0AI accessYour provider keys
You operate the boundary

Straightforward procurement

One deployment. One fixed price.

Collaboration should grow because more people contribute—not become more expensive because they do.

Self-hosted on AWS

Fixed annual license

Launch pricing on request
  • Unlimited collaborators
  • AWS Marketplace billing
  • Enterprise SSO and permissions
  • CLI and agent workflows included
Review deployment docs

Good questions

The short version.

For setup details, the customer documentation stays as open and direct as the product.

Browse customer documentation
Does Markyard replace my Markdown files?

No. Markdown is the source of truth. Bring a file in, collaborate in Markyard, and download or pull Markdown back into your existing workflow.

Can Markyard run inside our AWS account?

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.

Does a self-hosted deployment send product data to Markyard?

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.

Which identity providers are supported?

Each hosting uses one identity provider. Customer setup documentation is currently available for Microsoft Entra ID and Auth0.

How is Markyard priced?

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.

Make the document the place where the decision happens.