Status

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.

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.

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.

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.

The GitHub App that reviews pull requests. Unlike the desktop app this is a service — it receives a webhook from GitHub, queues the job, and posts the review back. It runs on the Atlarix Core proxy above, so anything affecting that affects reviews.

• A brief outage delays a review, it does not lose one. Every pull request becomes a durable job before any work starts, and a job that fails is retried. Reviews queued while the service is down are picked up when it returns rather than being dropped on the floor.
• A review that cannot complete says so on the pull request. If it still fails after its retries — a model provider being down is the usual reason — it posts a comment telling you the pull request has not been reviewed. Silence would be worse than a failure, because silence is indistinguishable from a clean review.
• A review that never starts costs nothing. A review that fails partway has spent whatever it used before it stopped — usage is metered as the work happens, so we would rather tell you that than claim a refund we do not make. What each product has spent is itemised on your account page.
• Reviewer never executes, builds, installs or tests the code it reads, so an incident here cannot run anything from a pull request.

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.