Anonymous Keys DPI is a free and open-source Android privacy and connectivity application built for people who live, travel, study, or work in countries where Internet access is restricted by heavy filtering, Deep Packet Inspection (DPI), network interference, or widespread censorship.
Anonymous Keys DPI combines an Android VPN interface, Xray-core, a native ByeDPI layer, local SOCKS chaining, routing controls, and practical connection testing in one application.
The project is intended for environments where ordinary connections may be blocked, throttled, reset, filtered, or inspected. Its goal is to make advanced connectivity tools more accessible without hiding the underlying controls from experienced users.
This repository began from open-source networking projects, but the current application has its own Anonymous Keys identity, user interface, release pipeline, application ID, release certificate, community links, and integrated DPI-bypass workflow.
Anonymous Keys DPI is not a commercial VPN service and does not provide a server subscription. Users connect with their own compatible configurations and infrastructure.
Access to information should not depend on where a person lives.
In many regions, Internet censorship is not an occasional inconvenience. It is part of everyday life. Websites, social platforms, news sources, messaging services, and independent resources may be blocked or made unreliable through DNS interference, IP filtering, traffic shaping, connection resets, and DPI.
Anonymous Keys DPI was created to help users in these environments:
- reach lawful information and communication services;
- use compatible Xray configurations from a single Android client;
- apply ByeDPI strategies when DPI interferes with a connection;
- test connectivity quickly and adjust settings without rebuilding the app;
- keep a transparent, auditable, open-source tool available to the community.
The project does not promise universal access. Network restrictions differ between providers, regions, protocols, destinations, and time periods. A method that works today may require adjustment tomorrow.
- Android VPN service
- Xray-core integration
- Native ByeDPI / ciadpi support
- Local SOCKS chaining between Xray and ByeDPI
- tun2socks integration
- VPN socket protection
- Per-destination routing support
- Built-in DPI bypass switch
- Automatic and manual ByeDPI profiles
- Strategy presets
- Split-position controls
- Remembered successful strategy groups
- Fast delay and connectivity testing
- Compatible Xray configuration handling
- JSON configuration import
- Subscription and profile management inherited from the client foundation
- Routing settings
- Log viewer
- Backup and restore tools
- Dark-only interface
- Purple and cyan visual identity
- Anonymous Keys dragon artwork
- Custom launcher icon and splash screen
- Branded navigation drawer
- Direct GitHub and Telegram links
- Officially signed APK releases
- Automatic GitHub Release publishing
A typical protected connection follows this path:
Android applications
│
▼
Android VPN / TUN
│
▼
tun2socks
│
▼
Xray-core
│
▼
Local ByeDPI SOCKS layer
│
▼
User-configured VPN / proxy server
│
▼
Internet
ByeDPI is used as a local transport-processing layer. It does not replace the user's Xray server configuration.
Official builds are published in GitHub Releases.
Download:
Anonymous_keys_dpi.apk
A checksum is published beside every automated release:
Anonymous_keys_dpi.apk.sha256
- Open the latest release.
- Download
Anonymous_keys_dpi.apk. - Allow installation from the browser or file manager when Android asks.
- Install the APK.
- Import or create a compatible connection profile.
- Review the routing and DPI settings before connecting.
Anonymous Keys DPI now uses the official Anonymous Keys signing certificate.
Android only allows an installed application to be updated by another APK signed with a compatible certificate. If an older build was signed with a different certificate, Android may require you to uninstall it before installing the official release.
Export important configurations before uninstalling an older build.
All future official Anonymous Keys updates are intended to use the same release key.
On Linux, macOS, or Termux:
sha256sum Anonymous_keys_dpi.apk
cat Anonymous_keys_dpi.apk.sha256The hashes must match exactly.
With Android SDK Build Tools installed:
apksigner verify --verbose --print-certs Anonymous_keys_dpi.apkOnly download release files from the official repository:
https://github.com/anonymouskeys/Project-X
- Install the latest official APK.
- Open Anonymous Keys.
- Import your compatible Xray configuration or subscription.
- Select a profile.
- Open DPI settings when your network requires bypass strategies.
- Start with an automatic or moderate preset.
- Run a delay test.
- Connect.
- Review the log if the connection fails.
DPI behavior is network-specific. Avoid assuming that the strongest preset is always the best one. More aggressive fragmentation or manipulation may reduce performance or break otherwise functional destinations.
- Android 8.0 or newer
- A compatible Xray configuration or subscription
- Network access
- Permission to create an Android VPN connection
- A server or service you are authorized to use
Some features and protocols may depend on the included native libraries, Android version, device vendor, and server configuration.
Development news, release announcements, project updates, and community information are published in the official Telegram channel:
https://t.me/anonymouskeys
Please use GitHub Issues for reproducible technical bugs. Do not post private keys, subscription links, server credentials, passwords, or sensitive logs in public channels.
Anonymous Keys DPI is developed and maintained with personal time and resources.
Voluntary donations can help with:
- development and maintenance;
- Android testing devices;
- server and infrastructure expenses;
- debugging across different networks;
- documentation and translations;
- future privacy and anti-censorship features.
Donations are optional and do not unlock paid features.
Send only assets supported by the TON wallet to this address:
UQCezHtAYYkC0eJW26rkXgdT4fG9f9m6m-3oQanpd4bpyrEG
Send only USDT using the TRC20 network to this address:
TYUFWzRdicVgUgAf5HCPTVGHr6J7p2Kxrf
Always verify the address and network before sending. Cryptocurrency transactions are generally irreversible. Sending an unsupported asset or using the wrong network can permanently lose funds.
Thank you for supporting the continued development of Anonymous Keys. ❤️
- Anonymous Keys DPI is a client application.
- The project does not operate or guarantee the privacy of third-party servers.
- A server operator may be able to observe connection metadata or unencrypted traffic reaching that server.
- Use encrypted protocols and infrastructure you trust.
- Review imported JSON and subscription sources before using them.
- Do not install APK files from unofficial mirrors unless you independently verify their signature and checksum.
- Logs may contain hostnames, IP addresses, profile names, or diagnostic details. Review them before sharing.
No networking application can guarantee anonymity by itself. Privacy depends on the complete system: device, configuration, server, protocol, DNS behavior, applications, browser state, accounts, and user behavior.
Anonymous Keys DPI is intended for legitimate privacy, interoperability, research, communication, and access to information.
Users are responsible for understanding and complying with laws, regulations, contracts, workplace policies, school policies, and service terms applicable to them.
The maintainers do not encourage unlawful access, attacks, credential theft, fraud, harassment, malware distribution, or interference with systems and networks.
The installed app may have been signed with another certificate. Export your configuration, uninstall the old build, and install the official release.
Check:
- whether the profile itself works;
- DNS and routing settings;
- server availability;
- the selected ByeDPI preset;
- the application log;
- whether the destination is blocked by a different method.
DPI bypass is not a simple strength scale. Different strategies alter traffic in different ways. Use the least disruptive working preset.
The service itself may be filtered. Try a working connection, another network, or a trusted access method available in your region.
A failed test may indicate server failure, routing problems, blocked test destinations, DNS issues, or an incompatible DPI strategy. It does not always mean the entire profile is unusable.
The Android project is located in:
V2rayNG/
The complete GitHub Actions build also compiles native components and the Xray Android library before running Gradle.
Important parts include:
AndroidLibXrayLite/ Xray Android library
V2rayNG/ Android application
compile-tun2socks.sh tun2socks build
compile-byedpi.sh ByeDPI native build
.github/workflows/ CI, signing, and release automation
Official CI currently uses Java 17, Android NDK r27, Go, gomobile, and Gradle.
The signed F-Droid universal artifact is produced as:
V2rayNG/app/build/outputs/apk/fdroid/debug/Anonymous_keys_dpi.apk
Release signing secrets are not stored in the repository.
Official releases are created from version tags:
git tag -a v1.0.1 -m "Anonymous Keys DPI v1.0.1"
git push origin v1.0.1For a matching v* tag, GitHub Actions:
- builds native tun2socks;
- builds native ByeDPI;
- builds the Xray Android library;
- restores the signing key from encrypted repository secrets;
- builds the APK;
- verifies its signature;
- calculates SHA-256;
- creates or updates the GitHub Release;
- uploads the APK and checksum.
Never move or reuse a published release tag.
Contributions are welcome.
Useful contributions include:
- reproducible bug reports;
- Android compatibility fixes;
- translations;
- documentation improvements;
- accessibility improvements;
- carefully tested DPI presets;
- UI and UX improvements;
- build-system maintenance;
- security reviews.
Before submitting an issue:
- Check existing issues.
- Test the latest release.
- Remove private information from logs.
- Describe the Android version, device, network type, profile type, selected DPI settings, and exact result.
- Include clear reproduction steps.
Before submitting a pull request:
- Keep changes focused.
- Explain why the change is needed.
- Avoid committing credentials, keystores, subscriptions, or generated build output.
- Confirm that the project builds.
- Describe how the change was tested.
Possible future directions include:
- improved automatic DPI strategy selection;
- clearer diagnostics and guided troubleshooting;
- additional routing controls;
- better import and export workflows;
- improved accessibility;
- more translations;
- expanded documentation;
- broader device and Android-version testing;
- carefully evaluated support for additional anti-censorship transports;
- desktop companion tools where appropriate.
Roadmap items are not guarantees and may change based on testing, security, maintenance cost, and community feedback.
No. It is an Android client. You need a compatible configuration and server or service.
No. In this project, ByeDPI is integrated into the local connection chain and works alongside Xray.
No. Censorship systems and provider behavior vary. Configuration and strategy selection may need adjustment.
The application alone cannot guarantee anonymity. See the privacy and security notes above.
The filename is part of the independent Anonymous Keys release identity and is used consistently by the automated release workflow.
Join the official Telegram channel:
https://t.me/anonymouskeys
Use GitHub Issues:
https://github.com/anonymouskeys/Project-X/issues
Anonymous Keys DPI exists because of the work of many open-source developers.
The project includes or builds upon components and ideas from:
- v2rayNG
- Xray-core
- ByeDPI
- tun2socks and BadVPN-related components
- Android, Go, Kotlin, Gradle, and their open-source ecosystems
Please respect the licenses and attribution requirements of all included components.
See the repository's LICENSE file and the license files included
with individual third-party components.
Different bundled components may be distributed under different compatible licenses. Their original notices remain authoritative for those components.