Skip to main content
Alkera is accessible via an IDE extension and a command-line tool. You install and update them separately.
The extension and the CLI follow the same version numbers and are released together.

​
Self-hosted deployment

Alkera can run on your own infrastructure if your data cannot leave it.
Deploy Alkera into your VPC, or onto hardware you own.Air-gapped installs are supported. Once deployed, the only traffic that leaves your network is the call to your model provider, and you can point that at a provider inside your own network.
Everything below covers the hosted Alkera platform, which is how most teams run Alkera. On a self-hosted deployment, your administrator gives you the install steps for your environment instead.

​
IDE extension

​
VS Code

Open in VS Code to install it directly, view it in the Visual Studio Marketplace, or search for “Alkera AI” within the Marketplace in VS Code.

​
Cursor and other IDEs

Cursor, Windsurf, and other VSIX-compatible IDEs install extensions from the Open VSX Registry. Get Alkera from the Open VSX Registry, or search for “Alkera AI” in your editor’s extensions panel.

​
CLI

Run the command for your operating system. Alkera runs natively on x64 and arm64. The one exception is Windows on arm64, where Alkera installs as normal and runs under emulation. Native support is coming soon.
Restart your terminal and confirm the install:

​
Updating

Extensions update through their marketplace. VS Code and most forks update installed extensions automatically. You can also update Alkera by hand from the extensions panel. Update the CLI with:

​
Uninstalling

Remove the extension from your editor’s extensions panel. Remove the CLI with:

​
Project files

Alkera creates a .alkera directory at the root of each data project you open. It holds your chat history, your connection settings, and credentials.
Add .alkera/ to your .gitignore. Never commit it.

​
Next steps

Quickstart

Open Alkera, sign in, and start a chat.