--- title: "Home" description: "Documentation for AlisX, the agent-native platform that brings structure to how and where you and your teams work with your AI tools. The Skill Store, the Ideate tools, the Build tools and Specialists, from the console, the command line or the agent you already have." url: "https://docs.alisx.com/" ---
# AI at the scale of an organisation. AlisX is the agent-native platform that brings structure to how and where you and your teams work with your AI tools, so work goes further, moves faster and happens safer. Think of it as a bench. Four things sit on it: the **Skill Store** for know-how your agents can apply, the **Ideate tools** for context they can trust, the **Build tools** for a secure place to build and ship in your own cloud, and **Specialists**, the right people to ask. You work from the **console** in a browser, from the **CLI** in a script or a coding agent, or from the **TUI** in a terminal.
[Get started](https://docs.alisx.com/tutorials/index.md){ .app-btn .app-state .app-target .app-btn--filled } [Install the CLI](https://docs.alisx.com/tutorials/install-the-cli.md){ .app-btn .app-state .app-target } [Open the console :symbols-open_in_new:{ .app-icon--trailing }](https://console.alisx.com){ .app-btn .app-state .app-target target="_blank" rel="noopener" aria-label="Open the console, opens in a new tab" }
## Find what you need
- :symbols-school: **Get started** Step-by-step lessons that end with something working: an account, the CLI, a first Ideate project, a first deployed service. [Tutorials →](https://docs.alisx.com/tutorials/index.md) - :symbols-checklist: **How-to guides** Recipes for a task you already have: invite a member, upload a recording, run an interview, deploy a version, read logs, script the CLI. [How-to guides →](https://docs.alisx.com/how-to/index.md) - :symbols-menu_book: **Reference** Exact and complete: every CLI command and flag, console screens, the resource model, the variables the platform gives your infrastructure. [Reference →](https://docs.alisx.com/reference/index.md) - :symbols-lightbulb: **Explanation** The ideas behind the platform: what sits on the bench, why context comes before code, why Define, Build and Deploy are separate, how accounts and billing work. [Explanation →](https://docs.alisx.com/explanation/index.md)
## The workbench Everything you need to bring structure to how and where you work with AI. Whichever door you come in by, the whole bench is yours: one account, one plan, one credit balance, and one active account that every tool reads.
- :symbols-alis_skills: **Skill Store** Knowledge and know-how. Give every AI you use the knowledge it needs and the way you and your best people work: capture a skill as you work, load it live mid-session, share it by policy and improve it from feedback. Four layers: me, my team, community and platform. [Discover and load skills →](https://docs.alisx.com/how-to/skill-store/discover-and-load-skills.md) · [Reference](https://docs.alisx.com/reference/skill-store.md) - :symbols-alis_interviews: **Alis Ideate Interviews** Context and alignment from the people who know the work: Alis talks to each of them, in their own language and in their own time, and writes a report across everyone. [Run an interview →](https://docs.alisx.com/how-to/ideate/run-an-interview.md) · [Reference](https://docs.alisx.com/reference/interviews.md) - :symbols-alis_projects: **Alis Ideate Projects** Files, interviews, decisions and outputs kept together, and served to agents at a fraction of the tokens. [Your first project →](https://docs.alisx.com/tutorials/first-ideate-project.md) · [Reference](https://docs.alisx.com/reference/projects/index.md) - :symbols-alis_artifacts: **Alis Ideate Artifacts** Context turned into documents, specs and prototypes others can review and act on. [Create and review artifacts →](https://docs.alisx.com/how-to/ideate/generate-and-review-outputs.md) · [Reference](https://docs.alisx.com/reference/artifacts.md) - :symbols-alis_environments: **Alis Build Environments** A secure place for people and agents to build together, in your own Google Cloud under your own IAM. [Set up a build environment →](https://docs.alisx.com/how-to/alis-build/set-up-a-cloud-environment.md) · [Reference](https://docs.alisx.com/reference/environments/index.md) - :symbols-alis_workstations: **Alis Build Workstations** Machines of your own that keep your agent working after the laptop shuts. [Use workstations →](https://docs.alisx.com/how-to/alis-build/use-workstations.md) · [Reference](https://docs.alisx.com/reference/workstations.md) - :symbols-deployed_code: **Alis Build DBD** Every change shipped the same way: Define, Build, Deploy, with a person before production. [Ship your first service →](https://docs.alisx.com/tutorials/first-build-service.md) · [Define, Build, Deploy](https://docs.alisx.com/explanation/define-build-deploy.md) - :symbols-support_agent: **AlisX Specialists** Experts. When you or your agent need another person, AlisX routes you to the right Specialist: a working Builder who reads your ticket or shared session first, including tickets written by agents. [Get support →](https://docs.alisx.com/how-to/help/get-support.md) · [Reference](https://docs.alisx.com/reference/specialists.md)
## From the first idea to the review after it ships A project on AlisX runs through nine stages, and each stage names the tool that does the work: **Capture**, **Describe**, **Decide**, **Define**, **Design**, **Build**, **Verify**, **Launch** and **Review**. The Ideate tools carry the first four and come back at every check-in, the Skill Store and a Specialist shape the design, and the Build tools make, verify and launch the thing. Read [how a project runs on AlisX](https://docs.alisx.com/explanation/platform-overview.md#how-a-project-runs-on-alisx). ## Three ways to work
- :symbols-dashboard: **The console** [console.alisx.com](https://console.alisx.com) is where you sign up, manage your account, members and billing, and use the Ideate tools, the Build dashboards, the Skill store and Specialist conversations in a browser. [How-to guides →](https://docs.alisx.com/how-to/index.md) - :symbols-terminal: **The CLI** `alis` is made for scripts and coding agents: deterministic, one JSON object on stdout, self-documenting with `alis docs`. [CLI reference →](https://docs.alisx.com/reference/cli/index.md) - :symbols-code_blocks: **The TUI** Run `alis` with no arguments for a full-screen terminal interface for people: products, services, builds, deployments and logs. [Tour the TUI →](https://docs.alisx.com/tutorials/tour-the-tui.md) - :symbols-smart_toy: **Coding agents** Bring the agent you already have. Point Claude Code, Codex, Gemini CLI, Cursor or another agent at the CLI, load skills live, and let it define, build and deploy with a human on the production gate. These docs are readable by agents too: every page is also markdown, indexed at [`/llms.txt`](https://docs.alisx.com/reference/docs-for-agents.md). [Work with a coding agent →](https://docs.alisx.com/tutorials/work-with-a-coding-agent.md)