Drop it in.
Share it out.
Your team builds working web tools, then has nowhere safe to put them. canvas-drop is where they land: deploy a static canvas in seconds, share it behind your org sign-in, and skip the screenshots and slide decks.
Connect your agent over MCP, or curl a folder straight to a live URL.
A guided tour
See it across the whole workflow.
Create, edit, share, and govern. Every surface of canvas-drop, in one place.
Why canvas-drop
From “I built a thing” to “the team is using it,” without a deploy pipeline.
Deploy in seconds
Drag a folder, paste HTML, push from a script, or connect your AI agent over MCP so it can create and deploy canvases for you. A canvas is just static files: no build to wait on, nothing to provision.
Shared exactly as far as you mean
An access ladder, per canvas: keep it private, share with a team, add a named few, open it to the whole org, or publish an admin-gated public link. Invite anyone by email — colleagues, or friends & family — and they're in the moment they sign in, with no extra account or password for you to manage. Add a password or expiry, and revoke anytime.
Versions you can roll back
Each publish snapshots an immutable version. Edit in the browser, preview the draft, then publish. If something breaks, make an earlier version current again in one click.
Sharing
An access ladder that fits how people actually share.
One rung per canvas — from just you to the whole internet, with everything in between. Teams sit in the middle: a group you create and share a subset of canvases with.
Just you, the owner.
A named few you add or invite, by email.
A group you create — your colleagues, or friends & family you invite by email.
Anyone signed in to your organization.
Anyone with the URL — admin-gated, and static files only.
Invite anyone by email — colleagues, contractors, or friends & family. They're in the moment they sign in through your instance's auth: no app-managed passwords, no magic-link accounts. A personal team needs no org at all.
Five primitives
Static canvases, real backend power.
Canvases ship as static files, with no server build. When a canvas needs more, it reaches exactly five audited primitives. Secrets stay server-side, always.
Key–value kv
Persist state with a tiny get/set store. No database to run.
Files files
Upload, store, and serve assets straight from a canvas.
AI ai
Call the model through a server-side proxy, with no keys in the browser.
Identity identity
Know who is viewing. `me()` returns the signed-in org member, resolved server-side.
Realtime realtime
Broadcast and subscribe over a managed socket. No server to operate.
Built for teams
Control, without the overhead.
canvas-drop is built for your whole org from day one. Access, limits, and accountability come standard, not bolted on.
Teams & invites
Group people into a team — your colleagues, or friends & family — and share a subset of canvases with just them. Invite by email; new people get access the instant they first sign in. No app-managed passwords, no magic-link accounts.
Org sign-in (SSO)
Everyone signs in with your Google or OIDC org account, gated by email domain and an admin allowlist.
Admin console
Set global quotas and defaults, and choose which members may publish public links.
Your brand, your look
Flip the whole instance — dashboard, editor, and landing — to one of four design skins from the admin console. No restart, no code.
Member management
See who's in, grant or revoke admin, and block access in a click.
Audit log
Significant actions are recorded, so there's always an account of what changed.
Make it yours
One platform, your look.
Pick a design skin in the admin console and the whole instance re-voices — accent colour, display type, and corner shape — across the dashboard, the editor, and this landing page. Same app, your brand. No restart, no code.
Private by design
Your tools, your data, your infrastructure.
Privacy isn't a setting here. It's the default posture: canvas-drop keeps the minimum it needs to run, and nothing leaves your instance.
Org-only by default
Every canvas sits behind your sign-in until you deliberately share it.
No telemetry, ever
canvas-drop never phones home. No tracking, no analytics, no third-party beacons.
Secrets stay server-side
AI and provider keys live on the server and are never shipped to the browser.
Backend off by default
A canvas reaches no backend until you switch it on, one primitive at a time. Public visitors get static files only.
Your infrastructure
Self-host on your own VPS or cloud; your data lives where you put it.
Read the Privacy Policy and Terms of Service.
Open source
Yours to run. MIT-licensed, self-hostable.
canvas-drop is open source and self-contained: your database, your storage, your sign-in. SQLite or Postgres, local disk or S3, all a config change away. No telemetry, no phone-home. Host it on a single VPS or bring your own cloud.