Skip to main content
VISUAL COLLABORATION FOR ENGINEERING TEAMS

Open Excalidraw from Git. Edit together. Commit it back.

Sketchblock opens existing .excalidraw files from a connected GitHub repository directly in the browser. Work on the diagram alone or in a live session, then save the reviewed file back to the project as a commit.

One repository file. One visual workspace. One traceable history.

$ git clone https://github.com/mimeonline/sketchblock.git
$ ./scripts/start.sh
A visual artifact moving from a whiteboard into Git and a live collaboration sessionAShared ideaarchitecture.excalidrawGit commitversioned · reviewableMMAK2 live
THE GAP SKETCHBLOCK CLOSES

Updating a diagram in Git takes too many manual steps.

A repository-backed Excalidraw file usually travels through downloads, exports, file replacement, and a separate commit. Shared sessions add another place where the latest result can live. Sketchblock connects these steps in one browser workflow.

01

Files take a manual round trip

A repository diagram must be downloaded, opened in Excalidraw, exported again, replaced in the project, and committed manually.

02

Collaboration leaves Git behind

A shared whiteboard session creates a useful result, but the repository file does not update with it.

03

Guests need focused access

Customers and reviewers should be able to work on one diagram without receiving access to the entire repository.

Open from Git

Select an existing .excalidraw file from a connected GitHub repository and open it in the browser.

Edit together

Work on the same diagram in a focused live session with collaborator and viewer roles.

Commit it back

Save the reviewed file directly to its repository as a traceable Git commit.

FROM REPOSITORY TO LIVE ROOM AND BACK

One file.
One continuous workflow.

sketchblock / architecture.excalidraw
Product context
Shared understanding
MMAK2 live
BUILT FOR TECHNICAL CONVERSATIONS

Some decisions need a canvas.
Every result needs a home.

Sketchblock connects the moment when a team thinks together with the place where its technical work already lives.

01

Architecture decisions

Turn a technical conversation into a versioned artifact that stays beside the code.

02

System maps

Explore relationships visually while keeping every reviewed result inspectable in Git.

03

Focused workshops

Invite collaborators for the working session and viewers for the shared understanding.

FIVE MINUTES TO FIRST VALUE

Start with no credentials.

01

Start locally

One script launches Postgres, migrations, the web app, and collaboration runtime.

02

Try the demo

Edit the included board and open a live session without creating credentials.

03

Connect GitHub

Switch to your repositories when you are ready to work with real project artifacts.

Michael Meierhoff, creator of Sketchblock
WHY I BUILT SKETCHBLOCK

The diagram belonged in the project. Updating it kept pulling the work out of the project.

I’m Michael Meierhoff, a software architect, systems thinker, and independent builder. For more than two decades I have worked with software systems, architecture, and the difficult space between technical detail and shared understanding.

Sketchblock grew from a recurring frustration: editing a repository-backed diagram meant moving the file between Git, Excalidraw, exports, and commits. Live collaboration created another disconnected workspace. Sketchblock turns that round trip into one self-hosted, traceable workflow.

Open the repository file.
Work together. Commit the result.

Open the quickstart