The ease of Vercel and Supabase, on a server that’s yours alone. Your coding agent describes your app, Aria sets up the server, databases and deploys around it, and you run it all from a native Mac app.
For macOS 26 or later.
No config to write by hand. Your coding agent reads the code, and Aria does the setup.
In the Mac app, choose Starter, Developer, Pro, Business, Scale or Scale Plus. Not sure? Aria suggests one once it has read your stack file.
Choose the repositories Aria may see. It asks for read access, nothing more.
Needs Aria’s GitHub AppClaude Code, Cursor or any other agent reads your repository and writes aria.yaml.
The server, the databases, every service and environment variable. Then it redeploys on every push.
aria.yaml lists what your app needs to run: its services, databases and environment variables. You don’t write it. Aria gives your coding agent a prompt, the agent reads your repository and writes the file, and Aria checks every line before anything is created.
from: main.url hands each service its database address. No connection strings to copy.
Aria generates session keys itself and asks you only for what it can’t know, like a Stripe key.
Aria estimates the memory your stack needs and suggests the smallest plan that fits.
version: 1services: web: type: web path: apps/web context: . framework: nextjs build: pnpm install --frozen-lockfile && pnpm --filter web... build start: pnpm --filter web start port: 3000 healthcheck: /api/health domain: "@" worker: type: worker path: apps/worker start: node dist/worker.jsdatabases: main: type: postgres cache: type: redisenv: DATABASE_URL: services: [web, worker] from: main.url REDIS_URL: services: [web, worker] from: cache.url SESSION_SECRET: services: [web] generate: secret STRIPE_SECRET_KEY: services: [web] required: true secret: true description: Stripe secret key, from the Stripe dashboardValid: 2 services, 2 databases and 4 variables. Needs your value: STRIPE_SECRET_KEY.
Estimated memory 6.3 GB, so Developer fits. An estimate, not a measurement.
Each one says where it stands today. Planned means it isn’t built yet.
Websites, APIs, workers and static sites from one repository. Aria builds with Railpack or your Dockerfile, keeps the logs, and rolls back in about two seconds.
webapiworkerstaticNew commits redeploy only the services they touch. Local git folders work today; GitHub repositories need Aria’s GitHub App.
Aria fills in what it can, like database addresses and generated secrets. You fill in the rest, one by one or by pasting a whole .env.
Services that need a value you haven’t given yet wait, then deploy as soon as you add it.
Connect Claude Code with one command. It can read status and logs, submit aria.yaml and deploy your workspace, and its key only reaches that one workspace.
The official self-hosted Supabase on your own server, wired into your services, with a guided move from Supabase Cloud: the exact commands to copy your database, then a prompt for your agent to move the rest.
Point your domain at your server and Aria checks the DNS and takes care of the certificates.
Real domains need a server on the internet. On the local server, .localhost names work straight away.
One line of aria.yaml gives your app an SMTP server, with the settings wired in and every email readable in Aria.
Emails land in a private test inbox for now. Sending to real inboxes needs a Resend key.
Aria checks CPU and memory every minute. When your app outgrows its server it suggests a bigger plan and emails you, and switching resizes the server without stopping it.
Every action in Aria has a safety level, and Aria’s own rules enforce it, not the AI. A clever prompt can’t talk its way past them, and the same rules apply to Claude Code and other agents.
Runs straight away
Status, logs, health, resource use and deploy history. Reading never changes anything.
Needs your approval
Deploys, restarts, installs and settings. When the AI or an agent asks, you see what will happen first.
Needs you to type the name
Servers, databases and their data. The AI can ask, but only you can confirm it.
Here is where each part stands. Statuses come from this Aria server’s own settings, so nothing is called Real before it is.
| Part | Status | Details |
|---|---|---|
| Accounts and sign-in | Real | Create an account, verify your email with a 6-digit code, sign in, reset your password, turn on two-factor authentication, download your data or delete your account. |
| Emails from Aria | Local only | Codes are sent for real, but in development they arrive in a local test inbox, not your mailbox. |
| Stack file (aria.yaml) | Real | The prompt for your coding agent, line-by-line validation, a draft Aria writes from your code, and a memory estimate that suggests a plan. |
| Server setup | Local only | Creates the server, pins its SSH identity, installs Docker, a firewall and Aria’s server tools, then checks its health. |
| Deploys and rollback | Local only | Builds with Railpack or your Dockerfile, switches over without downtime, keeps build and runtime logs, and rolls back in about 2 seconds. |
| PostgreSQL and Redis | Local only | Created, connected to your app, health-checked and backed up on the server. |
| Environment variables | Local only | Wired from your databases, generated, or set by you (one by one or by pasting a .env). A service waits for missing values and deploys when you add them. |
| Claude Code and other agents (MCP) | Local only | Connect Claude Code with one command. Its key only reaches one workspace, and changes to variables or anything destructive still need your approval. |
| GitHub and deploy on push | Not configured | Redeploying the services a commit touches works today with local git folders. GitHub repositories need Aria’s GitHub App, which isn’t set up yet. |
| Cloud servers | Not configured | Built and tested: ordering a dedicated server, its firewall, setup, resizing and release. It opens once Aria’s cloud account is connected; no real server has been created yet. |
| AI Operator | Not configured | Reads logs and server state, shows its evidence and asks before changing anything. It needs an Anthropic API key; so far it is tested with a scripted model. |
| Plans and checkout | Not configured | Prices are drafts. Payments through Stripe are built (checkout, invoices, VAT, failed payments); until Stripe is connected, checkout is a test-mode demo and no card is charged. |
| Setting up everything from aria.yaml | Local only | One launch creates the server, databases, variables and every service in the file, then checks each one answers. |
| Self-hosted Supabase | Local only | Postgres, Auth, REST, Realtime, Storage and Studio on your server, wired into your services, with direct database access and a guided move from Supabase Cloud. |
| Domains and HTTPS | Local only | .localhost names work on the local server now. Real domains check DNS and get certificates once the server is on the internet. |
| Email for your app | Local only | An SMTP server for your app with a private test inbox you can read in Aria. Real delivery needs a Resend key. |
| Server upgrades and size suggestions | Local only | Changing plan resizes the server while it runs. Aria samples usage every minute and suggests a bigger plan (and emails you) when memory, CPU or disk run short. |
| Hetzner, DigitalOcean and Vultr | Planned | More places for your server to run. |
| Offsite backups | Planned | Copies of your backups kept away from your server. |
Create an account, confirm your email and download the Mac app. Plans start at £8 a month, and today’s prices are drafts.