Getting Started

Head to aethernaut.ai/signup and choose the cloud tier. You'll pick an org name, a region (US or EU), and an initial seat count. The person who creates the org is the Manager — the single billing and org-state owner. The role is transferable later, but only ever held by one person at a time.

Cloud pricing is a $250 one-time setup fee plus $25 per seat per month. You're billed for the current seat count; add or remove seats from the portal at any time and the next invoice prorates. Self-hosted and BYOC tiers are flat-fee — contact sales if that fits you better.

After payment, verify the work email on the Manager account. You'll land in the portal with an empty org, ready for the desktop client.

Velocity is a native desktop app — there is no browser version. Download links live in the portal under Downloads, and on the public site at aethernaut.ai/download.

• macOS 12+ — universal build for Apple Silicon (arm64) and Intel (x64), signed and notarized.
• Windows 10/11 — x64 installer, Authenticode signed.
• Roughly 500 MB on disk. Code OSS and all extensions are bundled — no Marketplace pulls at runtime.

Launch Velocity. The sign-in screen takes the same email and password you set up in the portal. If your org has SSO enforced, you'll be bounced to your IdP instead — see the SSO Setup page.

On first launch the client provisions a local encrypted RAM cache and a device key pair. Nothing sensitive is written to disk. If you sign out, the in-RAM cache is zeroed and the device key is revoked server-side.

You'll land on the project picker. It's empty — let's fix that.

Click New Project. You have three options:

1. Clone from GitHub. Authorize the Velocity GitHub app on the repos you want to pull from. We clone into the encrypted cloud working copy — never to your local disk.
2. Upload a folder. Drag a directory onto the picker. We stream the contents into encrypted cloud storage and zero the source bytes in memory once committed.
3. Start empty. A blank project with a single

   README.md

   and a default

   .velocityignore

   . Useful for greenfield work.

Set the project name, pick the Reviewers who can approve builds, and confirm. Projects live forever in your org until archived.

Open Org Settings → People. Click Invite, paste one or more email addresses, and pick a role: Developer, Reviewer, or Admin. Developers are the default — they write code in sessions and submit builds. Reviewers approve those builds. Admins manage people, projects, and policy short of billing.

Invitees get an email with a one-time link. They install the desktop client, set a password (or sign in via SSO), and appear in your People list. Each accepted invite consumes one seat.

Roles are mutable — promote a Developer to Reviewer the moment they're ready. Only the Manager can transfer the Manager role itself, and only to an existing Admin.

Open the project, click New Session, and pick the version you want to pull from. A session is a live working copy backed by Loro CRDTs — every keystroke from every participant is merged in real time. Up to a thousand people can join a single session.

Invite a teammate by copying the session link from the top bar. They click it inside their desktop client and join instantly. You'll see their cursor, their selection, and (if they use the CLI tab) their AI authorship highlighted in hot pink.

When you're ready to ship, hit Submit for Review from the Build tab. The diff goes to a Reviewer, who approves or sends it back with comments. Approved builds flow to an Admin for the final merge. That's the whole loop — Developer → Reviewer → Admin, no exceptions.