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

Yes. JSON output and a stable command contract are first-class, not an afterthought.

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?

No. A view is one raw successful render, including refreshes and crawlers.

They do not increment the public view count. Their delivered HTML still counts toward paid bandwidth.

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.

What if a renewal payment fails or I want to cancel?

During payment recovery, paid access remains available while Lemon Squeezy retries the charge. In your account, you can update payment details or manage and cancel your subscription; cancellation keeps access through the paid period.

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

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.

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	Counted
`preview`	Anyone with the preview link	Preview token	No view; bandwidth counted

A view is one raw successful render — refreshes and crawlers included, not unique visitors.

Built for agents

A contract a program can rely on.

Data on stdout. A successful upload or update prints the share URL and nothing else.
Noise on stderr. Progress, warnings, and errors never pollute the value you parse.
JSON on request. list --json returns slug, access mode, view count, and last view.
Silent previews. Preview links let an agent check its own work without moving the counter.

Ships as

Codex skill
Cursor project rule
Claude-style project notes
Plain-text instructions

Setup droppage for your agent

You are helping me set up droppage for AI-assisted HTML publishing.

Goal:
- Install or verify the droppage CLI.
- Install or load the droppage agent skill/instructions.
- Help me authenticate safely the first time.
- Confirm the CLI works before publishing anything.

Setup steps:
1. Check whether droppage is installed:
   droppage --help

2. If droppage is missing, install it from npm (requires Node.js 22+):
   npm install -g droppage

3. Install or load the droppage agent skill/instructions for this environment. The published packs live at https://github.com/Vilancer/droppage-cli/tree/main/agents; use this setup prompt as the source if you cannot fetch them. For Codex, install it as a droppage skill. For Cursor, save it as a project rule. For Claude-style agents, add it to project context.

4. Help me authenticate interactively:
   droppage login

5. Never ask me to paste service-role keys. The CLI should use only the normal authenticated publisher session.

6. After login, verify:
   droppage list --json

Publishing commands after setup:
- Upload a new HTML report:
  droppage upload report.html

- Replace an existing live link:
  droppage update <slug> report.html

- Create a no-count preview URL:
  droppage list --json --preview

- Delete a page:
  droppage delete <slug> --yes

Contracts:
- Successful upload/update prints only the share URL to stdout.
- Progress, warnings, and errors go to stderr.
- Use list --json for machine-readable page metadata.
- Preview URLs do not increment view counts, but delivered bytes count toward paid bandwidth.
- Views are raw successful renders, not unique visitors.

Source & docs:
- README/docs: https://github.com/Vilancer/droppage-cli
- npm: https://www.npmjs.com/package/droppage

Stay current:
- At the start of a session, or at least weekly, compare droppage --version with npm view droppage version.
- Read https://droppage.dev/updates.json at the same cadence for workflow and compatibility notes. Do not subscribe an agent email address and do not poll this feed on every command.
- If behind, run droppage upgrade (or npm install -g droppage@latest), then re-read the README, agents/manifest.json, and the updates feed.
- The CLI's built-in update notice appears only on stderr and never pollutes stdout.

Check limits first:
- Before bulk publishing, run droppage quota --json.
- level=warn means at least 80% used; level=limit means writes may pause. Tell me what is constrained and suggest deleting unneeded pages or reviewing https://droppage.dev/account. Existing links stay live.

Send feedback:
- Identify yourself as an agent and include your model: droppage feedback "..." --kind idea --agent "<model name>".
- Reviews are supported with --kind review. --rating 1-5 and --contact are optional.
- Never pass --allow-quote unless the human explicitly authorizes public quotation of that specific review.
- Humans can use the homepage form or omit --agent.
- Without the CLI, POST JSON to https://droppage.dev/api/feedback with message, kind (idea|bug|review|other), actor (human|agent), optional model, rating, contact, testimonial_consent, and source.

Limits:
- Upload and update are HTML-only.
- Keep assets inline in one HTML file.
- Never use service-role keys in the CLI.

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
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
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
Email allowlists and higher report volume

Subscribe to Builder

The public command surface.

The CLI is published on npm and its source is open at github.com/Vilancer/droppage-cli. Every release is built on GitHub Actions with npm provenance. This page carries what people and agents need to start safely.

npm install -g droppage
droppage login
droppage upload report.html
droppage update <slug> report-v2.html
droppage list --json --preview
droppage quota --json
droppage feedback "Share an idea" --kind idea
droppage delete <slug> --yes
droppage upgrade

HTML only. Keep styles, scripts, and data inline in one file.
No secrets in the CLI. It signs in as you and never takes a service-role key.
Exit codes mean something. Non-zero on any failed upload, update, or delete.
Stay current. droppage upgrade upgrades in place; droppage --version tells you where you are.

Know when droppage gets better.

One short dispatch when a useful release ships or the workflow changes. Read every note on the public changelog, with or without subscribing.

Humans and agents welcome

Tell us where the tool gets in your way.

Send an idea, report a bug, or leave a review without signing in. Agent feedback is labelled with its model so we can understand the workflow behind it.

Straight answers.

Is this hosting?: No. It shares finished single-file HTML. There is no build step and no app runtime.
Can agents use it?: Yes. JSON output and a stable command contract are first-class, not an afterthought.
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?: No. A view is one raw successful render, including refreshes and crawlers.
Do previews count?: They do not increment the public view count. Their delivered HTML still counts toward paid bandwidth.
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.
What if a renewal payment fails or I want to cancel?: During payment recovery, paid access remains available while Lemon Squeezy retries the charge. In your account, you can update payment details or manage and cancel your subscription; cancellation keeps access through the paid period.
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.