# Mojo Up documentation > Documentation for AI Workbench (the desktop app), its headless nodes and the mobile app, Mojo Up AI Cloud (Free and Teams, hosted in Australia) and self-hosted AIOE (Enterprise). Every page is also available as Markdown at /llms.mdx//content.md, and all of them together at /llms-full.txt. - Get started - [Get started](/get-started): From nothing to a working AI Workbench, signed in, with your team and a node, in five short tutorials. - **Tutorials** - [Install AI Workbench](/get-started/install-the-workbench): Install the desktop app, set up your first project and team, and sign in to Mojo Up AI Cloud or your organisation. - [Sign in to Mojo Up AI Cloud](/get-started/sign-in-to-cloud): Create your Mojo Up account, then connect your workbench to it. - [Pair your phone](/get-started/pair-your-phone): Sign the mobile app in to Mojo Up AI Cloud or your organisation, find your workbench, and answer your first approval from your phone. - [Create a team and invite people](/get-started/create-a-team): Make a team on Mojo Up AI Cloud, invite your colleagues by email and give each of them a role. - [Add a node](/get-started/add-a-node): Install mojoup-node on a spare machine, join it to Mojo Up AI Cloud or your organisation, approve it, and run it as a service. - [Download AI Workbench](/download): Get the desktop app for Windows, macOS or Linux. Free to use on your own; sign in to Mojo Up AI Cloud for a team, or to your organisation's own platform. - Mojo Up AI Cloud - [Mojo Up AI Cloud](/cloud): The platform for AI Workbench, run for you by Mojo Up in Australia, for people on their own (Free) and teams (Teams). - **How-to guides** - [Sign-in methods](/cloud/sign-in-methods): Sign in to Mojo Up AI Cloud with Google, Microsoft, GitHub, Facebook or an emailed code, and add or remove the ways you sign in. - [Teams and organisations](/cloud/teams): Switch between your personal space and your teams, create and rename a team, and leave one. - [Connect a workbench](/cloud/connect-a-workbench): Approve an AI Workbench into your personal space or a team on Mojo Up AI Cloud, and take its access away again. - [Control a workbench from the browser](/cloud/remote-control): Watch a workbench's agents, answer their requests and send them prompts from the Mojo Up AI Cloud console. - [Nodes on Mojo Up AI Cloud](/cloud/nodes): Join a headless node to your personal space or a team on Mojo Up AI Cloud. - [Keep it on your own network](/cloud/your-own-network): Run your team's hub on one of your own machines, reached over your own network, instead of through Mojo Up AI Cloud. - [Delete your Mojo Up AI Cloud account](/cloud/account-deletion): How to delete your Mojo Up AI Cloud account yourself or by asking us, and what is deleted with it. - **Reference** - [Plans](/cloud/plans): Free, Teams and Enterprise, what each includes, and what Teams costs. - [Cloud and self-hosted compared](/cloud/cloud-and-self-hosted): What Mojo Up AI Cloud offers, what only self-hosted AIOE offers, and how to choose. - [Where your data lives](/cloud/data-residency): Where Mojo Up AI Cloud runs, what it keeps about you and your workbenches, and which other services are involved. - **Explanation** - [How remote control works](/cloud/how-remote-control-works): How a browser reaches a workbench through Mojo Up's relay, without opening a port, and what keeps it safe. - [How sign-in works](/cloud/how-sign-in-works): Why Mojo Up AI Cloud issues its own tokens, how sessions and organisations fit together, and how accounts are kept from being taken over. - AI Workbench - [AI Workbench](/workbench): The desktop app for running teams of AI coding agents on your own repositories, on Windows, macOS and Linux. - **How-to guides** - [Sign in and spaces](/workbench/sign-in-and-spaces): Sign AI Workbench in to Mojo Up AI Cloud or your organisation, and keep each account apart in its own space. - [Projects and repositories](/workbench/projects): Group repositories into a project, choose the machine each one runs on, and find a repository again when it moves. - [Memory](/workbench/memory): How agents remember your code and decisions, where that memory is kept, and how to explore it. - [Your subscriptions](/workbench/your-subscriptions): Use your own Claude, ChatGPT, GitHub Copilot and Google plans with AI Workbench, on your computer and on shared nodes. - [Skills and the catalogue](/workbench/skills-and-catalogue): The skills agents load, the customisations you can add, and the teams, roles and templates your organisation or team shares. - [Policies](/workbench/policies): What a repository's, your team's or your organisation's policy decides, how it caps your settings, and where you see it. - [Run a team hub on your own network](/workbench/team-hub): Make one workbench or node your team's hub over Tailscale or a VPN, invite people and devices, and share projects without going through Mojo Up. - [Back up and restore](/workbench/backup-and-restore): Back up your settings, projects and each repository's chat history and runs, and restore them on a new computer. - **Reference** - [Settings](/workbench/reference/settings): Every AI Workbench setting, its default, and where you can set it. - [Keyboard shortcuts](/workbench/reference/keyboard-shortcuts): Every keyboard shortcut in AI Workbench's menus, the composer and the editor. - [System requirements](/workbench/reference/system-requirements): The operating systems, packages and tools AI Workbench and its nodes need. - **Explanation** - [Runtimes and agents](/workbench/runtimes-and-agents): How AI Workbench runs the agent tools you already use, where their models come from, and how a team of agents works together. - [Sandboxing](/workbench/sandboxing): How AI Workbench keeps agents apart from each other and from your machine, and when an agent runs in a sandbox. - Nodes - [Nodes](/nodes): mojoup-node is AI Workbench without a screen, for a Linux VM, a GPU box or a build machine that runs agent teams for you or your team. - **How-to guides** - [Install a node](/nodes/install): Install mojoup-node on Linux, macOS or Windows with one command, and what the machine needs first. - [Join a node](/nodes/join): Connect a node to Mojo Up AI Cloud, your organisation or your team's own hub, and get it approved. - [Run a node as a service](/nodes/run-as-a-service): Start a node with the machine, keep it running after a crash, and control it with start, stop and status. - [Work with a running node](/nodes/work-with-a-node): Watch a node, answer its agents' approvals, add repositories, talk to its agents and keep it healthy from its terminal. - [Sandboxed nodes](/nodes/sandboxed-nodes): Run each agent session on a Linux node in its own sandbox, with your network rules enforced and API keys out of the agent's reach. - **Reference** - [mojoup-node command line](/nodes/reference/cli): Every mojoup-node command, its options and its exit codes. - [Configuration, files and ports](/nodes/reference/configuration-and-ports): Where a node keeps its settings and state, how its settings are layered, and the network ports it uses. - Mobile app - [Mobile app](/mobile): Answer your agents' approvals, watch your workbenches and enrol new ones from your phone. - [Sign in and enrol a workbench](/mobile/pairing): Sign the mobile app in to Mojo Up AI Cloud or your organisation, switch organisation, accept an invitation, and approve a workbench's sign-in code. - [Approvals and the inbox](/mobile/approvals): Answer agents' tool permissions, decisions and other requests from your phone. - [Your workbenches](/mobile/workbenches): See each AI Workbench you can reach, its agents and events, and send an agent a message from your phone. - [Notifications](/mobile/notifications): Get a push notification when something needs you, and what your lock screen shows. - [Troubleshooting](/troubleshooting/mobile) - Administration - [Administration](/administration): Run your organisation in the console: people, workbenches, policy, the catalogue, tools, secrets, projects, memory and the audit trail. - **How-to guides** - [People and roles](/administration/people-and-roles): How people join your organisation, the roles they can hold, and what each role may do. - [Enrol workbenches](/administration/enrol-workbenches): Approve the code an AI Workbench shows when it connects, see it in the fleet, and revoke it later. - [Policy](/administration/policy): Decide what every workbench and node may do, publish it for the organisation or chosen projects, and lock their settings. - [Catalogue](/administration/catalogue): Publish teams, roles, skills, prompts and document templates that every workbench in your organisation pulls in. - [Tools](/administration/tools): Decide which tool servers your agents may use and what each tool may do, from seeing what runs to enforcing it. - [Secrets](/administration/secrets): Keep the API keys and tokens agents' tools need, by name, and release them only to signed-in machines. - [Projects](/administration/projects): Create projects, add members, share personal projects with the organisation, and find your way around a project's tabs. - [Memory](/administration/memory): The organisation's shared knowledge and each project's memory, and how labels decide who may read what. - [Source control](/administration/source-control): Connect GitHub and Azure DevOps so people, and the agents working for them, act with their own accounts. - [Audit](/administration/audit): Search the record of what people, agents and machines did, check that nobody has changed it, and export it. - Self-hosted AIOE - [Self-hosted AIOE](/self-hosted): Run the AI Enterprise Operating Environment in your own tenancy, and choose how to install it. - **Tutorials** - [Evaluate with Docker Compose](/self-hosted/evaluate-with-docker-compose): Run AIOE on one machine, sign in with Entra ID, and enrol your first workbench. - **How-to guides** - [Install with Helm](/self-hosted/install-with-helm): Deploy the AIOE API and console to any Kubernetes cluster, with your own PostgreSQL and Redis. - [Install on Azure](/self-hosted/install-on-azure): Deploy AIOE to Azure Container Apps with the Bicep template, with PostgreSQL, Redis, a registry and logs. - [Connect your identity provider](/self-hosted/connect-your-identity-provider): Register AIOE in Microsoft Entra ID, give people roles, and set the values the API reads at start. - [Publish the discovery record](/self-hosted/dns-discovery): Add the aioe-discover DNS record so a workbench finds your organisation from a person's work email. - [Overlay and relays](/self-hosted/overlay-and-relays): How remote control reaches a workbench through the outbound relay, and how to add the WireGuard overlay. - [Redis for more than one replica](/self-hosted/redis-for-replicas): Add Redis so several API replicas share live workbench connections, and what else replicas need. - [Observability](/self-hosted/observability): Send AIOE's traces and metrics to your OpenTelemetry collector, and read its logs. - [Upgrades and backups](/self-hosted/upgrades-and-backups): Move AIOE to a new release, and back up what you cannot rebuild. - [Platform keys and rotation](/self-hosted/rotate-secrets): The keys and secrets the AIOE API holds, how to make each one, and what happens when you change it. - **Reference** - [Environment variables](/self-hosted/reference/environment-variables): Every environment variable the AIOE API reads, with its default and what it does. - [Helm values](/self-hosted/reference/helm-values): Every value of the aioe Helm chart, with its default and what it sets. - [Ports and endpoints](/self-hosted/reference/ports-and-endpoints): The ports AIOE's services listen on, the addresses clients call, and the network paths a firewall must allow. - **Explanation** - [Architecture](/self-hosted/architecture): The pieces of self-hosted AIOE, how a workbench finds and talks to it, and the principles behind the design. - [Tenancy and tokens](/self-hosted/tenancy-and-tokens): How AIOE keeps every organisation's data apart, and how people, workbenches and the platform prove who they are. - API reference - [API reference](/api-reference): The public HTTP API of Mojo Up AI Cloud and self-hosted AIOE, generated from the platform's own schemas. - [Authentication](/api-reference/authentication): The three kinds of access token the API accepts, how devices get theirs, and how to choose the organisation on Mojo Up AI Cloud. - [Discovery](/api-reference/discovery): How AI Workbench, nodes and the mobile app find an organisation's platform from a work email, and what the discovery document says. - [Versions and compatibility](/api-reference/versions): How the API is versioned, and how it stays compatible with workbenches already in use. - Endpoints - [Discovery](/api-reference/endpoints/discovery) - [Organisation](/api-reference/endpoints/organisation) - [Cloud sign in](/api-reference/endpoints/cloud-sign-in) - [Cloud account](/api-reference/endpoints/cloud-account) - [Cloud organisations](/api-reference/endpoints/cloud-organisations) - [Devices](/api-reference/endpoints/devices) - [Ingest](/api-reference/endpoints/ingest) - [Catalogue](/api-reference/endpoints/catalogue) - [Policy](/api-reference/endpoints/policy) - [Health](/api-reference/endpoints/health) - Security and trust - [Security and trust](/security): How Mojo Up handles, protects and stores your data, and how to tell us about a security problem. - [Data handling](/security/data-handling): What the Mojo Up platform keeps, what it never sees, how it treats credentials that slip into reports, and how to delete data. - [Encryption and keys](/security/encryption): How the Mojo Up platform protects data in transit and at rest, and how tokens, secrets and remote-control requests are secured. - [Where data lives](/security/where-data-lives): Where Mojo Up AI Cloud stores your data, and how self-hosted AIOE lets you choose. - [The audit trail](/security/audit-trail): An append-only, hash-chained record of what people, agents and machines did, which you can check without trusting the platform. - [Report a vulnerability](/security/vulnerability-disclosure): How to tell Mojo Up about a security problem in AI Workbench, its nodes, the mobile app, Mojo Up AI Cloud or AIOE. - Release notes - [Release notes](/release-notes): What changed in each release of AI Workbench, its nodes, Mojo Up AI Cloud and AIOE. - [AI Workbench](/release-notes/ai-workbench): What changed in each release of the AI Workbench desktop app and its headless node. - Troubleshooting - [Troubleshooting](/troubleshooting): Fixes for the problems people meet most, by product. - [Mojo Up AI Cloud](/troubleshooting/cloud): Fixes for sign-in, invitation, workbench approval and team ownership problems on Mojo Up AI Cloud. - [Troubleshooting AI Workbench](/troubleshooting/workbench): Fix common problems installing AI Workbench, signing in, joining a team hub and running agents. - [Troubleshooting nodes](/troubleshooting/nodes): Fix the common problems installing, joining and running mojoup-node. - [Troubleshooting the mobile app](/troubleshooting/mobile): Fix common problems signing in, seeing workbenches, approving and getting notifications on your phone. - [Self-hosted AIOE](/troubleshooting/self-hosted): Common problems running self-hosted AIOE, what causes them, and how to fix them. - Support - [Support](/support): How to get help with AI Workbench, nodes, the mobile app, Mojo Up AI Cloud and self-hosted AIOE, and what to send.