Readeck is a tool for saving, organizing and revisiting web content, aimed at people who want to keep the pages they read and come back to them later.

What it is

Readeck is a bookmark and content management project listed in this registry under Productivity & Utilities, in the Bookmark & Content Management category. Its own description says it is for "Save, organize and revisit web content effortlessly." The GitHub repository is a signpost rather than the project's home: the README consists of one line stating that the official repository is on Codeberg at https://codeberg.org/readeck/readeck. The facts provided do not name a specific product that Readeck replaces, so claiming it displaces any particular incumbent would go beyond what is documented here.

The problem it addresses is the one implied by its description: web content that gets read once and then cannot be found again, because saving and re-finding pages is usually handled badly by browser bookmarks or not handled at all. Readeck's stated scope covers three steps — saving content, organizing it, and revisiting it. Because the README in these facts is a redirect notice rather than documentation, the concrete mechanics behind those three steps (how content is stored, how it is organized, what interface is used to revisit it) are not described here.

Key capabilities

• Saves web content, per the project description "Save, organize and revisit web content effortlessly."
• Organizes saved content, the second verb in that same description.
• Revisits saved content, the third and final verb in the description.
• Points to the official repository at https://codeberg.org/readeck/readeck, per the README line.
• Lists no command names, file names, image names, formats or protocols in the provided README excerpt.
• Declares no repository topics, no programming language, and no licence in the provided metadata.

Who uses it and how

• Individual readers who save web pages and return to them later, which is the workflow the description names.
• Users arriving through the GitHub listing, who are directed to Codeberg for the actual project.
• Interest is visible in the listing itself: 274 stars and 0 forks.
• Maintenance signal from the same listing: last push on 2023-12-18, with 2 open issues.
• The facts do not describe deployment scenarios, team shapes, hosted options, or self-hosted environments.

Getting started

The README excerpt provides no install method, no package name, no Docker image and no compose file. Its only concrete instruction is that the official repository lives at https://codeberg.org/readeck/readeck, which is where setup information would have to come from.

How it compares

No list of paid products and no list of similar tools is provided in these facts. Readeck therefore stands alone in this registry, with nothing documented here to compare it against on licence, hosting, data ownership or cost.

When to use it — and when not to

The facts here do not mention a database, file storage, SMTP, or any other component a self-hoster would have to operate, so no operational cost can be estimated from this page. Anyone who needs a documented install path, a stated licence, a declared language, or evidence of recent releases should treat that as a gap in this listing and go to the Codeberg repository instead. The last push recorded here is December 2023, the entry declares no topics, and the README is a one-line redirect, so this page is best read as a pointer rather than as project documentation.