# Quickstart: from sign-up to a running app

> Create your account and workspace, add a project, connect GitHub, let Aria AI write aria.yaml, choose the plan Aria recommends, and launch.

Source: https://getaria.cloud/docs/quickstart (updated 1 November 2026)

Seven steps take you from sign-up to a running app. You make an account and a project, connect your code, and Aria AI writes `aria.yaml`, the one file that says what your app needs. Aria then recommends a plan and sets up the server, databases and deploys.

You need a GitHub repository with your code. You choose which repositories Aria can read. To use your own AI subscription, you also need the [Mac app](https://getaria.cloud/download). In the browser, an API key does the same job.

## 1. Create your account

1. Open [getaria.cloud/signup](https://getaria.cloud/signup) and choose **Personal** or **Business**. A Business account puts your company's details on your invoices.
2. Enter your details and accept the terms.
3. Aria emails you a six-digit code. Enter it to confirm your email.

Then choose where to work: the [Mac app](https://getaria.cloud/download), or the browser at [getaria.cloud/app](https://getaria.cloud/app). Both show the same workspace.

## 2. Open your workspace

Aria makes your workspace when your email is confirmed. A Business account names it after your company, and a Personal account names it after you. Your projects, servers, team, domains and billing all live here. You can rename it in **Settings**, and turn on two-factor sign-in under your account. See [Workspaces and projects](https://getaria.cloud/docs/workspaces).

## 3. Add a project

A project runs one thing on a server of yours. Under **Create your first project**:

1. Choose **Website** or **Custom App**.
2. Say who it is for, **Personal** or **Business**. A business adds its company and billing address.
3. Name it. Aria suggests Production, and you can rename it later.

## 4. Connect GitHub

Connect GitHub, then choose the repository and the branch. Aria only ever reads your code. If `aria.yaml` is not at the root of the repository, say where it is.

## 5. Let Aria AI write aria.yaml

First connect Aria AI, once. Choose Claude Code, Codex, Gemini, Antigravity, Cursor or OpenRouter.

- **On the Mac,** Aria finds the tool on your Mac and asks **Is this the one?** One click and it is connected, on the subscription you already pay for.
- **In the browser,** paste an API key from Anthropic, OpenAI, Gemini or OpenRouter.

Then choose **Write it with Aria's AI**. It reads your code, asks you a few questions here and writes the file: every service, database and variable. Aria checks the file and shows line numbers for any problem. See [Aria AI](https://getaria.cloud/docs/aria-ai).

Prefer your own tools? Copy the prompt into a coding agent, write it through an agent [connected over MCP](https://getaria.cloud/docs/agents), or paste a file you already have.

## 6. Choose the plan Aria recommends

Aria sizes the plan from your `aria.yaml` and shows the one that fits. Tell it how many people use the app at the same time at its busiest, and pick a location. Each plan is one server, and it can run several projects. You choose the plan. If a server you already have has room, you can use that instead.

Then make three quick choices:

- **Your data.** Start with empty databases built from your migrations, or bring users and data from Supabase, Firebase, Neon or another Postgres. See [Move from Supabase Cloud](https://getaria.cloud/docs/move-from-supabase-cloud).
- **Your web address.** Every app gets a free address you can name. You can also connect a domain you own or buy one. See [Domains](https://getaria.cloud/docs/domains).
- **Email.** Turn on [Aria Mail](https://getaria.cloud/docs/mail) if the app sends email, or do it later.

Pay on Stripe's secure form. Your server is ordered the moment the payment goes through.

## 7. Launch

Aria sets up the rest and walks you through it, one thing at a time: **Server**, **Keys**, **Domain**, **Data** and **Live**.

- **Keys:** enter only the secrets Aria cannot make for you, such as a payment provider's key. They are saved encrypted and never shown again.
- **Domain:** add the DNS records if you are connecting your own domain.
- **Data:** bring your data in if you chose to.

Each step shows as your server reports it, and Aria emails you when the app is live. If a step fails, the finished steps are kept. **Ask Aria to fix it** reads the logs and fixes what it can, with any change waiting for you.

## How do I deploy from the terminal?

The command line does the same with commands. Install it, sign in and connect your repository. It needs Node.js 22 or newer.

```bash
curl -fsSL https://api.getaria.cloud/v1/downloads/cli/install.sh | sh
```

Then, in your repository:

```bash
aria login
aria init
```

`aria login` shows a code that you confirm in Aria. `aria init` links the repository to a project, adds the Aria skill and a short section to `AGENTS.md`, and connects Claude Code over MCP. Now ask your agent: "Use the Aria skill to write aria.yaml and deploy." When the file is saved, deploy and check it:

```bash
aria deploy --wait
aria check
aria open
```

Every command is described on [The aria command line](https://getaria.cloud/docs/cli).

## What does the smallest aria.yaml look like?

This file runs one web service with a Postgres database. Aria creates the database and fills `DATABASE_URL` for you.

```yaml
version: 1
name: my-app
services:
  web:
    type: web
    port: 3000
    healthcheck: /
databases:
  main:
    type: postgres
env:
  DATABASE_URL:
    services: [web]
    from: main.url
  SESSION_SECRET:
    services: [web]
    generate: secret
```

Your service must listen on `0.0.0.0` and read the `PORT` variable. Aria sets `PORT` to the `port` in the file. The full list of fields is in the [aria.yaml reference](https://getaria.cloud/docs/aria-yaml).

## How do I know it works?

The **Overview** page shows your app's state and what needs you. From a terminal:

```bash
aria status
aria check
```

`aria status` lists each service with its status and address. `aria check` tests every service, database, migration, Supabase part and domain, and exits with code 1 if anything fails. To try the app itself, use [Browser checks](https://getaria.cloud/docs/checks).

## What if a service waits for a variable?

A service with a required variable that has no value waits until you add it. **Environment** shows what is missing. From a terminal, run `aria env ls`, then enter each value yourself:

```bash
aria env add EXTERNAL_API_KEY
```

The value is typed with hidden input and never printed. Details are on [Environment variables](https://getaria.cloud/docs/environment-variables).

Next: [Workspaces and projects on Aria Cloud](https://getaria.cloud/docs/workspaces)