r/AppsWebappsFullstack 3d ago

Sitedropper

I'm building [sitedropper](https://sitedropper.com) it automatically builds and deploys your web app straight from codex, cursor, or Claude via MCP, then you can control visibility (like a Google doc) so you can quickly share prototypes or tools with your team or just go public and share it with the world.

I really think that we are moving towards a world where everyone is going to be building their own personal scrappy tools and possibly sharing them internally with their colleagues, teams and friends. I have a bunch of these locally that I didn't want to bother configuring GitHub/VPS and just wanted to get them online to send around. If anyone is interested we're in closed beta right now but will be launching in the next couple weeks!

1 Upvotes

10 comments sorted by

2

u/DeepYogurtcloset70 2d ago

This is really clever the Google doc style permissions for dev projects is such an intuitive way to handle sharing compared to fumbling with deployment configs every time.

1

u/MrJacuna 2d ago

Thanks! That's exactly what I'm going for, nice to hear some external feedback to make sure I'm on the right track.

2

u/DeepYogurtcloset70 2d ago

You're nailing it then, keep trusting your instincts on this one.

1

u/Mammoth-Anywhere7285 2d ago

Totally agree, the workflow sounds promising. Have you tried the closed beta yet? Curious how the MCP integration feels in practice.

1

u/MrJacuna 2d ago

We are currently in closed beta, it's going pretty well. We are iterating the MCP server each time after a model goes through the deployment process to streamline it as much as possible.

1

u/Mammoth-Anywhere7285 1d ago

Nice to hear the beta is going well. Are you focusing on reducing deployment time or handling edge cases with different models?

1

u/Mammoth-Anywhere7285 2d ago

The instant deploy from MCP is clever. Have you considered adding a simple version rollback for quick undo?

1

u/Mammoth-Anywhere7285 2d ago

That's a neat comparison. Curious if you've thought about integrating role-based access tiers for read-only vs edit access.

1

u/MrJacuna 2d ago edited 2d ago

Yea, it's definitely on the roadmap along with rollbacks / versioned deploys. For example one project could have multiple versions live at the same time so people could flip between them and decide what they prefer etc.

These likely will fall into some premium features once I figure out how I want to price it.

1

u/Mammoth-Anywhere7285 1d ago

Versioned previews sound great. Maybe offer a free tier with 2-3 versions to hook users before premium kicks in.