Prefer to run nao on your own infrastructure? See the Deployment Guide. The organization and project model below is the same in both.
Step 1: Create your account
Go to app.getnao.io/signup and sign up with email and password, or with Google. On your first sign-in, nao automatically creates a workspace (your organization) with you as its admin - there is no separate setup wizard. If you sign up with a Google address whose domain already has a nao Cloud workspace, you can be added to that existing workspace instead. Already have an account? Sign in at app.getnao.io/login.Step 2: Add your first project
A fresh workspace has no project yet. A project holds one agent’s context, data connections, chats, and members. There are two ways to create one.Option A: Import from GitHub
If your nao project already lives in a GitHub repository (a folder containingnao_config.yaml), import it straight from the browser:
- From the empty-project screen, choose Import from GitHub.
- Authorize the nao GitHub app on the account or organization that owns the repo.
- Pick the repository and branch that holds your
nao_config.yaml.
The repository picker only lists repos the nao GitHub app can access. If yours isn’t listed, add it to the app’s installation on GitHub.
Option B: Deploy from the CLI
If you build context locally with the CLI, push it to your workspace withnao deploy.
-
Build your project locally - see the Quickstart:
- Create an organization API key in the Cloud UI: Settings -> Organization -> API Keys -> Create key. Copy it - it’s shown only once.
-
From the project folder, deploy to your Cloud workspace:
project_name in nao_config.yaml. Deploying a new name creates a project; deploying an existing name replaces its context in place.
nao deploy reference
Full command flags, exclusions,
.naoignore, and create-vs-update behaviorStep 3: Configure the project
Your data connections, rules, and semantics are defined innao_config.yaml and your context folder - edit them locally and re-deploy (or push to the connected Git branch). A few things are set directly in the Cloud UI, under Settings -> Project:
- Environment variables - provide values for the secrets your config references with
{{ env('MY_VAR') }}(warehouse credentials, API tokens), so you never ship them in Git. - Models - add your LLM provider keys and pick the models the agent can use.
- Agent settings - template prompts, MCP servers, budgets, and connectors (Slack, Teams, Telegram, WhatsApp).
Context Builder
Structure the databases, repos, rules, and semantics your agent reads from
Step 4: Invite your team
Add teammates from Settings -> Organization -> Members: invite by email and pick a role. Each new member signs in with their email and the generated password. Members join projects to get access to that project’s chats, context, and data - manage each project’s members under Settings -> Project -> Team. For roles and permissions, see Admin Setup.On Cloud, users who sign in with a Google address on your workspace’s claimed domain can join automatically - no manual invite needed.
Step 5: Start chatting
Open your project and ask a question in plain English. The agent uses your project’s context to write SQL, run it against your connected warehouse, and return results and charts.What’s next
nao Cloud overview
Organizations, projects, members, API keys, and managed env vars
Host multiple projects
Run several projects in one workspace with a project switcher
Synchronization
Automate context deploys with GitHub Actions
Chat Interface
Stories, memory, automations, and admin tools