About Simple Web

Simple Web is a community-maintained directory of privacy-focused web frontends and public instances. It helps people reach online services without handing over more personal data than they need to.

Our mission

Useful online services should not depend on surveillance-based business models. Privacy-focused web frontends show that it is technically possible to provide real functionality while respecting user privacy. That is the point here, and it is a fairly practical one.

Simple Web exists to make these tools easier to find and easier to use. That means clear documentation, reliable instance directories, and guidance that works for both experienced users and people who are only just getting comfortable with the idea. The aim is not to push a particular technology for its own sake, but to explain what is available and where the rough edges are.

What we provide

• Comprehensive directories of privacy-focused web frontends across multiple service categories
• Curated instance directories with coverage of HTTPS, Tor, I2P, and Loki network access methods
• Practical guides on using privacy frontends safely and choosing reliable instances
• Clear, accessible documentation that respects users\' intelligence while avoiding unnecessary jargon

How the directory is handled

The directory is kept neutral and informational. It does not promote specific instances or operators, because that would defeat the point. Users need enough detail to make their own decisions based on their requirements, threat models, and technical comfort.

The projects and instances documented here are run by independent volunteers and organisations. Simple Web does not operate instances, and it does not claim authorship of the privacy frontend projects it documents. The role is narrower than that: curator, index, and guide.

Technical setup

This site is built as a static Next.js application and deployed on Cloudflare Pages. That keeps the stack simple, the delivery fast, and the attack surface smaller than a site built around server-side processing or a database. All content is generated at build time.

Standard web security practices are in place, including Content Security Policyheaders, secure SSL/TLS configuration, and careful management of external resources. The broader point is simple: privacy-focused documentation should not need heavy tracking or analytics infrastructure to exist.

Contact and feedback

Feedback is welcome if something is inaccurate, out of date, or could be explained more clearly. Visit our contact page for information on how to reach us.