Give it an HTML file and get back a live link anyone can open. There is no project to create, no repository to connect, and nothing to configure.
Free to publish. Free to serve. Your page is live at https://launch-notes.emits.page about a second later.
$ emit publish launch-notes.html
published https://launch-notes.emits.page
id: pg_7k2m4c
version: v1
$ emit update pg_7k2m4c launch-notes.html
published https://launch-notes.emits.page
version: v2
$ ▌
https://launch-notes.emits.page is now on version 2. The link never changed, and anyone who already had it sees the new page.
01/The honest comparison
02/What a Emits link does
Republish to the same page and the URL never changes. The link you sent last week still opens, and now it shows this week's version.
Public for the open web. Unlisted for a link you hand out, served with noindex. Private, which answers 401 without a valid token.
Give a page an expiry and it takes itself down on time. Good for a quote, an invitation, or anything that should not outlive the week.
Bind a domain once at the account level and every page also serves at your-domain/launch-notes. Certificates are issued for you.
Each publish becomes an immutable artifact served from the edge with no origin compute. Nothing to keep running, and a busy page costs about nothing.
Four verbs, plus tags and groups for keeping track. Small enough that an agent can hold the entire surface in one prompt.
03/The whole API
Small on purpose, so a person can learn it in a minute and an agent can hold all of it in one prompt. Publishing is a single request. Everything else is bookkeeping.
POST /v1/pages
{
"html": "<main>…</main>",
"slug": "launch-notes",
"visibility": "unlisted"
}
201 Created
{
"url": "https://launch-notes.emits.page",
"version": 1
}04/Pricing
For every page you publish.
Your pages, on your own domain.
05/Questions
Create an account and publish your first page in about a minute. No card, no project setup, no build to wait on.