If you've seen my project, you've probably thought: "Isn't this just Diptyx?"
Fair question. I want to address it directly.
Yes, Diptyx inspired Verso
I'm not going to pretend I invented the dual-screen e-reader concept. The Diptyx project showed me it was possible. Same screens, same ESP32 approach, same core idea. I have huge respect for what they've built.
If Diptyx didn't exist, I probably wouldn't be building Verso.
So what's different?
The difference isn't in the what — it's in the who and the how.
Diptyx is for makers
Diptyx is open-source and built for people who want to understand and modify their devices. The enclosure is 3D-printed. The firmware is MIT-licensed. You can fork it, hack it, improve it.
That's genuinely great. The maker community needs projects like this.
But it means Diptyx is optimized for hackability, not polish. And that's a deliberate choice, not a flaw.
Verso is for readers
I'm building for a different audience: people who want a dual-screen e-reader but don't want to assemble it themselves.
People who want to buy a finished product, take it out of the box, load their books, and read.
The kind of person who buys a Kindle or a reMarkable, not the kind who builds an Inkplate project.
What that means in practice
| Diptyx | Verso | |
|---|---|---|
| Enclosure | 3D printed | Injection molded (goal) |
| Target user | Makers, tinkerers | General readers |
| Open source | Yes, fully | No, but open formats supported |
| Assembly | Pre-assembled | Pre-assembled |
| Price point | ~$230 | TBD, likely similar or slightly higher |
| Aesthetic | Functional | Premium (that's the goal) |
The software question
Diptyx is fully open-source, including firmware. Verso won't be.
But I'm committed to supporting open formats and software:
- EPUB, PDF, TXT — your books, your files
- OPDS — connect to your own library
- KOReader compatible — if you want to run it, you can
You own your books. You control your library. No DRM lock-in, no proprietary ecosystem.
I'm just not open-sourcing the firmware itself. Partly because I want to maintain a consistent experience, partly because I need something proprietary if this becomes a business.
Room for both
I don't see Verso as competing with Diptyx. Different audiences, different goals.
If you want to hack, learn, and build — get a Diptyx.
If you want a finished product you can just use — that's what I'm trying to make.
The dual-screen e-reader market is basically nonexistent. There's room for multiple approaches.
My commitment
I'll always credit Diptyx as inspiration. I'll never pretend I came up with this idea in isolation. And if my project helps bring more attention to dual-screen e-readers in general — including Diptyx — that's a win for everyone who's wanted one of these devices.
Follow the Verso journey on X.