Frequently asked questions

Download the app for your platform from the Download page, run the installer or unpack the archive, and open Aurora. The site is the main place to grab current builds and release notes.

You use an account on this site to sign in, and eligible users can download builds from Download or your dashboard. How license or subscription ties to in-app unlock is still being defined; for now, access is centered on having a site account and download permission. Check Status for the latest on gating and releases.

Typical flow: install from the site → sign in or use your access method (see above) → add and configure add-ons or connect providers → attach media sources (debrid, local files, or APIs) → set metadata and scrobble keys if you use them → browse and play. Details vary by how you want to run Aurora (with Stremio-style add-ons, API-only mode, or both).

Add-ons supply streams, catalogs, and integrations using the same protocol-style model many users already know. You add them by URL, manage them in the app, and tune catalogs: order, visibility, names, and layout on the home screen.

No. You can run without traditional add-ons by wiring metadata providers, debrid services, custom list sources, and local or remote libraries (where supported). Add-ons are one path, not the only one.

Common options include a debrid account (for cached or host-backed streams, depending on provider), local files on your machine, and (in the future) remote libraries such as WebDAV or libraries exposed by media servers. Server-style integrations (for example Jellyfin or Plex) are not in the app yet; treat that as planned until announced on Status.

Only if that is how you want to source streams. Aurora does not replace a debrid subscription; you bring your own key for providers you choose. You can still use local files and other integrations without debrid.

Yes. You can configure API keys for metadata services (for example TMDB, TVDB, MDBList, PMDB) and for debrid providers (for example TorBox, Real-Debrid), and connect custom list providers so your catalogs reflect both built-in metadata and your own lists.

It is a configurable source that feeds catalogs or rows alongside metadata-driven ones, so you can surface curated or third-party lists in addition to default metadata catalogs.

You choose a scrobble provider in settings, add the API credentials that provider requires, and Aurora reports watch progress and activity according to that integration. Exact providers depend on what the app supports in your build.

You can create an account, download releases you are allowed to access, manage email and security settings, and (where enabled) create API keys for app features such as sync (for example under Settings on the site). See Settings when signed in.