Astvyr
DOWNLOAD // NOT RELEASED

No public build yet. Here is what the first launch will do.

Astvyr has not been released and no builds are published. The planned release date is 7 July 2027, and early access is not provided. When it ships, Astvyr will run read-only analysis first: a repository is indexed on your machine, and cloud execution will only happen for a Mission you explicitly start.

RELEASE STATUS

No public build yet.

PRE-RELEASE // IN DEVELOPMENT · PRIVATE TESTING

Astvyr has not been released. The product is in development and under private testing; the planned release date is 7 July 2027. Early access is not provided and no builds are published. Prices are not yet determined. Nothing on this website is an offer, a promise of availability or a commitment to any date.

  • PLANNED RELEASE: 7 JULY 2027
  • EARLY ACCESS: NOT PROVIDED
  • BUILDS PUBLISHED: NONE
BUILDS

Six planned channels.

None of these builds exists yet. They are the channels planned for the release on 7 July 2027.

macOS

UNIVERSAL

Apple Silicon and Intel, signed and notarised, with staged updates.

Not available yet

Windows

X64 · ARM64

x64 and ARM64, signed installer, per-user install without admin rights.

Not available yet

Linux

X64 · ARM64

x64 and ARM64, AppImage and deb, with a headless CLI package.

Not available yet

Astvyr CLI

CROSS-PLATFORM BINARY

Headless Missions in CI, runner enrolment and evidence export.

Not available yet

Web console

BROWSER

Missions, reviews, releases, incidents, policy and usage. No install.

Not available yet

Mobile companion

IOS · ANDROID

Approvals, incident alerts, release control and emergency stop.

Not available yet

PLANNED: SIGNED BUILDS, STAGED UPDATES AND ROLLBACK ON EVERY CHANNEL.

FIRST RUN

What will happen on the first launch.

Planned behaviour: no forced repository upload, no silent model calls, no surprise compute.

  1. 01Choose a privacy and model profile before anything is indexed.
  2. 02Run read-only analysis on a repository — no writes, no uploads.
  3. 03Start a low-risk Mission from a template and review its acceptance contract.
  4. 04Approve the plan, watch the run, then read the evidence bundle.
  5. 05Release through the gate, or keep it local and export the evidence.
REQUIREMENTS

What it will need, and the planned targets.

8 cores, 16 GB memory, SSDREFERENCE HARDWARE
< 2 s p50 on reference hardwareWARM START
Available when the cloud is notLOCAL EDITING
Keyboard-first, targeting WCAG 2.2 AAACCESSIBILITY
CHANNELS

Planned release channels.

When the product ships: signed updates with rollback on every channel, and Enterprise LTS with an admin-controlled upgrade window.

  • StableStaged rollout, minimum soak, rollback, signed provenance.
  • Early accessNot offered before release. After release: opt-in, a separate telemetry and evaluation cohort, a clear downgrade path.
  • InsiderDaily builds with no production guarantee.
  • Enterprise LTSLong support, security backports, an admin-controlled upgrade window.
  • Air-gappedOffline signed bundles, checksums, chain verification and a rollback package.
Release plan — 7 July 2027Read the manualSecurity model
LOCAL FIRST

Planned: your code stays on your machine until you start a Mission.

At release: local analysis, local checkpoints and a working editing loop when the cloud is unavailable.