SimplyTranslate Instances
Public instance directory and access guide
SimplyTranslate operates through a distributed network of public instances, each providing privacy-focused translation services. This directory helps you find and access instances across different networks and protocols, from standard HTTPS connections to privacy networks like Tor, I2P, and Loki.
Available Access Methods
HTTPS Instances
Standard web access through secure HTTPS connections. Accessible from any modern browser without additional software.
Onion Service (Tor)
Tor hidden services providing network-level anonymity. Requires Tor Browser or properly configured Tor client.
I2P Network
Instances within the Invisible Internet Project network. Requires I2P router installation and configuration.
Loki Network
Services on the Lokinet anonymity network. Requires Lokinet client software for access.
Understanding Public Instances
A public instance is a server that runs the SimplyTranslate software and makes it accessible to users. Each instance is independently operated by volunteers, privacy organizations, or community members who dedicate resources to maintaining privacy-friendly services. When you use a public instance, you connect to that specific server rather than a centralized service.
Different instances may have varying capabilities, performance characteristics, and privacy features. Some instances are accessible through standard web browsers via HTTPS, while others operate on privacy networks that require specialized software. The choice of instance depends on your specific privacy requirements, technical capabilities, and threat model.
Public instances rely on community support and volunteer effort. Instance availability, performance, and features can vary based on server resources, maintenance schedules, and operator decisions. This decentralized model prevents single points of failure and control, but it also means that users should familiarize themselves with multiple instances for reliability.
Benefits and Considerations
Benefits
- •No account registration or personal information required
- •Community-operated infrastructure resistant to centralized control
- •Multiple access methods across different privacy networks
- •Free to use with no monetization through advertising or data sales
- •Diverse instance locations and jurisdictions for different privacy needs
Considerations
- •Instance availability not guaranteed; operators maintain services voluntarily
- •Performance varies based on server resources and user load
- •Features and translation engine availability differ between instances
- •No customer support or service level agreements
- •Users must evaluate trustworthiness of instance operators
Choosing the Right Access Method
For most general usage, standard HTTPS instances provide good privacy protection with easy access through any modern web browser. These instances are suitable when your primary concern is avoiding tracking by translation services rather than hiding your translation activity from network observers.
When translating sensitive content that you prefer to keep private from your internet service provider or network administrators, consider using instances accessible through Tor (Onion services). Tor instances provide network-level privacy by routing your connections through the Tor network, making it difficult to determine what services you are accessing.
For users already participating in alternative networks like I2P or Loki, instances on these networks provide integrated privacy within those ecosystems. These options are particularly relevant for users who prioritize using decentralized, privacy-focused network infrastructure for all their online activities.
Instance Selection Safety Checklist
- Verify that you are connecting to the intended instance by carefully checking URLs and certificates
- Test instance responsiveness and translation quality before relying on it for important tasks
- Bookmark multiple instances to ensure continued access if your primary choice becomes unavailable
- Consider the geographic location and legal jurisdiction of instances for your use case
- Be aware that instance operators can technically access translation requests, even on privacy networks
- Monitor for any unusual behavior such as unexpected redirects or requests for personal information
- Use browser developer tools to verify that translations are being processed without unexpected external connections
- Rotate between different instances periodically to avoid building correlatable usage patterns
Related Resources
This page is maintained as a static reference to keep URLs predictable and safe.
Last updated: January 15, 2026