The Markdown workspace for technical teams

GPDoc gives teams one place to write documents, run notebooks, build slides, manage scripts and spreadsheets, diagram systems, and publish websites from open, versionable files.

Start building in GPDoc See how GPEditor works

Web macOS iOS VS Code IDEs

Documents

Notebooks

Diagrams

Publishing

Google

GPDoc document editor showing a structured document workflow

Documents proof

Structured documents with Markdown at the center

Draft specs, launch notes, handbooks, and research writeups with rich formatting, comments, tables, math, and source-controlled content.

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.

Workflow demos

See GPDoc workflows move from source to finished work

These product-like previews show edits, diagrams, code output, and slide assembly moving through one open-file workflow. Live Markdown collaboration is still shown as an in-development preview.

Live Markdown review

A simulated shared-document flow with typed edits, cursor movement, review state, suggestions, and comments. Live collaboration remains labeled as in development.

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 in development

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.

Platform surfaces

Available where technical teams work

GPDoc meets teams across the web app, macOS, iOS, VS Code, Cursor, and other supported IDE workflows so documents can stay close to the files and tools teams already use.

Review setup paths

Web app

Available

Start in the browser when you need the fastest path into a GPDoc workspace.

macOS

Available

Use GPDoc from the desktop app when your work should stay close to local files.

iOS

Available

Open GPDoc workflows on mobile for review and on-the-go access.

VS Code

Extension

Use the GPDoc extension from the IDE where technical teams already work.

Cursor and other IDEs

Supported

Bring GPDoc into extension-compatible IDE workflows where supported.

Choose a path

Open GPDoc or evaluate the setup with your team

Open the app when you are ready to create files. Use the docs, workflow pages, and pricing details to help the team evaluate setup, publishing, and adoption.

Docs

Install GPDoc, connect integrations, and understand the product model.

Read the docs

Solutions

Map GPDoc to documentation, notebooks, publishing, and review workflows.

Browse solutions

Pricing

Review current plans and decide where to start.

View pricing

Open GPDoc

Start the app flow and create the first workspace.

Start building

Create the first GPDoc workspace

Start with a document, notebook, slide deck, spreadsheet, or diagram. Keep the work in open files, then add docs, publishing, and setup paths as the team evaluates GPDoc.

Start building in GPDoc Read setup docs