About
Why we built Dropway
Our coworkers were generating reports, dashboards, and prototypes all day. Sharing them safely was the hard part.
The problem
It started with a pattern we kept hitting at work. Someone would generate something worth showing: an analysis exported to HTML, a dashboard, a one-off prototype, a design handoff, a build of a docs site. Then came the awkward part. How do you actually share it?
Every option was bad in its own way. Email attachments go stale the moment you send them and can’t be updated. Files dropped in chat get buried and lost. Public buckets and pastebins have no access control, so anything sensitive leaks the instant the link escapes. And the “proper” route was no better: pushing a simple website to GitHub and wiring up Netlify or Vercel was overkill for a folder of files we just wanted a few people to see. Standing up a real server with authentication in front of it was more overkill still.
So reports either got shared unsafely, or didn’t get shared at all. Good work sat on someone’s laptop because the last mile was too much friction.
The idea
A folder of files should become a live URL in seconds, with access control built in from the start. Not after you configure a pipeline. Not after you write a YAML file. Not after you wire up auth. You pick the folder, you get a link, and you decide exactly who can open it.
That last part is the whole point. Every Dropway site has a sharing tier: public, password protected, an email allowlist, or org only. Sharing safely is the default, not an extra step you remember to take later.
What Dropway is
Dropway turns a folder of static files into a live, access controlled URL. Drag and drop it in the dashboard, push it from your terminal with the CLI, or deploy it straight from an AI client through the Dropway MCP server. Only changed files upload, and your folder is live the moment it finishes.
Beyond the artifact itself, teams can share the skills that produced it and the chat behind the build: an org skill library everyone can install, and session transcripts you can attach to a site as a “How this was made” panel under the same access controls.
It’s also open source and fully self hostable under the FSL. Run the hosted service if you want zero ops, or run the entire stack yourself if you’d rather keep everything in house. Either way the code is on GitHub.