Three storefronts and one launcher
Astellia 2 has no Steam page and no Epic listing. On PC it installs through the HIVE Crossplay Launcher, and on Android through Google Play or ONE store. That is the entire published install matrix, and getting the order right avoids most of the failures people hit on day one.
The install table
| Platform | Where | Notes |
|---|---|---|
| Windows PC | HIVE Crossplay Launcher | Windows 10 or later |
| Android | Google Play | Also listed on ONE store |
| iOS | App Store | Listed, no date |
| Steam / Epic | — | No listing |
PC: the order of operations
- Open the official site at astellia2.com and use its download button. The button opens a
hivelauncher:URI rather than a direct file, which is why it asks for permission to open an external app. - If the URI does nothing, download the installer directly. The official installer address is on the same page; it is an
.exehosted by the publisher's file service. - Run the installer as administrator if it fails silently. Launcher installers write to protected directories and a standard user account can block that without an error.
- Let the launcher patch before you press Play. The installer ships a stub; the client is pulled afterwards. Pressing Play during the patch is the most common cause of a "game won't start" report.
- Check Windows version. Windows 10 or later is the only published requirement. Anything older is untested by the developer.
The launcher URI, explained
The download button on the official site points at a hivelauncher: link with an app identifier embedded. That is a protocol handler, not a URL — it tells an already-installed launcher to start installing a specific app.
If you have never installed HIVE, the handler will not exist and the browser will show nothing or an error. That is expected. Use the direct installer in that case, then use the button for future updates.
Android
Google Play is the primary route, and the listing is live with in-app purchases disclosed. ONE store carries it as well.
Two practical notes. First, the Play listing shows a very small install count, which is normal for a game a day old — it is not a red flag. Second, the listing discloses random items among the purchases, which matters if the device is shared.
iOS
The App Store listing exists and carries no release date. Do not install a third-party APK-style workaround; there is no legitimate iOS sideload path for this game.
What about emulators?
No official statement. The game ships a native Windows client, so emulating Android on a PC is strictly worse than installing the PC build: same account, better performance, no virtualisation overhead.
If you are on a machine that cannot run the PC client, an emulator is a workaround, not a supported configuration.
Troubleshooting, in the order to try
| Symptom | First thing to try |
|---|---|
| Download button does nothing | Use the direct installer; the URI handler is missing |
| Installer exits immediately | Run as administrator |
| Launcher opens, Play greyed out | Let the patch finish |
| Client crashes at logo | Update GPU drivers, then repair install |
| Store says "not available in your country" | Try the other store; region lists are unpublished |
| Download stalls at a percentage | Restart the launcher; resume support is unclear |
Disk space
Disk space is not published. The store listing gives an install size only in the vague terms mobile listings use, and the PC client expands after patching. If you are tight on space, budget generously — modern MMO clients routinely triple their installer size once patched.
That is a general MMO observation, not an Astellia 2 measurement, and this site will not invent a number for it.
Accounts and crossplay
One account covers phone and PC. The PC launcher uses a HIVE account; the Android build uses the store account you install with. Linking them is what makes crossplay work, and it is the step people skip when their character "disappears" on the other device.
If your character is missing after switching devices, log out and back in rather than starting a new game — the character is attached to the account, not the device.
After the install
The first hour is the class decision, which is the only irreversible choice in the launch build. Read the class picker before you commit, and keep the classes overview open while you decide.
If the client will not start at all, check system requirements for the one published line, then the platforms page for store status.
Verifying you have the right client
There are no official mirrors, so the only trustworthy sources are the ones the publisher controls: the install button on the official site, the Google Play listing, the ONE store listing and the App Store listing.
Three quick checks after installing:
- The launcher should name the game, not a generic HIVE shell. If it opens to a store page with no Astellia 2 entry, the app identifier did not register.
- The patch should show a size. A patcher stuck at zero without a size is a network block, not a slow download.
- The login screen should offer account creation, not just an existing-account login. If it does not, you are in the wrong regional client.
Install paths and platform availability checked against the official install page and store listings on 6 November 2026.
