Victorious Framework

The Victorious Framework app fleet

Pre-release notice: Every APK on this site is a debug or pre-release build. Most have not been tested on a real device. Install only if you understand the risks. Do not treat these as finished software.

What is the fleet?

The Victorious Framework fleet is a family of Android apps (and a few related tools) built by one developer under the Victorious93 GitHub account. They are meant to work as a set: DroidCommand AI is the chat hub, and the other apps plug in as companions, independent nodes, a Termux environment, a mesh VPN, or local host tools — each over a documented integration class rather than one giant monolith.

What that looks like in practice (from the fleet docs and the apps themselves):

  • Shared design and branding — the same dark charcoal look, cyan-to-magenta neon accents, and Victorious logos across the apps that ship branding assets.
  • Shared build and CI patterns — multi-module Gradle/Kotlin (or Rust for EDL), GitHub Actions that assemble debug APKs, and a draft public fleet-manifest that can index release APKs by ABI and checksum.
  • How the apps work together — a published control map with classes such as bound companions (AIDL + signature permission + same signing key), external nodes (Messenger + shared JSON envelope, their own keys), Termux RUN_COMMAND IPC, and localhost host-process tools. Bound companions and several nodes speak a shared JSON bridge (protocol_major 1). External control stays off until you turn it on in each app.
  • Privacy and local-first where stated — for example Victorious Keyboard ships with no INTERNET permission; IdentityShield is a local KYC lab against its own simulator; Victorious Mesh holds the device’s single VpnService so other fleet apps can share one private tunnel instead of each running their own.
  • Root and power-user focus — host-phone USB toolkits, Termux/proot Linux, Magisk/KernelSU module workflows, dual-pane file tools with root/Shizuku paths, and a safety-first Qualcomm EDL companion (read-only identify today).
  • Open on GitHub where public — public repos link from each card; a few apps (messaging, launcher, spoof) are still private or empty, so this site lists them without download links.

None of this claims the fleet is finished or that every bridge is live. The hub docs mark control as partial or planned until it is runtime-verified. Every APK here remains debug or pre-release.

Download

Debug and pre-release APKs with source links. Each card shows version, license, capabilities, and download options when available.

Coming soon

Projects in progress. Repo links where public; no downloads yet. Expand a card for capabilities grounded in that project’s docs or code.

How to install an APK

  1. Open the download link on your Android device (or transfer the file to it).
  2. Enable installing apps from unknown sources for your browser or file manager (Settings → Apps → Special app access → Install unknown apps, or similar).
  3. Open the downloaded .apk and follow the system installer prompts.
  4. Verify the source: prefer the GitHub release page for the project, and check the version and file name before installing.
  5. Remember these are debug / pre-release builds — expect bugs, incomplete features, and possible package-id conflicts with other apps.