GPDoc logoGPDoc

The collaborative Markdown workspace for technical teams

Write together live, review comments and suggestions, restore safe versions, connect Google Workspace and Microsoft 365, and bring reviewable agent workflows into open, versionable files.

GPDoc editor with three named participants and labeled live cursors in one Markdown document

Live collaboration

Edit one open file together

People can edit the same live file from web, VS Code, macOS, and iOS with connected presence, labeled cursors, comments, and suggestions. Controls differ by surface.

One connected workflow

Write, collaborate live, review comments, restore safely, and publish

GPDoc combines the team controls expected from a document platform with open files that remain usable across editors, devices, Git, and cloud systems.

Collaborate Live

Edit together with presence, shared cursors, comments, suggestions, and role-aware sharing.

Review & Comment

Add attributed comments and suggestions, then use version history and safe restore when needed.

Google Docs & Microsoft 365

Move documents and slides through Google Docs, Google Slides, Word, and PowerPoint workflows.

Works With Agents

Keep configured-agent comments, suggestions, and file changes visible in GPDoc and Git.

Works Everywhere

Carry one open GPDoc file model across web, macOS, iOS, VS Code, and Cursor.

GPEditor proof

One Markdown engine, many technical workflows

GPEditor is the shared Markdown engine inside GPDoc. GPDoc adds the workspace, file model, Git workflow, publishing path, sharing model, product surfaces, and integrations around it.

Engine model

Open files

Markdown, Mermaid, notebooks, tables, scripts, slides, and site content.

GPEditor

One Markdown engine renders and edits the work across content types.

GPDoc workspace

The app adds workspace, Git, publishing, sharing, and platform surfaces.

Write

Markdown documents

Readable source files for specs, plans, handbooks, and technical notes.

Analyze

LaTeX math

Equations stay close to scientific and analytical writing.

Diagram

Mermaid diagrams

Architecture and process diagrams can be reviewed as source.

Run

Scripts and notebooks

Executable work can sit beside the documents and slides that explain it.

Structure

Tables and spreadsheets

Structured data work keeps its surrounding project context.

Publish

Slides and websites

Presentation and web output can come from the same source files.

Formats and publishing

Bring Markdown editing everywhere

Keep open, versionable source in GPDoc while moving work through cloud documents, IDEs, native apps, Git review, portable local output, and published websites. Connected providers use their own formats and controls where conversion or linking is required.

Review publishing and export paths

Editable imports

Open GPDoc JSON, Markdown, LaTeX, HTML, plain text, Python, JavaScript, TypeScript, JSX, TSX, Jupyter Notebook, CSV, Microsoft Word, Microsoft PowerPoint, Google Docs, and Google Slides where the file type and surface support import.

Portable local output

Use File > Save File to download a complete GPDoc JSON source copy. Use Export for Markdown, HTML, PDF, LaTeX, CSV, Jupyter Notebook, supported source code, Microsoft Word, and Microsoft PowerPoint, plus SVG and PNG for supported drawing files.

Provider-native transfers

Send supported work to Google Docs, Google Slides, Microsoft Word, or Microsoft PowerPoint through a connected Google Drive, Microsoft 365, or OneDrive workflow.

Publishing destinations

Publish websites for easy sharing through GitHub publishing, HTML export, and static-site output. Hosting, domains, and deployment controls remain with the selected destination.

Workflow demos

See GPDoc workflows move from source to finished work

These product-like previews show live edits, diagrams, code output, and slide assembly moving through one open-file workflow.

Live Markdown review

A shared-document flow with typed edits, cursor movement, review state, suggestions, and comments.

Diagram editing

Nodes connect on the canvas while Mermaid source appears beside it, keeping visual work tied to source-controlled diagrams.

Notebooks and code

Code cells execute into a table and chart built from the named risk file, so the output is tied to the source data.

Slides from Markdown

Markdown lines become slide content, diagram evidence, a summary table, and presenter notes in the same versionable workflow.

roadmap.md
Live collaboration
1# Launch architecture notes
2The API gateway validates signed requests
3- Add sequence diagram for webhook retries
4- Owner: platform security
Maya commented

Add the retry path before publishing.

Devon is editing line 2
State: Draft in review
Maya
Devon
architecture.mmd
Source-controlled diagram

graph LR

Editor -- draft --> Review

Draw mode
EditorMarkdown
ReviewComments
SitePublish
DiagramSource
DataTable
risk-notebook.gpnb

1import gpdoc

2workspace = gpdoc.open('./launch-review')

3risks = workspace.table('risk-register.csv')

4risks.group_by('owner').to_markdown()

In [3] Ready
Output
Security12
Data7
Release5
Security
Data
Release
The chart uses risk-register.csv output, so the visual changes with the source data.
board-update.gpslides
Markdown to deck
1. Brief
2. Diagram
3. Table
4. Notes

## Architecture update

Slide 2
Building slide

Review status by workflow

Webhook retry pathApproved
API
Worker
Queue
Security 12
Data 7
Release 5
Presenter note: confirm owners before customer review.

Create the first GPDoc workspace

Start with an open document, notebook, slide deck, spreadsheet, or diagram. Collaborate live, review comments and suggestions, restore safe versions, connect cloud tools, and keep the source ready for Git and agents.