RELEASES. 0/3 sources detected

Protected delivery belongs here.

Downloads are now a first-class Aegis surface. This page does not expose raw project folders; it creates the delivery lane where installers, launchers, protected tools, and customer entitlements can be routed through Auth, Store, and the Aegis Launcher.

LANES. Delivery Map

Release targets.

Each card is driven by config/releases.php. When builds are ready, these lanes can point at signed installers, protected files, or Auth-backed entitlements instead of raw folders.

Launcher Login Required

Aegis Update Launcher

Branded updater and boot sequence surface for Aegis desktop releases.

Channel: Desktop
Product: Aegis UpdateLauncher
Source: not detected yet
Access: checkout or redeem required
License: not issued
HWID: not validated

Launcher Login Required

Aegis Launcher

Authenticated launcher package for account-aware product access and future entitlement-gated tool delivery.

Channel: Desktop
Product: Aegis Launcher
Source: not detected yet
Access: checkout or redeem required
License: not issued
HWID: not validated

Diagnostics Login Required

Aegis Troubleshooter

Authenticated troubleshooting package with EXE access, setup guide, launcher/update fixes, and common error recovery notes.

Channel: Desktop
Product: Aegis Troubleshooter
Source: not detected yet
Access: checkout or redeem required
License: not issued
HWID: not validated

SECURE. Delivery Rule

Never serve tool source directly.

The release center intentionally routes users to Store, Auth, the Customer Library, or launcher-managed fulfillment. Production downloads should be signed, entitlement-checked, logged, and served outside the public source tree.

Customer downloads belong behind Auth sessions Launcher metadata is reserved for authenticated runtime flows Raw project folders remain outside public download links Store can become the fulfillment authority