Astvyr
PRODUCT // PRE-RELEASE

What the product is planned to include.

Astvyr has not been released. Every area below is planned scope, and each one links to the page where it is described in full. The planned release date is 7 July 2027; early access is not provided.

RELEASE STATUS

Planned scope, not a shipped product.

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 SCOPE

Fourteen planned areas, one delivery loop.

As planned, desktop, web, CLI and mobile share one Mission, policy and evidence model — so a change started in one surface is verified and released by the same rules everywhere.

Desktop IDE

Local workspace, editing, missions and review on Windows, macOS and Linux.

Web console

Missions, dashboards, reviews, administration and incident handling.

CLI

Headless missions, CI integration and remote runner control.

Mobile companion

Approvals, incident alerts and release control away from the desk.

Mission OS

Intent, acceptance contract, planning and multi-agent execution with human checkpoints.

Verification and evidence

Independent verification, sealed evidence bundles and release confidence.

Production Twin

Production-like environments, traffic replay and migration rehearsal.

Release control

Policy-controlled rollout, canary stages, metric gates and rollback.

Observability and incidents

Telemetry, Production Lens, the incident lifecycle and bounded automation.

DevOps Studio

Infrastructure understanding, the build and artifact chain, environments and database DevOps.

Context engine

Code and system graph, the memory model and the Release Outcome Graph.

Model gateway

Model routing and evaluation across cloud, private and local providers.

Enterprise and governance

Identity, policy, audit, residency and every deployment profile from shared to air-gapped.

Marketplace and SDK

Agents, skills, connectors and templates with publisher trust and a package lifecycle.

LANGUAGES

Four planned depths of localization.

Localization is not a translated interface. Each tier covers a different part of the product, and a language will only be listed once its tier is complete.

L1 Interface

UI strings, dates and numbers, keyboard and input, docs basics.

L2 Product experience

AI responses, templates, onboarding, billing, support content.

L3 Commercial

Website, campaigns, sales, security and legal materials, local pricing and payment.

L4 Operations

Native support, community, partners, local incidents and regulatory processes.

PLANNED LANGUAGES

  • LaunchEnglish
  • Expansion 1Spanish, Portuguese, German, French, Japanese, Korean
  • Expansion 2Simplified Chinese, Hindi, Turkish, Arabic
  • CommunityRussian and others
ECONOMICS

The numbers the product is measured on.

Cost per verified outcome is the unit that matters, and it has to fall as usage grows.

65-80%Mature blended gross margin
< 12 monthsCAC payback, product-led and team
< 18-24 monthsCAC payback, enterprise
> 120%Net revenue retention
Required before GA for every featureUnit cost model
ChangelogBenchmarks and SLORead the manual
HONESTY

Transparent limitations, reproducible benchmarks.

A target is published so it can be checked. A benchmark includes our failures, not only our best runs.