No. It shares finished single-file HTML. There is no build step and no app runtime.

Can I share a Jupyter notebook or a Plotly dashboard?

Yes. Export it as one HTML file (Jupyter’s export to HTML, Plotly’s write_html, Altair’s chart.save) and run droppage upload. Scripts run, so interactive charts work, and chart libraries can load from a CDN. Keep the data inside the file, up to 5 MB. Send it to named people by email (Builder) or behind a password (Starter and Builder).

Can I replace a live page?

Starter and Builder plans can update the HTML behind the same link while keeping its access settings. Every plan can delete its own pages.

What happens if I reach a limit, downgrade, or a payment expires?

Existing links stay live with their current access settings. The affected uploads, updates, or new previews pause until your next UTC reset or an eligible plan is active.

Yes. Install the CLI with npm install -g droppage, run droppage login, and publish your first file. Product-update emails are optional and require confirmation.

For data analysts, developers, and AI agents · one command · one live link

Publish interactive reports. Share one live link.

Turn an analytics dashboard, stakeholder report, model card, data story, or AI-generated HTML file into a URL you can lock down, update, or take back. No build step, server, or framework.

$ npm install -g droppage

Read the docs Set up your agent or get product updates by email

Input: One HTML file
Output: One URL on stdout
Access: Choose before sharing
Undo: Delete anytime; updates on paid plans

droppage upload report.html --password

fd 2stderr — for you

reading report.html · 412 KB
uploading to pages/6f1c…/QHckYKmBq5.html
access mode: password
published in 1.2s

fd 1stdout — for the next program

https://droppage.dev/p/QHckYKmBq5

For analysts

Send the dashboard, not a screenshot of it.

Export the report you already built and publish it. Stakeholders open a link in their browser and get the real thing: filters, hover values, and tabs included. No account, no attachment, no “which version is this?”

Charts just work. Interactive charts run as authored, and chart images saved next to the HTML go up with it.
One link, every week. droppage update replaces the report behind the same link, so readers keep one bookmark and the access you chose.
Only the right people. Invite named stakeholders by email or set a password. Signed in, you open your own report directly.
Views are people. One unique visitor per page. Refreshes, chat link previews, and your own opens don’t count, so the number tells you who actually looked.
Reports that clean up. --expires 30d on a board pack or client deliverable, and the page and its charts are deleted after.

Publish from

Jupyter (nbconvert to HTML)
Plotly and Altair exports
Chart.js and ECharts pages
Your AI agent

Five commands cover the whole life of a link.

Left is what you type. Right is what comes back. Nothing else to learn.

npm install -g droppageone global binary · Node.js 22+
droppage loginmagic link sent · session saved to ~/.droppage
droppage upload report.htmlhttps://droppage.dev/p/QHckYKmBq5
droppage update QHckYKmBq5 report-v2.htmlsame link, new HTML, access settings untouched
droppage list --json[{ "slug": "QHckYKmBq5", "view_count": 42, … }]
droppage delete QHckYKmBq5 --yesblob removed first, then the row

Sharing rules, not server config.

Every page has one access mode chosen when it is published. The link stays the same for paid-plan HTML updates. When you are signed in, your own protected pages open directly, without the password or email link.

Mode	Opens for	Visitor needs	Views
`public`	Anyone with the link	—	Counted
`password`	Anyone you give the password to	Password	Counted
`email`	Addresses on your allowlist	Magic link	Counted
`private`	Only you	Your session	Owner opens not counted
`preview`	Anyone with the preview link	Preview token	No view; bandwidth counted

A view is one unique visitor per page. Refreshes, reopening in the same browser, link previews from chat apps, and your own opens do not add views.

Built for agents

A contract a program can rely on.

The share URL alone on stdout, JSON on request, progress and errors on stderr, and non-zero exit codes on failure. droppage ships ready-made instructions for Codex, Cursor, Claude-style agents, and any other agent: paste one setup prompt and your agent installs, signs in, and checks the CLI before it publishes anything.

Set up your agent Read the command contract

Plans and pricing

Small plans for single-file sharing.

Choose a monthly or yearly subscription for one person or one agent. Start free, then upgrade when you need more reports, bandwidth, or access controls.

Free

always free

For trying droppage and occasional HTML shares.

5 pages
100 views/month
Images up to 5 MB per page
Public links and private drafts

Get started

Starter

$4/mo

$39/year

$9 saved yearly

For individuals and agents publishing small reports.

50 pages
2 GB served/month
Images up to 20 MB per page
Updates, previews, and password pages

Subscribe to Starter

Builder

$12/mo

$99/year

$45 saved yearly

For regular analyst and developer reporting workflows.

200 pages
10 GB served/month
Images up to 50 MB per page
Email allowlists and higher report volume

Subscribe to Builder

Straight answers.

Is this hosting?: No. It shares finished single-file HTML. There is no build step and no app runtime.
Can I share a Jupyter notebook or a Plotly dashboard?: Yes. Export it as one HTML file (Jupyter’s export to HTML, Plotly’s write_html, Altair’s chart.save) and run droppage upload. Scripts run, so interactive charts work, and chart libraries can load from a CDN. Keep the data inside the file, up to 5 MB. Send it to named people by email (Builder) or behind a password (Starter and Builder).
Can I replace a live page?: Starter and Builder plans can update the HTML behind the same link while keeping its access settings. Every plan can delete its own pages.
Are views unique visitors?: Yes. A view is one unique visitor per page. Refreshes, reopening in the same browser, link previews from chat apps, and your own opens do not add views. Bandwidth is still measured per delivery.
What happens if I reach a limit, downgrade, or a payment expires?: Existing links stay live with their current access settings. The affected uploads, updates, or new previews pause until your next UTC reset or an eligible plan is active.
Can I use it today?: Yes. Install the CLI with npm install -g droppage, run droppage login, and publish your first file. Product-update emails are optional and require confirmation.

Images, expiry, previews, payments: more answers in the docs. Something missing? Tell us.