Docs navigation

Docs / YAI / Start

Install and activate

English2 min read
On this page1. Create your account2. Get the application3. Connect the installation4. Choose a model5. Open a Case in Studio

The YAI setup path takes you from an account to a local Case. Platform packages appear on the download page as they are published; the account can be created before an installer is available.

1. Create your account

Create a YAI account with your name, email and password. Confirm your email before accessing your account or approving a machine. Use password recovery if you cannot sign in.

Your 14-day trial starts only when you explicitly start it in your account. Creating an account alone does not consume the trial.

2. Get the application

On Downloads, choose YAI, your operating system and your architecture. An active trial or paid plan is required for YAI downloads. Check the release requirements and checksum. The distribution includes Studio, Core and YVEX. Model weights are not bundled.

If you only need the free command-line runtime, choose YVEX instead. It does not need a YAI account or subscription.

3. Connect the installation

Start sign-in from Studio. It opens the browser to link the installation to your YAI account. If you are already signed in on the website, you only confirm the pending installation. The CLI can use a short code for the same flow. Review the machine name and platform before approving it on Activate a device. Approve only a request you initiated on your own machine.

The website issues a signed entitlement that the application receives automatically: there is no license key to copy. All windows using the same local installation/profile share this activation. The website device list manages connected installations; it does not detect the computer running the browser. The desktop Core verifies that entitlement locally. This desktop integration is specified for the upcoming packages; the website cannot activate an older build that does not implement it.

4. Choose a model

The model catalog lists exact prepared GGUF files, their checksums and the configuration used for their recorded tests. Those files are optional quickstart choices.

Different hardware may need a different representation. File size alone does not tell you the peak memory requirement. Follow the model lifecycle guide for acquisition, preparation, loading and verification.

5. Open a Case in Studio

Use the Home screen to create a Case or return to existing work. Keep related sources, conversations and results in the same Case so the context has a stable home.

Understand the Case · How memory works · Manage your account

Source: content/docs/get-started.md
Documentation figure