The closest analogy I can find is a matchstick.
You have a note. In Obsidian, in Bear, in Apple Notes, in a text file on your desktop. You have been refining it. Adding a sentence. Removing two. Reading it back. Fixing the rhythm. At some point a thought enters your head:
This is ready. I need to share this with the world.
You strike the match. POST /publish. The matchstick ignites.
The flame parses your frontmatter. It extracts the title, the date, the tags. It renders your Markdown through a Jinja2 template – the Terminal theme, or Brutalist, or Ink, or whichever personality you chose. It fetches the taxonomy from your GitHub repo. It appends your post to the index. It pushes four files in one atomic commit – the rendered HTML, the source Markdown, the updated taxonomy, the new index page. It returns a permalink.
The match burns out. The process terminates. The flame is gone.
But the cigarette is lit. The blog post is live. The permalink is in your clipboard. The static HTML is on a CDN, served to anyone in the world at the speed of light. The thing you wrote in your notes app three minutes ago now has a permanent address on the open web.
The match existed for one second. The post exists forever.
The Speed of Doubt
Here is what the matchstick captures that no technical description can.
The pipeline is faster than hesitation. You press publish and before you can second-guess yourself – before you can reread the opening paragraph one more time, before you can wonder if the title is right, before you can question whether anyone will care – the permalink is already in your hands. The decision and the result are separated by one second. There is no window for doubt.
Every other publishing system inserts a gap between the decision and the result. WordPress shows you a preview page with a “Publish” button that asks “Are you sure?” Jekyll requires you to commit, push, wait for CI, and watch the deploy. Ghost shows a loading spinner. Substack asks you to review the email preview. Each gap is an invitation to hesitate. Each hesitation is an opportunity to decide this is not good enough, not ready, not worth sharing.
The matchstick does not ask if you are sure. You struck it. It burned. It is done. The post is live. If you do not like it, delete it. But the default is published, not draft. The default is live, not pending. The default is courage, not caution.
More good writing dies in the gap between “I should publish this” and “maybe tomorrow” than to any other cause. The matchstick eliminates the gap. One second. No gap. No tomorrow. Now.
What Burns
The match consumes itself. This is not a defect. It is the design.
The FastAPI process that handled your request does not persist. The memory it allocated is returned. The database connection it opened is closed. The Jinja2 template it loaded is forgotten. The httpx client it used to push to GitHub is garbage collected. Every object, every variable, every byte of state that participated in transforming your Markdown into a blog post is destroyed.
Nothing remains of the pipeline except the output. The HTML on the CDN. The Markdown in the repo. The taxonomy entry in the JSON file. The artifacts survive. The process that created them does not. Like a matchstick that leaves behind light and warmth but no matchstick.
This is what makes the system trustworthy. A process that persists is a process that accumulates – state, bugs, memory leaks, security vulnerabilities. A process that dies after every use cannot accumulate anything. It is born clean and dies before it can get dirty. The next request gets a new match from the box. Fresh, unused, identical to every match before it.
What Does Not Burn
The post. The words. The permalink. The static HTML that loads in 200 milliseconds on any device on any network in any country. The source Markdown in the git history, version-controlled, backed up, permanently retrievable. The taxonomy entry that tells the index page this post exists.
The permanent things are permanent. The ephemeral things are ephemeral. The system does not confuse the two. The words matter, so they are stored in a git repo that GitHub backs up across multiple data centers. The pipeline does not matter, so it is destroyed after every use. The theme does not change between publishes, so it lives in the source code. The rendered HTML does not change after publication, so it lives on a CDN.
Every piece of data lives in the place that matches its lifecycle. Permanent data in permanent storage. Ephemeral processes in ephemeral compute. Nothing is over-stored. Nothing is under-stored. The matchstick does not try to be a candle. The candle does not try to be a matchstick. Each exists for exactly as long as it should.
Why a Matchstick and Not a Lighter
A lighter persists. You carry it in your pocket. It accumulates lint, loses fluid, develops a finicky spark wheel. It requires maintenance. You refill it. You adjust the flame. You replace the flint. The lighter is a small persistent server in your pocket – always ready, always consuming space, always one mechanical failure away from not working.
A matchstick is pulled from a box when needed and discarded after use. The box is the serverless runtime. The matches are the workers. Each match is identical. Each match works on the first strike. There is no maintenance because there is no mechanism. There is no mechanical failure because the mechanism is chemistry, not engineering. Phosphorus meets friction. Fire happens. The match burns. Done.
The note2cms pipeline is a matchstick, not a lighter. It is not always ready. It does not idle in your pocket. It springs into existence when you need it and ceases to exist when you do not. There is no maintenance because there is nothing to maintain. There is no state to corrupt because there is no state. There is no configuration to drift because every execution starts from the same configuration.
A lighter is convenient. A matchstick is reliable. The industry chose lighters. note2cms chose matches.
The Box
If the match is the pipeline, the box is the protocol. PBPP. Four endpoints. One bearer token. Markdown in, permalink out.
The box does not care which match you pull. The first match and the thousandth match are identical. The box does not track which matches have been used. It does not maintain state about previous strikes. It holds matches and dispenses them. That is its entire function.
The Neon database – one table, one row per user – is the label on the box. It tells the match where to send the flame. This user’s match lights their GitHub repo. That user’s match lights theirs. The match burns the same way regardless. The output destination is configuration, not behavior.
The protocol is the box. The pipeline is the match. The blog is the light. The match is gone but the light remains.
Finality
I did not plan this metaphor. I was trying to explain to someone on Twitter what the pipeline does, and the matchstick appeared. It appeared because it is accurate. Not poetically accurate – structurally accurate. The ephemeral worker pattern IS a matchstick. Born from a box of identical instances. Activated by a single strike. Burns for exactly as long as the job requires. Produces a lasting result. Destroys itself in the process.
The entire note2cms architecture is a box of matches in a world of lighters. The lighters are impressive. They are engineered. They have adjustable flames and windproof housings and refillable reservoirs. They are designed to last.
The matches are designed to work. Once. Perfectly. And then to disappear.
There is a matchstick that burned one second ago. You are reading its output right now. The match is gone. The words remain.
That is the entire philosophy.
You struck the match. It burned. The post is live. The match is gone. The words remain.