Getting started

From a local file to a link you can send.

SaveKit is intentionally boring to use. Choose the smallest workflow that fits your project, then keep the details in the dashboard.

Publish one HTML file

Open the publisher, paste your markup or drop an .html file, preview it at three widths, and choose an expiry.

Host a static build

Zip the output folder with index.html at its root. SaveKit preserves relative assets and gives the build a version history.

Add controls

For logged-in pages, turn on password protection, form collection, a custom slug, or an automatic renewal policy.

Agent publishing

Let your coding agent hand you the URL.

Create a token in your dashboard, then let Claude Code, Cursor, or another tool call the publish API. Tokens are shown once and can be revoked any time.

Create an API token

curl -X POST https://api.savekit.net/v1/publish \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "title": "My launch page",
    "html": "<!doctype html>...",
    "renewalMode": "auto"
  }'

Security notes

A safe default, with clear boundaries.

Uploads are size-checked and validated before publish.

Published HTML is rendered in an isolated frame in the starter build.

Production runs pages on a separate origin with CSP and malware scanning.

Password secrets are hashed; API tokens are only stored as hashes.

You can delete your account and associated content from the dashboard.