Documentation
DrawGetting started
Updated
Connect the Scalpels team to the GitHub account that should own Draw. Once GitHub and Laravel Cloud are ready, select Draw in the catalog and deploy it.
What the install provisions
| Resource | Why Draw needs it |
|---|---|
| Neon Postgres 18 | Stores people, teams, boards, revisions, and sharing rules. |
| Managed queue | Runs work outside the web request. |
| Managed WebSockets | Carries board updates between people working at the same time. |
After deployment, Scalpels runs php artisan migrate --force. Laravel Cloud injects the resource connection values, so there are no catalog environment values to fill in.
First checks
- Make a private board.
- Share it with one teammate as a viewer, confirm that they cannot edit, then change them to an editor and confirm that they can.
- Share it with the whole team and check both access levels.
- Create a read-only signed link and open it in a signed-out browser.
- Open the board in two sessions and confirm that changes arrive live.
- Connect an agent to Draw's MCP server and ask it to add a small sketch.
The last two checks exercise the managed WebSocket application and the MCP door separately, while the earlier sharing checks cover the rules around the board itself. The editor is a separate path.