Choose where AGVM runs.

Use Cloud AGVM from Detwin, or run the open AGVM Core locally. Pro modules unlock only through the account plan and a signed local lease.

Free starts with AGVM Core. You can use Cloud AGVM after sign-in, but paid modules require Pro.

Use Cloud AGVMOpen local AGVM if running
Recommended first test

Use Cloud AGVM

Open the hosted AGVM workspace in this browser. After sign-in, Detwin creates or selects a cloud workspace and keeps cloud calls scoped to your account.

Open Cloud AGVM
Free core

Run AGVM locally

Local AGVM Core is the open-source runtime for your machine. The signed release flow is still being prepared, so this page opens an existing local cockpit only when it is already running.

Open local cockpit
Release and source

The clean detwin-agvm-core release repository is not published yet. Until that split is complete, Cloud AGVM is the supported hosted path and local AGVM must already be installed on this machine.

Pro modules

Activate Clone, Grow and Maintain

After Pro checkout, Detwin issues signed local claims. Local AGVM can then install or update paid module sidecars and report receipts back to the account.

Review Pro checkout
Open core

AGVM Core will ship from the public GPLv3 repo.

The public package will be detwin-agvm-core: local memory runtime, MCP bridge, core UI, health, bench and retrieve. It is not published until the clean-history split and license review are complete.

Private modules

Paid modules stay account-controlled.

Clone, Grow, Maintain and Auto Memory are activated from the Detwin account. Local AGVM receives signed lease claims and shows whether each module is locked, licensed, not installed, running or ready for update.

Local activation journeyLocal activation wizard

From account to running local modules.

Use this path when the user wants AGVM on their machine. The free core runs locally; Pro modules activate only after account sign-in, plan validation, signed local lease and local runtime receipts.

Current state
account needed
Core license
GPLv3 public core
Paid modules
Account plan plus signed local lease plus receipt
Sign in to connect local AGVMDownload AGVM Core
1
Download AGVM Core

Install the public GPLv3 core package from the Detwin release page or public repository when the clean release is published. The core contains memory, MCP, retrieve, health and bench.

2
Start local AGVM

Run the local cockpit on this machine, then open it from the platform when the service is available.

3
Connect this Detwin account

Sign in from local AGVM so the same account controls cloud access, billing, credits, module entitlement and local trust.

4
Sync signed local lease

Local AGVM receives account-scoped claims. Browser state alone never unlocks paid modules.

5
Install or update Pro modules

Clone, Grow and Maintain move from licensed to installed only through the local module manager and signed install receipts.

6
Receipts return to Detwin

The account page shows module state, running version, usage credits and cloud/local sync receipts after the local runtime reports them.

Open-source boundary

The local core repository should contain AGVM Core, local MCP setup and the account connector, but not private module implementation source.

Private module boundary

Paid modules should be distributed as authenticated runtime images and activated only after Detwin validates the plan, lease and install receipt.