Privacy frontend hosting

Your private frontends, hosted and maintained

Privacy-respecting frontends, hosted and maintained for you: Redlib, Invidious, SearXNG, Nitter-style instances. Always updated, always up. We keep the image, the updates and the egress; you keep an instance that’s yours, with no ads and no tracking.

This is hosting built as a managed service: one dashboard, one invoice, and the hard part — the rotating residential egress that upstreams block — handled for you.

Who it’s for

• Privacy-conscious individuals — you want your own reliable instance, without depending on an overloaded or blocked public one. The Essential tier is enough.
• Collectives and journalists — you share stable access to several frontends. The Pro tier covers Invidious, SearXNG and more.
• Sovereignty-minded organizations — you host the whole catalogue under a single contract. The Signature tier unlocks the Suite discount.

What’s managed

Responsibilities are split clearly and in writing:

• We manage: the image build (glibc TLS fixes included) and updates.
• We manage: rotating residential proxy egress — the hard part, because providers block static IPs.
• We manage: token plumbing (po-token), the Tor overlay and monitoring.
• You manage: your instance’s branding and its terms of use.
• Shared: the choice of frontends by tier.

Features included

• A private instance that’s yours, with no ads and no tracking
• Managed rotating residential proxy egress (dedicated by tier)
• Optional .onion Tor overlay on the Pro and Signature tiers
• Automatic update channel (weekly to daily by tier)
• Anti-bot and rate-limiting (Anubis) included
• Custom domain on every tier
• Catalogue: Redlib, Invidious, SearXNG, Nitter-style instances
• FR + EN support, chat within 2 business hours (Signature tier)

The Essential, Pro and Signature tiers, with their published prices and quotas, are detailed in the table below.

Security included

Every instance is isolated, fronted by anti-bot and served through a managed residential egress, with no exposed static IP. Images are rebuilt and patched continuously, the Tor overlay is available, and monitoring runs in the background. You keep control of your instance; we keep the infrastructure hardened and current.

Frequently asked questions

Are these frontends legal?

They are alternative clients to public services, for personal use. You remain responsible for your usage and your terms; we provide the hosting and maintenance.

Why a residential proxy?

Because upstream services block data-center and static IPs. A rotating residential egress keeps your instance working where a shared instance fails.

Why my own instance rather than a public one?

For reliability: no shared-IP blocks, no overload, no outage right when you need it. Your instance, your uptime.

The YouTube po-token breaks sometimes, doesn’t it?

Yes, it happens when the upstream changes. We commit to fixing it as a priority, within 48 hours on average — which is exactly what you’re delegating.

Can I have a .onion and my own domain?

Yes: the .onion Tor overlay is available on the Pro and Signature tiers, and the custom domain on every tier.