Sendant provides a robust framework for secure messaging for intermittent networks, ensuring that critical communications remain private and intact even when connectivity is unreliable. By utilizing a persistent, low-bandwidth architecture, Sendant minimizes the impact of high-latency environments, allowing journalists, NGOs, and field teams to maintain secure contact without the need for constant, high-speed internet access. The platform is designed to handle the realities of field operations where infrastructure is often compromised or intentionally throttled.
The Reality of Secure Messaging for Intermittent Networks
In environments where network infrastructure is fragile—such as during humanitarian crises, in remote field locations, or under active network throttling—standard communication protocols often fail. Many messaging applications are built on the assumption of a persistent, high-speed connection. When the signal drops or bandwidth is severely limited, these apps frequently time out, lose synchronization, or fail to deliver messages entirely.
The primary challenge of secure messaging for intermittent networks is the overhead of the handshake process. Secure messaging protocols typically require a back-and-forth exchange of cryptographic keys to establish a session. According to the Internet Engineering Task Force (IETF), high-latency environments exacerbate the "head-of-line blocking" problem, where a single lost packet stalls the entire communication stream. If the connection is severed mid-handshake, the process must restart, leading to a loop of failed attempts that consumes data and battery life. This is particularly problematic for users relying on satellite uplinks or congested cellular towers where packet loss is a frequent occurrence.
Furthermore, standard protocols often struggle with out-of-order delivery. In a high-latency environment, packets may arrive out of sequence, causing the application to discard them as invalid or corrupted. Optimizing for intermittent connectivity requires specific architectural patterns that prioritize data integrity over real-time synchronization. Without a system designed to queue and re-verify messages when the connection returns, users are left with messages that rarely reach their intended recipient. Sendant mitigates this by maintaining a stateful connection that resumes precisely where it left off, rather than forcing a full re-authentication cycle.
How Sendant Maintains Connectivity on Throttled Networks
Sendant addresses the challenges of messaging on throttled networks by stripping away unnecessary data overhead and prioritizing the delivery of encrypted payloads. Unlike applications that transmit large metadata headers or unnecessary background telemetry, Sendant’s communication packets are optimized to be as lightweight as possible. This efficiency ensures that even on 2G connections or heavily congested networks, the essential content of your message can traverse the bandwidth bottleneck.
A critical component of this resilience is the Sendant offline mailbox. When a recipient is offline or the network is too unstable to complete a transmission, Sendant does not simply discard the attempt. Instead, messages are queued securely in an offline mailbox. Once the connection is re-established, Sendant automatically reconciles the state of the conversation, delivering the queued messages in the correct sequence. This ensures that even if a user only has a few seconds of connectivity, their messages are successfully pushed to the server.
Sendant keeps working over throttled, restricted, or intermittent networks and can deliver later via an offline mailbox; it is not a radio-mesh app and does not work with no network at all. It requires some level of connectivity to facilitate the exchange. By acknowledging this limitation, we ensure our users have realistic expectations about the performance of the platform in extreme conditions. We prioritize transparency regarding the physical requirements of the network, ensuring that users do not rely on the service in scenarios where absolutely no signal is available.
Technical Foundations: X3DH and Double Ratchet in Practice
The security of your communications is paramount, especially when navigating unpredictable network conditions. Sendant is built on X3DH + Double Ratchet — the same primitives Signal uses — with publicly documented architecture. As detailed in the Signal Protocol documentation, these cryptographic primitives provide forward secrecy and post-compromise security, ensuring that even if a session key is compromised in the future, past messages remain unreadable. An independent audit is planned; Sendant has not yet been audited.
The implementation of these primitives allows us to maintain security even when the network is unreliable. Because X3DH allows for asynchronous key exchange, we can establish secure channels even when both parties are not online at the same time, which is a significant advantage for secure messaging for intermittent networks. This asynchronous capability means that the handshake does not need to be completed in a single, uninterrupted burst of data, making it far more resilient to the "drop-out" nature of unstable connections.
Browser-Based Flexibility for Secure Messaging
One of the most powerful features of our platform is the only identifier-free messenger with a persistent, full-featured no-install browser client. By operating directly within the browser, Sendant avoids the limitations often associated with native applications that require constant background synchronization and large updates. This architecture is particularly useful for teams operating in environments where installing software is restricted or where device security policies are strictly enforced.
For users on the move, this flexibility is a practical advantage. Sendant works on an iPhone right now, in the browser — there is no native iOS app. Because the browser client is designed for web-standard performance, it handles network interruptions more gracefully than many native apps. When the browser detects a loss of connectivity, it enters a state of "graceful degradation," caching the current state and waiting for the network to return to resume transmission, rather than crashing or clearing the session. This allows users to continue drafting messages or reviewing previous threads even while offline, with the app automatically syncing once a connection is detected.
This approach is particularly beneficial for teams who cannot rely on centralized app stores or who need to access their communications across a variety of hardware without installing permanent, potentially trackable software on every device. You can access your secure workspace from any device, provided you have your credentials. This portability ensures that your communication stream is not tied to a single piece of hardware, which is a critical consideration for journalists and field workers who may need to switch devices rapidly in high-risk scenarios.
Metadata and Privacy in Challenging Network Conditions
Privacy is not just about the content of your messages; it is about the footprint you leave behind. Sendant's servers see only ciphertext (message content). Sendant does not claim to hide network-level metadata such as IP addresses. In the context of privacy-focused messaging, it is common for apps to make sweeping claims about "hiding everything." We believe in transparency. For users who require absolute network-level anonymity, we recommend pairing Sendant with trusted, professional-grade VPN or Tor-based routing solutions, as recommended by the Electronic Frontier Foundation for masking origin IP addresses.
This honesty is part of our commitment to our users. We do not use marketing-speak to hide the technical realities of how the internet works. By understanding that the server acts as a relay for encrypted data, you can make informed decisions about how to layer your security measures when working in high-risk environments. We encourage our users to adopt a defense-in-depth strategy, using Sendant for end-to-end encrypted content while utilizing external tools to manage network-level visibility if their threat model requires it.
Comparing Approaches to Network Resilience
When choosing a messenger for challenging environments, it is helpful to look at how different architectures handle the trade-offs between security, usability, and network resilience. The following comparison highlights why Sendant is uniquely positioned for professional use cases:
- Sendant: Optimized for minimal, throttled connectivity with an offline mailbox and browser-based access, ensuring that messages are queued and delivered as soon as a connection is detected.
- Standard Messengers: Generally require persistent, high-speed connections; often fail in low-bandwidth scenarios because they rely on continuous real-time socket connections that time out under latency.
- Mesh-Based Apps: Operate without traditional internet but require physical proximity between devices, which is often impractical for global communication or coordination between distant teams.
Sendant sits in a strategic middle ground. While mesh apps require physical proximity, and standard apps require robust data plans, Sendant provides a persistent, web-based experience that thrives where others struggle. For NGOs and journalists, the ability to switch between devices and maintain an offline mailbox is a strategic advantage. It allows for a consistent workflow that does not break when moving between a stable office network and a restricted field environment.
Best Practices for Maintaining Communication in Restricted Zones
- Utilize the Offline Mailbox: If you are in a location with known outages, compose your messages while connected, but do not worry if they remain in "pending" status. The offline mailbox will hold them until the network detects a path to the server.
- Keep Your Session Active: If you are using the browser client, keep the tab open. Sendant is designed to attempt silent reconnections in the background. Closing and reopening the tab forces a full state reload, which can be bandwidth-intensive.
- Manage Media Expectations: When bandwidth is low, prioritize text-based communication. While Sendant can handle attachments, large files will naturally take longer to transmit over throttled connections.
- Use Reliable Networks: Even with our optimizations, a stable connection is often better than a poor one. If you are near a public Wi-Fi hotspot or a local network, use it to sync your inbox before heading back into a restricted zone.
- Monitor Battery and Data Usage: In extreme environments, keep an eye on your device's power consumption. While Sendant is efficient, maintaining a persistent browser session can consume more energy than a static page; ensure your device is charged before entering areas with limited power infrastructure.
Frequently Asked Questions
Does Sendant work without any internet connection?
No. Sendant keeps working over throttled, restricted, or intermittent networks and can deliver later via an offline mailbox; it is not a radio-mesh app and does not work with no network at all.
Is Sendant an open-source messenger?
Sendant is built on X3DH + Double Ratchet — the same primitives Signal uses — with publicly documented architecture. Sendant's source code is not public.
Can I use Sendant on my iPhone?
Yes. Sendant works on an iPhone right now, in the browser — there is no native iOS app.
Does Sendant hide my IP address?
No. Sendant's servers see only ciphertext (message content). Sendant does not claim to hide network-level metadata such as IP addresses.
What happens to my messages if the network fails while sending?
If the network fails, your message is safely queued in our offline mailbox. Sendant will automatically attempt to deliver the message once the connection is restored, ensuring that your communication remains intact and in the correct order. You can learn more about this in our documentation on network failures.
Ready to experience reliable, private communication? Sign up for Sendant today and stay connected regardless of your network conditions.