Free Speech Hosting — Legal Content, No Keyword Police

Free-speech hosting on Reykjavik and Zurich racks: no content scanning, copyright mail closed, SKN entity, token signup. Legal content only, AUP enforced.

نص المقال الطويل بالإنجليزية. الواجهة والكتالوج والدفع مترجمة.

What free-speech hosting means here

Three commitments, each checkable. No keyword or content scanning of what you host — abuse is handled on external reports, never by crawling customers. Copyright-only mail is closed without action on the content. Takedown demands carry weight only from law enforcement of the facility jurisdiction; private “content police” services get nothing. The contract entity is Meridian Node Ltd. (Saint Kitts and Nevis), and the speech-friendly racks — Reykjavik, Zurich — are in the catalog by design, not by accident.

What you can host

• Political, controversial and dissenting viewpoints of every orientation.
• Journalism, archives, whistle-blower-adjacent resources that obey criminal law.
• Legal adult content (RTA-labelled, 2257-compliant).
• Tor relays, bridges, onion services — explicitly allowed.

The common thread is lawfulness: none of the four categories needs a promise extracted under pressure. The signup takes an inbox or a bare token, and the no-email signup path keeps your name off the billing file entirely.

The boundary, stated once

Free speech covers lawful speech. CSAM, phishing, spam, paid attacks and credible threats are prohibited and enforced — the AUP lists them plainly. A project that needs criminal conduct hosted will not find an honest provider anywhere, and pretending otherwise would be the first lie on this page.

Which locations fit best

• Reykjavik — Iceland’s speech tradition, no mandatory retention, geothermal power.
• Zurich — outside the EU, Swiss judicial oversight of data requests.
• Sao Paulo / Bucharest — regional speech markets with EU-adjacent process.

The rest of the stack stays yours

The rack is one layer of a speech project. A registrar that matches the threat model, DNS with a short TTL before any cutover, and TLS from a CA that does not demand more than the law does — each choice either preserves or spends the hosting layer's restraint. Start with a token-paid VPS, keep the domain decision deliberate, and document what each vendor holds so the whole picture stays legible under pressure.