Permanent storage holds the actual text and images
The bytes go to Arweave, where storage is paid for once rather than rented monthly. Nobody sends you a renewal notice, so nobody can fail to pay one.
Switch platforms. Get cancelled. Forget to pay. We'll make sure your work stays discoverable ... even if we disappear. PermaPress gives you centralized UX with decentralized infrastructure.
This is Ghost, not PermaPress. The story starts where you already work, and it stays there.
Fields land on definitions other software already understands. This is the only PermaPress screen in the sequence.
Three things happen, not one. Each finishes on its own and each leaves something behind you can look up.
The same string, in a window we don't run and can't edit. That is the whole argument.
One post, resting in four places. Three of them keep working if we don't.
The sequence above shows an automatic feed connection. Coming soon. The full split is below.
Publishing through PermaPress puts your content on the permaweb, so even if we disappear, or you lapse on your hosting, your work stays live. We also offer redundancy while we're here.
The bytes go to Arweave, where storage is paid for once rather than rented monthly. Nobody sends you a renewal notice, so nobody can fail to pay one.
An attestation on Ethereum ties the content hash to the identity that signed it and to a timestamp. A reader can confirm authorship and an edit chain without going through PermaPress. Metadata can be read on any block explorer.
Because the record uses Seed Protocol's shared schemas, another client can resolve your title, your byline, your revision history, and the relationship between a post and a publication. It doesn't need our code and it doesn't need our permission.
A public URL that loads in a browser with no wallet, no extension, and no explanation. This is the one piece we host. If PermaPress stops existing, this page goes away and the other three don't.
We're shipping fast based off the feedback we've received from our beta users.
Free during the beta.
Planned as paid features. Nothing here is available yet.
Writing bytes to storage that outlives a company is close to a solved problem. Several products do it, like Arweave and IPFS. PermaPress is concerned with the other half of the equation: how to find that content again.
Because the concept and ability is so new, few users or products have had to grapple with the finding of old content that was created by a tool that no longer exists. Most tools invent their own structure, schema, or format. The file survives but the metadata and viewing instructions lived in that company's codebase. Open the file with anything but their reader and you get an undifferentiated block of text with no byline, no date, and no history. Technically permanent, practically illegible.
PermaPress writes against universal schemas and Seed Protocol's semantic design: shared, public definitions that any client can resolve. The meaning travels with the bytes. It creates an archive rather than a backup you can't find or open.
{
"d": "<p>The county approved forty-…",
"m": "eyJ0IjoiVGhlIGJvbmQ...",
"v": 4
} Permanent, and opaque. The metadata blob is only meaningful to the application that wrote it.
Post {
title: "Humanity's Transition From Capital to Data"
author: Identity(kaxline)
publishedAt: 2026-03-14T09:41Z
supersedes: Post(v3)
} Permanent, and resolvable. Another client can list your work, credit you, and order your revisions.
Current publishing tools work well in short to medium time horizons. They match user expectations that come from years of losing work or migrating to new platforms every few years.
| Where you publish | What remains |
|---|---|
| Substack | Whatever you exported while it was running, in a format you'd need to re-host yourself. Your subscriber list is portable; the archive's public URLs are not. |
| Ghost, self-hosted | Everything, for as long as you keep paying for and patching a server. Genuinely yours, and genuinely easy to lose track of. |
| WordPress, self-hosted | The same trade, with more surface area to maintain and a longer history of abandoned sites going dark quietly. |
| Mirror, Paragraph | The content is on permanent storage and will still be there. The records use each product's own structure, so reading it usefully still means using their reader. |
| PermaPress | The content is on permanent storage, and the record of it is written against public schemas on a public index, so any client that speaks the protocol can resolve it. Today PermaPress is the only client, but seedprotocol.io hosts RSS feeds that can plug into any reader. |
A small team building big ideas for the long term.
The publishing client. Offline-first, runs in the browser, stores drafts on your device. Built and maintained by one developer, which is a real risk and is named as one in our planning documents rather than hidden. The client will be open source and self-hostable, the same way Ghost is — that packaging isn't ready yet.
The data layer underneath, built on the Ethereum Attestation Service. The schemas are public and any application can read from and write to the same content layer. It will be held by a nonprofit entity, separately from the product.
The team incubating PermaPress, with backgrounds in journalism and nonprofit education. Communications, outreach, partnerships and testing.
We're taking a small first group so we can actually read what you send back and fix it. If we're not a fit for what you publish, we'll say so.