// share / cursor
Share what you just built in Cursor.
Cursor turns an idea into working code in minutes. DropLine takes the build output and ships it on a 30-second public URL — no Git, no deploy.
// how it works
Three steps, about thirty seconds.
- Step 01
Build it locally in Cursor.
Run your project's build command from Cursor's terminal (npm run build, pnpm build, vite build — whatever your project uses). End up with a dist/ or build/ folder.
- Step 02
Drag the build folder into DropLine.
Open DropLine in another tab, drag the static output folder into the upload area. We pick index.html as the entry automatically.
- Step 03
Paste the URL into Slack / email / your spec doc.
DropLine returns a short URL on view.dropline.biz. View counts show up in your DropLine dashboard so you know who opened the link.
// use cases
What people do with this.
- Show your manager the small internal tool you scaffolded in Cursor this morning.
- Share a custom dashboard with the team that requested it, without DevOps overhead.
- Demo a Cursor + Claude pair-programming experiment without taking it through CI.
// faq
Frequently asked.
What if my Cursor project uses Next.js with SSR?+
SSR isn't supported on DropLine. Configure Next.js with output: 'export' for a static export, build locally, and upload the out/ folder. Server-only routes will not run.
Can I share work-in-progress code from Cursor without exposing the source?+
Yes. DropLine only serves the build output, not the source. Your Cursor workspace stays private; only the rendered HTML / CSS / JS / assets are public.
Do I need to commit to Git before sharing?+
No. DropLine has no Git integration — it just hosts the static output. This is the main reason indie hackers prefer DropLine over Vercel preview for quick shares.
// related
Or, the longer comparison.
DropLine vs Vercel Preview
Vercel is a production deploy platform. DropLine is the 30-second share between “I built it” and “they saw it.”