SimpleGo ships with its own independent SimpleX transport network — 10 dedicated routers operated by SimpleGo, forming infrastructure parallel to the internet. Every SimpleGo device works out of the box using our routers, while remaining fully compatible with the entire SimpleX ecosystem. You can also run your own router, use SimpleX official routers, or opt for our managed private infrastructure.
Every SimpleGo device ships pre-configured with these 10 dedicated routers. All routers support SMP with message routing (forwarding), TLS 1.3 on port 5223, and are operated exclusively by SimpleGo from German infrastructure. No SimpleX Chat routers are required — your device works independently out of the box.
All 10 SimpleGo SMP servers are currently being deployed and will be activated within the next 30 days. Server addresses include TLS certificate fingerprints for man-in-the-middle protection. Onion v3 addresses will follow after clearnet deployment is complete.
SimpleGo devices work with their own servers by default — but the SimpleX Protocol's design means you're never locked in. Every SimpleGo device is fully compatible with the entire SimpleX network: official servers, community servers, Flux servers, self-hosted instances, or any combination.
In the SimpleX Protocol, the recipient always chooses which server hosts their message queue. This is the key to seamless interoperability. When you scan the QR code or invitation link of any SimpleX user — regardless of which servers they use — the connection is established automatically using their server for their queue and your server for your queue.
This means a SimpleGo device using exclusively SimpleGo servers can communicate with someone whose SimpleX app uses the official simplex.im servers, a community server in Finland, or a self-hosted instance on a Raspberry Pi. Each side manages their own queue on their own server. The protocol handles everything transparently.
The result: you can run a completely private infrastructure for your organization while every member remains fully reachable by the outside SimpleX world. No walled gardens, no lock-in, no compromise.
SimpleGo places zero restrictions on server selection. You can use exclusively SimpleGo servers, exclusively SimpleX official servers, community servers, your own self-hosted server, or any combination — all configurable directly on the device. The system is completely open, and switching servers does not affect existing conversations.
SimpleX routers are fundamentally different from the servers used by Signal, WhatsApp, or Telegram. They are simple message mailboxes that know nothing about users, contacts, or conversation history.
Each SMP server hosts one-way message queues. A sender pushes encrypted messages into a queue; the recipient pulls them out. The server never sees both sides of a conversation — it only knows one direction of one queue. Different queues for the same conversation can be on entirely different servers.
SMP servers have no concept of "users." There are no accounts, no logins, no registration. Queues are identified by random cryptographic IDs. The server cannot determine which queues belong to the same person, or whether two queues carry messages for the same conversation.
The receiving party chooses which server hosts their queue — and can change it at any time. SimpleGo can use its own servers, SimpleX official servers, community servers, or your self-hosted instance. You can even use different servers for different contacts.
Neither router knows both sender and recipient. The forwarding router strips its onion layer and forwards; the destination router re-encrypts for the recipient. All SimpleGo routers support both SMP and routing roles.
Even if every router were operated by an adversary, the SimpleX protocol's layered encryption and unidirectional queue architecture prevents meaningful surveillance.
| Information | Traditional Server | SimpleX Router |
|---|---|---|
| Message content | Often accessible (Telegram server-side, email plaintext) | Four nested encryption layers — impossible |
| Sender identity | Known via account / phone number | Unknown — no accounts exist |
| Recipient identity | Known via account / phone number | Unknown — queue IDs are random |
| Who talks to whom | Full contact graph available | Cannot correlate — queues are unlinkable |
| Message timestamps | Exact delivery timestamps logged | Connection timestamps only (no message metadata) |
| Message frequency | Full pattern available | Obscured by fixed 16KB padding and batching |
| User's IP address | Logged per connection | Visible per connection — use Tor for protection |
| Group membership | Complete group lists stored | No concept of groups — only individual queues |
| Message history | Stored indefinitely on servers | Deleted after delivery — no permanent storage |
SimpleGo offers infrastructure for every use case — from free public routers to fully managed private deployments with contractual guarantees.
For maximum control, run your own SimpleX router. SimpleX routers are lightweight — they run on any Linux system, including a Raspberry Pi. Your SimpleGo device can be configured to use your private server exclusively, or as one of several servers in rotation.
Any Linux VPS or dedicated server (Ubuntu recommended)
A domain name pointed at the server
Port 5223 open (or 443 for websocket mode)
Minimal resources — runs on 512MB RAM
Optional: Tor for onion routing support
Full documentation: simplex.chat/docs/server.html
For files larger than the 16KB SMP message limit, SimpleX uses XFTP — a separate file transfer protocol with the same privacy properties. Files are encrypted, chunked, and distributed across multiple servers. No single server ever holds a complete file.
Files are padded to the nearest 256-byte boundary, encrypted with a random symmetric key, then split into chunks distributed across multiple XFTP servers. The symmetric key and chunk locations are sent via SMP as a regular encrypted message. The recipient downloads chunks from different servers and reassembles the file locally.
XFTP support is on the SimpleGo roadmap for post-MVP development. The initial focus is text messaging via SMP. File transfer will be added once the core messaging stack is production-ready, with files stored on the device's encrypted SD card using AES-256-GCM.
See how SimpleGo's 4-layer per-message encryption protects every message from device to device.
SimpleGo operates 10 dedicated SimpleX routers (smp.simplego.dev through smp9.simplego.dev) for secure hardware messaging devices. Every SimpleGo device ships pre-configured with these servers and works independently of the SimpleX Chat official server infrastructure. All servers support SMP message routing (forwarding) for Private Message Routing, TLS 1.3 encryption on port 5223, and are hosted on German infrastructure by IONOS SE with full GDPR compliance.
SimpleGo devices are fully compatible with the entire SimpleX messaging ecosystem. When a SimpleGo user scans a QR code or invitation link from a SimpleX Chat app user who uses different servers, the connection is established automatically across server boundaries. The SimpleX Protocol's design — where each recipient chooses their own server — enables seamless cross-server communication without any configuration. Users can also optionally enable SimpleX official servers, community servers, Flux servers, or self-hosted SMP instances directly on the device.
For organizations requiring dedicated infrastructure, SimpleGo offers managed private SMP server clusters with Onion v3 client authorization, SMP password protection, custom domains or onion-only operation, and contractual SLA guarantees. Private infrastructure contracts require KYC identity verification of the contracting party. Even with private infrastructure, users remain fully compatible with the public SimpleX network.
SimpleGo SimpleX router list 2026, dedicated encrypted messaging router Germany, SimpleX compatible hardware router, private SMP infrastructure managed hosting, onion v3 client authorized messaging, KYC verified secure router, German GDPR messaging infrastructure, SimpleX ecosystem hardware device servers, cross-server encrypted communication, decentralized messaging router network.