Not a switchboard.
The gateway behaves like a product entrance, not a deployment picker. It gives each runtime a clear role while keeping the decision quick.
Aura Gateway
Choose the host. Keep the same Aura reality.
One gateway introduces Aura's production stack, then hands you to the runtime or install channel that fits your device. Vercel, Netlify, and AWS CloudFront stay separate at the edge while account, cart, wishlist, checkout, profile, and order behavior keep one shared contract.
Choose your route
Three storefronts. One commerce core.
Pick the host you want to enter. The destination changes; Aura's production state and product posture do not.
aurapilot.vercel.app
Vercel primary runtime
aurapilot.netlify.app
Netlify mirrored runtime
dbtrhsolhec1s.cloudfront.net
AWS CloudFront secure runtime
Authentication continuity
Shared backend behavior
CloudFront edge parity
Checkout and order parity
Shared behavior contract.
Different domains and clouds are allowed. Behavioral drift is not. The install and storefront lanes keep the same core commerce expectations.
Install without guessing.
Desktop, mobile, tablet, browser-installed, and companion surfaces are named plainly so each device gets the strongest Aura lane it can actually run.
Desktop + mobile + PWA availability
Install Aura on the device you actually use.
Desktop links follow the latest desktop release. Android and Apple links follow the mobile release lane. iPadOS, ChromeOS, Unix/BSD, Indian Linux and Android-family OSes, HarmonyOS, and RTOS-family devices get explicit install or companion routes.
Release intelligence
Links below hydrate from GitHub Releases. If a specific package is not published yet, the button keeps you on the release page instead of sending you to a dead asset.
Checking latest desktop release...
Checking latest mobile release...
Windows
For everyday PC users
Choose the standard installer for most laptops and desktops. Portable builds are available when you do not want an installer.
Free Windows builds are unsigned, so Microsoft Defender SmartScreen may warn on first launch.
macOS
For MacBooks, iMacs, and Mac minis
Use Apple Silicon for M-series Macs and Intel for older machines. ZIP builds stay available for advanced workflows.
Linux
For Ubuntu, Fedora, and major desktop families
AppImage is the easiest universal option. Ubuntu/Debian users should choose deb, Fedora/RHEL users should choose RPM, and tar.gz stays available for manual installs.
Android
For phones and tablets
Use the APK for direct installs on your own device. The AAB is included for Play Console and managed distribution workflows.
Android binaries come from the dedicated mobile release lane.
iPhone + iPadOS
For Apple phones and tablets
Use the signed IPA when a real-device build is published. iPadOS users can also install the hosted Aura PWA from Safari today.
Apple device installs require signing and provisioning.
iPadOS PWA
For Safari Add to Home Screen
Open Aura in Safari on iPadOS, then use Share and Add to Home Screen for a standalone tablet app shell. The responsive storefront uses the same production backend as web and desktop.
ChromeOS
For Chromebooks and Chromeboxes
Install Aura from Chrome as a standalone PWA. On compatible Chromebooks, the Android APK is also available from the mobile release lane for testing.
Unix / BSD
For browser-first Unix systems
FreeBSD, OpenBSD, NetBSD, illumos, and other Unix-style systems can run the hosted Aura PWA in a modern browser. Linux users also get packaged desktop AppImage, deb, RPM, and tar.gz builds above.
HarmonyOS
For Huawei browser and web install
HarmonyOS can use the live Aura PWA through its browser. Android-compatible HarmonyOS devices may also test the APK, while a native HAP package would require a separate HarmonyOS project.
FreeRTOS / RTOS family
For embedded companion devices
RTOS devices cannot run the full Aura UI. They are supported as companion clients that call the Aura backend for device status, telemetry, inventory signals, and lightweight commerce events.
Use HTTPS/MQTT-capable firmware or a gateway bridge. Keep checkout and account screens on web, mobile, or desktop.
BOSS Linux family
BOSS, EduBOSS, Secure BOSS, and BOSS Server
BOSS Linux, EduBOSS, Secure BOSS, and BOSS Advanced Server are covered by Aura's Debian-compatible deb package and the hosted PWA. Server editions should use the web app from a managed browser session.
Maya OS
Ubuntu-based defence Linux
Maya OS is covered through Aura's Ubuntu-compatible deb package, AppImage, and hosted PWA. Deployment into controlled defence environments should follow local security policy and endpoint controls.
Garuda Linux
Arch-based desktop Linux
Garuda users should use the AppImage or tar.gz desktop artifacts, or install Aura as a browser PWA. A repo-native Arch package is not published yet.
BharOS, JioOS, and Indus
Android-family mobile and laptop surfaces
BharOS, JioOS on JioBook, and the Indus ecosystem are covered through Aura's Android APK where the OS accepts compatible Android packages, plus the hosted PWA for browser-first installs.
JioTele OS
Smart TV browser and app-store surface
JioTele OS is covered by Aura's hosted PWA/browser surface for TV-capable browsing. A native TV app would require a separate JioStore/TV packaging lane and remote-control UX pass.
watchOS
Apple Watch companion surface
Apple Watch cannot run the full Aura storefront. watchOS is covered as a companion surface for alerts, approval nudges, order status, and quick actions driven by the iPhone/iPadOS or web session.
tvOS
Apple TV discovery surface
tvOS is covered as a large-screen browsing and display surface where a browser or AirPlay workflow is available. A native Apple TV app needs a separate remote-control UX and App Store packaging lane.
Red Hat Enterprise Linux
Enterprise desktop, server, and cloud Linux
RHEL users should choose the RPM package for desktop installs, AppImage for portable use, or the hosted PWA from a managed browser on servers and cloud workstations.
VxWorks
Real-time embedded companion systems
VxWorks cannot run the full Aura UI. It is supported through the same embedded companion model as RTOS: authenticated telemetry, inventory signals, device state, and gateway-mediated commerce events.
Keep payments, account access, checkout, and admin tasks on Aura web, mobile, or desktop surfaces.
Linux / GNU-Linux family
Servers, cloud, desktop, embedded, and supercomputing
Aura covers the wider GNU-Linux family through AppImage, deb, RPM, tar.gz, and the hosted PWA. Server and cloud systems should use the browser/PWA from a managed user session.
SUSE Linux Enterprise + openSUSE
Enterprise, developer, server, and container Linux
SUSE Linux Enterprise and openSUSE users should choose Aura's RPM package or AppImage. Containers and server installs should use the hosted PWA from a managed browser.
Raspberry Pi OS
Debian-based ARM computers, education, IoT, and robotics
Raspberry Pi OS is covered by the hosted PWA and ARM64 Linux packages where the device and desktop stack support them. Lightweight Pi/IoT deployments can use the companion API model.
Sailfish OS
European mobile OS alternative
Sailfish OS is covered through the hosted Aura web/PWA surface in a compatible browser. Android app compatibility may work on configured Sailfish devices, but it is not the primary support lane.
MINIX + RISC OS
Education, microkernel research, ARM enthusiast systems
MINIX and RISC OS are covered only where a modern browser can run the hosted Aura app. Otherwise, use them as companion or research clients against backend APIs rather than full storefront hosts.
Symbian OS
Legacy Nokia-era smartphones
Symbian is treated as a legacy compatibility target. The full Aura UI requires modern browser APIs, so Symbian users should use a newer companion device for account, checkout, and marketplace flows.
No native Symbian package is produced.
Mageia
French community desktop/server Linux
Mageia users should choose Aura's RPM package, AppImage, or hosted PWA. Server deployments should keep Aura in a browser session rather than running the desktop UI as a service.
Astra Linux, ALT Linux, RED OS, and ROSA Linux
Certified desktop, server, government, education, and enterprise Linux
These Linux families are covered by Aura's Linux package set and hosted PWA. Use RPM on RPM-family deployments, deb where the system policy supports Debian packages, or AppImage for portable testing.
Aurora OS
Government and corporate mobile OS
Aurora OS is covered through the hosted mobile web/PWA lane where a compatible browser is available. Native Aurora packaging would require a separate SDK, signing, and enterprise distribution workflow.
KasperskyOS
Secure microkernel and critical infrastructure systems
KasperskyOS cannot run the full Aura storefront. It is supported as a secure companion endpoint through authenticated telemetry, inventory, device-state, and gateway-mediated event APIs.
Keep account, checkout, payment, and admin workflows on full Aura web, mobile, or desktop clients.
Elbrus Linux / Elbrus OS
Specialized Linux on Elbrus processor platforms
Elbrus systems are covered by the hosted PWA and browser route. Native desktop binaries are not emitted for Elbrus CPU targets in the current release pipeline.
Calculate Linux
Gentoo-based desktop/server Linux
Calculate Linux users should choose AppImage or tar.gz for desktop use, or install Aura as a PWA from a modern browser. No native ebuild is published yet.
KolibriOS + Phantom OS
Tiny, experimental, research, embedded, and object OS surfaces
KolibriOS and Phantom OS are not full Aura UI targets. They are covered as experimental companion clients through lightweight backend API or gateway bridge integrations.
HarmonyOS / Hongmeng OS + OpenHarmony
Phones, tablets, wearables, TVs, cars, IoT, and distributed devices
HarmonyOS users get Aura through the hosted PWA today, with Android-compatible APK testing where the device supports it. OpenHarmony and IoT targets use the companion API model.
Kylin OS, Galaxy Kylin, UOS, and deepin Linux
Domestic desktop/server Linux and consumer desktop systems
Kylin, Galaxy Kylin, UOS, and deepin are covered by Aura's Linux deb/AppImage/RPM choices plus the PWA. Use the package family approved by the target deployment.
openEuler, Anolis OS, and TencentOS Server
Server, cloud, edge, embedded, and digital infrastructure Linux
openEuler, Anolis OS, and TencentOS Server are covered by Aura's RPM/AppImage/PWA routes. Server and cloud environments should use managed browser access or gateway integration instead of desktop daemon use.
AliOS, AliOS Things, and RT-Thread
Smart cars, industrial systems, IoT, embedded, sensors, and RTOS devices
AliOS Things and RT-Thread cannot host the full Aura UI. They are covered through the embedded companion model: authenticated events, telemetry, inventory signals, and gateway-mediated actions.
Keep account, checkout, payment, and admin workflows on web, desktop, or mobile.
Same core.
Sessions, data, and features stay consistent.
Private by design.
Security posture stays visible at the edge.
Updates everywhere.
Hosted and packaged releases stay easy to find.