At some point I wanted to write something online that wasn’t tied to my name.
Not because it was controversial or anything dramatic. I just wanted a place to put thoughts without the whole setup: create an account, verify an email, pick a username, fill out a profile, and suddenly you’re a content creator with a brand.
That whole pipeline felt heavy for what was basically a few paragraphs I wanted to share.
So I looked around. Telegra.ph is close, but it’s Telegram’s thing and the editing experience feels dated. Medium wants an account. Substack wants your email and your audience-building strategy. Write.as is decent, but it still asks you to register.
I just wanted a page where I could write, publish, share the link, and be done.
That’s Echo.
How it works
You go to myecho.page, type, hit publish, and get a link. Share that link with whoever you want. That’s the entire thing.
No account. No email. No password. Nothing stored about you personally.
The post lives at a URL.
If you want to edit it later, there’s a mechanism for that without needing a login. If you want it gone, you can delete it.
The interesting design problem
Building something with no accounts sounds simple. It’s actually weird.
The normal way apps handle ownership of content is simple: the user logs in, the user is authenticated, and the user can edit their stuff. Remove user identity and you have to rethink what ownership even means.
Echo handles this with a local key stored in your browser. When you publish, a key is generated and saved client-side. That key is what lets you edit or delete later. No key means no access. It’s like a lock with no username attached to it.
The downside is if you clear your browser storage, that key is gone. You can still read the post, but you can’t edit it.
I’m still thinking about the right way to handle this without forcing an account on people.
What people actually use it for
From the testing-phase feedback, the use cases were interesting:
- Quick thoughts people didn’t want on their main blog
- Technical notes they wanted to share with a specific person via link
- Drafts for ideas that weren’t ready to publish under their name
- People in situations where posting publicly under their identity wasn’t safe
That last one I didn’t expect as much, but it makes sense.
Sometimes the point isn’t anonymity for its own sake. It’s just not wanting everything you write to be permanently attached to your identity.
Still in development
Echo is still being shaped. The testing phase is running until August 2026, and early users get pro features while it’s in beta.
The things I’m still figuring out are better key persistence, post discovery without compromising anonymity, and maybe some light formatting controls.
If you want to try it and give feedback: myecho.page
Honest feedback is the most useful thing right now.
What feels broken, what feels unnecessary, what’s missing.
The whole point of Echo is removing the friction between having something to say and saying it. No pipeline. No brand building. Just write and share.
Sometimes that’s all you need.