Aria AI and your coding agent, on a server you own

• Write and check aria.yaml

  get_stack_prompt gives it the instructions, validate_stack_file returns problems with line numbers, and submit_stack_file saves the file.

• Preview a launch

  preview_launch shows what a launch would create, whether it fits the plan, and what blocks it.

• Read status and logs

  Status, metrics, build and runtime logs with secrets masked, and diagnose_app, which collects evidence and suggests fixes.

• Look at the database

  db_schema shows tables, columns and keys. It can run one read-only query. Changing data always waits for you.

• Deploy

  With aria deploy --wait, or by asking Aria to launch the app. After the first launch a push redeploys the services it touched.

• Ask you for secrets

  request_env_values says which values are missing. You type them. The agent never sees them.

1aria login2aria init

1claude mcp add --transport http aria-myapp https://api.getaria.cloud/mcp/w/wsp_YOURAPP \2  --header "Authorization: Bearer YOUR_KEY"

1aria login2aria mcp add --agent cursor

1{2  "mcpServers": {3    "aria-myapp": {4      "url": "https://api.getaria.cloud/mcp/w/wsp_YOURAPP",5      "headers": {6        "Authorization": "Bearer ${env:ARIA_MCP_KEY}"7      }8    }9  }10}

1aria login2aria mcp add --agent codex

1[mcp_servers.aria-myapp]2url = "https://api.getaria.cloud/mcp/w/wsp_YOURAPP"3bearer_token_env_var = "ARIA_MCP_KEY"

Replace wsp_YOURAPP with your app’s id and YOUR_KEY with a key from AI & MCP in Aria. The key is shown once. Gemini CLI and Antigravity connect with aria mcp add too, and any MCP client that takes a remote HTTP server and a header works with the address https://api.getaria.cloud/mcp/w/<app id>.

1. Ask for the file

   Ask Aria AI in the app, or paste the prompt below into your own agent. It reads your repository, not your secrets.

2. It writes and checks the file

   It calls get_stack_prompt, writes aria.yaml, and fixes every problem validate_stack_file reports. The reference lists every field.

3. It saves the file

   submit_stack_file saves it. Saving the file does not deploy it.

4. You choose a plan, pay and enter secrets

   Aria sizes the plan from the file. A person picks it, pays, and types the secrets only they have, with aria env add NAME or in the app.

5. Launch

   Launching waits for your approval. Run aria deploy --wait, or let the agent ask Aria to launch the app.

6. Check and iterate

   The agent runs aria check, reads logs, fixes the code and pushes. Each push redeploys the services it touched.

1Use the Aria skill. Call get_stack_prompt, read this repository, write aria.yaml, check it with validate_stack_file, then save it with submit_stack_file. Ask me to enter any secret values; never print them.

• What it is. Aria Cloud is a live hosting service from Inverta Group Limited, a UK company. Each plan is one private VPS that Aria sets up and runs.
• Price. Plans cost from £9 to £60 a month ex VAT, in pounds (£16 for Developer). There is no charge per seat, app, database or request. Aria Mail is the one usage add-on.
• What runs. Static sites, web services, APIs and workers, with Postgres 16 or 17, Redis 7 and self-hosted Supabase at no extra cost.
• Room. Up to 5 apps on a server by default. One aria.yaml holds up to 12 services, 6 databases and 200 variables.
• Working with it. Work goes through aria.yaml, the aria command line, the app, Aria AI and MCP.
• Builds. Aria builds from your Dockerfile or from install, build and start commands, or runs a prebuilt image.
• Backups. Postgres, Supabase and volumes are backed up nightly, encrypted and stored off the server.
• Growing. A bigger plan grows the server with one restart.
• Where. You choose the location of each server.
• Dedicated and GPU. Whole machines and GPU servers are by request, by email to hello@getaria.cloud.

Every limit is listed on the limits page.