v1.4 · 31 edge regions

Ship a page.
Get a URL.
One call.

Hand Nullpoint an HTML document and it hands back a public HTTPS link. No build step, no config file, nothing to wait for.

Deploy your first page Read the 3-step

bash — nullpoint

# one request, no project setup
$ curl -X POST https://api.nullpoint.dev/v1/pages \
    -H "Authorization: Bearer $NP_TOKEN" \
    -F html=@index.html

→ 201 Created  (312 ms)
{
  "url":     "https://quiet-fox-41.nullpoint.dev",
  "region":  "fra1",
  "ttl":     "48h",
  "status":  "live"
}

312msmedian time to live URL

0config files required

31edge regions, anycast routed

Why it exists

Preview links shouldn't need a pipeline

Most of what you deploy is thrown away in an hour — a mockup for a client, a repro for a bug, a page an agent just generated. Nullpoint optimises for that case instead of pretending it's production.

Ephemeral by default

Every page carries a TTL between 1 and 168 hours. It expires on its own, so nothing rots in your account.

One artifact, no tree

A single self-contained document is the unit of deploy. Inline your CSS and JS and you're done — no bundler in the loop.

Promotable when it sticks

If a throwaway turns out to matter, promote it to a stable subdomain with a persistent TTL. Same URL semantics.

How it works

Three steps, none of them a build

STEP 1

Name it

Pick a lowercase DNS label, 3–32 chars. That label becomes the host, so it's readable in a Slack message.

STEP 2

POST the document

The body is your HTML. It lands in object storage and propagates to the edge before the response returns.

STEP 3

Send the link

The URL is live on the first request — no cold start, no "deploying…" screen to babysit.

Ship a page.Get a URL.One call.