Post-publish tools for the new internet

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.

Apply for the private beta Or check a published post yourself: 0x8506edd0…9404f2
One post, from Ghost to the public record
theledger.ghost.io/ghost/#/editor
Humanity's Transition From Capital to Data
Keith Axline · 14 March 2026
Published to your site and your list

This is Ghost, not PermaPress. The story starts where you already work, and it stays there.

From your feed

title
primary_author
published_at
html

Seed schema

Post.title
Post.author → Identity
Post.publishedAt
Post.body

Fields land on definitions other software already understands. This is the only PermaPress screen in the sequence.

Text and images written to permanent storage
Content hash recorded0x8506edd0…9404f2
Authorship signed and published to the index

Three things happen, not one. Each finishes on its own and each leaves something behind you can look up.

permapress.xyz
Published. Content hash

0x8506edd0…9404f2
block explorers
Record0x8506edd0…9404f2
Signed by0x8f42…3a12
Time2026-03-14 09:41 UTC

The same string, in a window we don't run and can't edit. That is the whole argument.

Humanity's Transition From Capital to Data
v1 · 0x8506edd0…9404f2
Permanent storageArweave
Public record of who published it Ethereum · EAS
Readable by any Seed clientSeed Protocol
An ordinary page for ordinary readers permapress.xyz

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.

Who has to stay in business for your work to stay live?

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.

Storage cost
Paid once at publish. No renewal, no invoice, no lapse.
Record cost
One transaction per published version.
Permanent storage The public record Other Seed clients The page we host

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.

Example transaction 9DleY…RgiQ

A public record says who published it and when

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.

Example attestation 0x8506edd0…9404f2

Can be read by RSS readers and other clients

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.

Schema definitions seedprotocol.io

And a normal web page, for people who just want to read it

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.

Our roadmap

We're shipping fast based off the feedback we've received from our beta users.

Status
Private beta. Small cohort, hand-selected.
Sign-in
Email or passkey. No seed phrase, no browser extension, no gas prompt.

Works today

  • Import any post you've published, by URL
  • Edit it locally in the browser, offline if you want
  • Publish to permanent storage with a signed public record
  • Get a public page and a content hash anyone can verify
  • Publish corrections as new versions, with the old ones still readable

Free during the beta.

Storage is one thing. Discovery is another.

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.

Schema registry
seedprotocol.io
Built on
Ethereum Attestation Service

The same post, stored against a private schema

{
  "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.

The same post, stored against a shared schema

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.

What's left when your publishing tools stop working?

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.

Note
Every tool here is good at other things this table doesn't measure.
If the company shuts down tomorrow, what survives and where can you find it?
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.

Who's building this

A small team building big ideas for the long term.

Licence
MIT

PermaPress

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.

Source not yet public

Seed Protocol

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.

JournoLabs

The team incubating PermaPress, with backgrounds in journalism and nonprofit education. Communications, outreach, partnerships and testing.

Apply for the private beta

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.

Optional: a link to something you've written recently.

We'll reply either way. We don't add you to a mailing list, and there's nothing to install while you wait.

Cost
Free during the beta.
What you'd need
An email address and something you've already published.
What you wouldn't
A wallet, a seed phrase, or any change to how you publish now.