HydraBox

English / Русский

Subscription-first Android client for the Hydra self-hosted VPN stack.

HydraBox imports, refreshes, stores, and activates one encrypted subscription from a server you control. HYDRA Ultimate produces that subscription; HydraCore validates and executes its native networking configuration.

HYDRA Ultimate  ->  encrypted subscription  ->  HydraBox  ->  HydraCore
self-hosted server                               client        runtime

Hydra is not a hosted VPN provider. HydraBox does not sell or provision servers: you own the server and subscription.

Status

HydraBox is in public beta. Android is the supported production target. Other Flutter platform folders remain source-compatible development targets, not a release promise.

Features

• Android VPN TUN mode powered by HydraCore.
• Hydra Subscription v2 with JWE A256GCM transport and independent, lossless storage of each native resource document.
• Automatic fail-closed requested_permissions validation with no user prompt or pending grant state.
• HydraCore API v2 runtime snapshots, sequenced events, and managed URL-test sessions over one persistent command connection.
• Fail-closed capability and remote-safety validation before activation.
• URL, QR, file, clipboard, and deep-link subscription import.
• Local HTTP/SOCKS mixed proxy for manual clients.
• Split tunnelling, DNS/routing controls, server latency checks, updater, and redacted diagnostics.
• Manual link/config imports for interoperability; Hydra Subscription v2 is the product contract.

Quick start

1. Deploy HYDRA Ultimate on a server you control.
2. Copy its encrypted Hydra subscription URL or QR code.
3. Install HydraBox from GitHub Releases.
4. Import the subscription and connect.

The decryption key is carried only in the URL fragment and is not sent to the subscription server. The exact schema, trust boundary, validation rules, and test vectors are documented in HydraCore Subscription v2 contract.

Security model

HydraBox treats every remote subscription as untrusted input. Activation requires authenticated JWE decryption, schema validation, an exact compatible HydraCore policy manifest, removal of local-authority fields, a closed reference graph, and native config validation. Unknown future fields remain storable but cannot become executable merely because they exist in JSON.

Report vulnerabilities according to SECURITY.md. Never attach live subscription URLs, keys, credentials, device identifiers, or private server addresses to a public issue.

Development

The authoritative build and verification environment is GitHub Actions. It checks the pinned HydraCore artifact and provenance, Flutter analysis/tests, Android unit/lint/assembly gates, and CodeQL. Contributions target main; see CONTRIBUTING.md and GitHub Actions.

Credits and license

HydraBox began as a fork of Etonify by MeowTeam. We are grateful to the team and all upstream contributors whose work made this project possible. HydraBox is now maintained independently for the Hydra ecosystem while preserving the complete source history, corresponding source, copyright notices, and licenses. Exact lineage and retained compatibility identifiers are documented in CREDITS.md, NOTICE.md, and THIRD_PARTY_NOTICES.md. The project is distributed under GPL-3.0-or-later.