Status

    Atlarix is a desktop application — it runs on your machine, not on our servers, so your workspace keeps working even when we do not. Below is what it reaches out to and how each part is updated. Model providers are not ours to report on — see the last section for where to check them.

    Desktop application

    The app runs locally and works offline. Once installed, it does not depend on Atlarix infrastructure to function — editing, running commands, git and local models all keep working regardless of anything on this page.

    Authentication

    Sign-in uses Supabase Auth (GitHub OAuth, Google OAuth, Discord). Authentication is only needed at sign-in — the app continues to work with a cached session if Supabase is temporarily unreachable.

    Releases and updates

    Atlarix is distributed two ways, and they update through different channels.

    • Direct download — installers are published to GitHub Releases for macOS (Apple Silicon and Intel), Windows and Linux. The app checks on launch and updates itself in the background.
    • Microsoft Store — the Store listing is signed by Microsoft, so it installs with no SmartScreen warning. Store installs are updated by the Store, not by Atlarix — the app deliberately runs no updater of its own there, because a Store package lives in a read-only location. A new version reaches you once Microsoft finishes certification, which usually takes a little longer than the direct download.
    • A few installs cannot be updated silently by design — Linux .deb / .rpm (your package manager owns them) and macOS copies running from outside /Applications. Those tell you a new version exists and link you to it rather than replacing themselves.

    Atlarix Core proxy

    Managed Atlarix Core models route through our proxy, which meters usage against your prepaid balance. It is the one piece of Atlarix infrastructure a chat depends on — if it is unreachable, your own API keys and local models keep working, and nothing is debited.

    AI model providers

    We do not run the models, so we cannot report on them here. Atlarix works with 145+ providers using your own keys — an outage at any of them is theirs, not ours, and their status page is the authoritative source. The common ones:

    Using a provider that is not listed? Search for its status page directly — and if a model is failing only inside Atlarix while the provider reports healthy, that is worth reporting to us below. Local models run entirely on your machine and depend on nothing here.