# Automagik Arca > Automagik Arca runs your services on machines you own. This file is for an assistant reading for a person. It is the record of what Arca does today, exactly. The page at https://automagik.si/arca/ is a launch page, and it speaks of where Arca is going. For what works now, go by this file. Each line in the four lists below is a fact from the project's own record of facts (`facts.json`), word for word, under the state that fact has there: works today, not yet, being built, or planned. After the lists: the install line, and how to put a person on Arca early access. ## Works today - Automagik Arca runs your services on machines you own. - Arca is one program. - Arca is open source under the Apache-2.0 licence. - These run from the templates Arca ships: Postgres, NATS, Omni and the Automagik server. An assistant proposes one, and nothing runs until you approve it with your passkey. - The Automagik server starts from Automagik's published image, pulled by its digest. Nothing is built on your machine. - The services Arca runs fetch their pinned images from public registries when they are created. - A running Automagik server moves to a newer Automagik in one step that keeps its data and puts the old version back if the new one does not answer. That step needs a token of the kind called `doctor`, which the installer does not give out and which changes things without your approval. - GitHub runner pools run from a template Arca ships, on a node where virtual machines are turned on in the config by hand. - A small program in a container image you name can run on a timer, as a function, once you approve its card. - The node is an MCP server over HTTP. An assistant with a shell on the same machine reaches it with `arca call`. - With the token the installer gives it, an assistant can only look and propose; you approve with your passkey. - You approve on a page the node serves on the machine itself. You enrol a passkey with a setup code from the machine. - Arca checks passkeys itself; no outside sign-in service is involved. - Arca keeps an append-only journal of the changes it applies. Starts, stops and restarts are logged separately. - The Doctor, Arca's own assistant on the canvas, reads the state of your machines and services, including Arca's alerts, and proposes changes that you approve. - A fresh install only looks: it changes nothing until you tell it which parts are its own. - Arca can save snapshots of a service onto a disk you plug in. - Two Arca machines can be paired with a one-time code, so an assistant on one can reach the other. You start pairing by hand. - On your own machine, your services' secrets stay on that machine. - Arca is self-hosted: it runs on machines you own, and Arca itself needs no outside service to work. - Arca is early software, before version 1.0: things can still change from one release to the next. Each machine runs its own Arca. - One Linux machine (x86_64 or ARM) with Incus. - One program for Linux on x86_64 and one for Linux on ARM (aarch64). It needs a recent Linux (glibc 2.34 or newer: Enterprise Linux 9, Ubuntu 22.04, Debian 12, or newer), Incus running on the machine, and a user allowed to read Incus. - One line installs Arca on a Linux machine (x86_64 or ARM) that already runs Incus. It sets Arca up to look only: Arca changes nothing on the machine it runs on until you say which parts are Arca's. - The installer never asks for sudo, refuses to run as root, writes only in your home folder, and a second run updates in place. - The installer sets up a node that only looks. An assistant with its token reads your projects, instances, host readings and alerts, and changes nothing. - The installer opens the node's MCP door for this machine only, and only with a token, and prints the one line that adds it to Claude Code. - The install gives you a node that only looks: it reads your machines and changes nothing. One step lets it change things: `arca init --enable-changes`, or `--enable-changes` on the install line. - `arca status` says in words whether the node only looks or may change things, and what to do next. ## Not yet - The one step that turns on changes does not turn on virtual machines (the workspace and the GitHub and GitLab runner pools) or taking over a service that already runs on the machine. Each is set in the config by hand. - The installer opens no address another machine can reach. An assistant on another machine needs a listener added to the config by hand. - The installer does not install Incus or give your user access to it. - The installer stops on anything but Linux on x86_64 or ARM. - Approving from a phone needs the node reachable under a name with a certificate, set up by hand. - The approval page on the machine is for a machine where every account is trusted. It has been tested with a test browser's passkey, not yet with a real passkey manager. - Arca cannot run an app you name as a service, something that keeps running: a service comes from a template Arca ships. - A service that needs a secret of yours does not start from the page alone: the Cloudflare tunnel, for example, is created stopped until its token is set. - The GitLab runner pool is new and has not run against a real GitLab. - Arca cannot yet restore a snapshot you took: restoring is done by hand with Incus. When updating a service fails, Arca puts the old version back by itself. - The ChatGPT and Claude apps cannot connect to Arca in one click yet. - Arca does not repair things by itself. - Arca does not yet spread your services across machines by itself. - There is no installer for a Mac itself; a Linux virtual machine on a Mac counts as a Linux machine. The installer has not been run on a machine that never had Arca or Incus. - Arca OS: where we are going. It takes over a whole machine and erases its disk. Not available for download yet. ## Being built - There is no hosted Arca you can use today, and nothing has a price yet. - Arca Cloud, the same thing on machines we run, is being built. It is not open. - You can join the waitlist for Arca Cloud. You confirm with one emailed link. ## Planned - A check that tells you what your machine can carry. - Arca OS takes over a whole machine: everything on its disk is erased. - The first Arca OS release will need an Intel or AMD machine with Secure Boot and a TPM 2.0 chip, on a wired network. Many old devices will not qualify. ## Install The install line, for a terminal: `curl -fsSL https://get.automagik.si/arca | sh` What the line needs and what it does to the machine is said once, under "Works today": the fact that begins "One line installs Arca". The same, as words to give an agent: `Download https://get.automagik.si/arca, read it, run it with sh, and tell me what it printed.` ## The tool for Arca early access Arca early access is the list of people who asked to be told first. Use the tool when your person asks to be put on it, with the answers they gave you. Only the email is required. - Endpoint: `https://automagik.si/arca/mcp`. MCP over streamable HTTP. No sign-in and no session. - One request per POST. A batch (a JSON array) is refused. - The answer is JSON: one JSON-RPC message. A client of the current protocol gets it as a JSON body. An older client gets it as the one `data:` line of an event stream. Either way the request must accept both `application/json` and `text/event-stream`. - A request body over 8 KB is refused. - Tool: `join_waitlist` - What the tool says of itself: "Put a person on Arca early access: what they want to run, which door (mac, linux, os, agent, cloud, phone), the machines they own if they said (laptop, desktop, mini PC, server, Mac, phone, with how many), and their email. Only the email is required. They confirm by one emailed link." - Arguments: - `wants`: string, optional, at most 500 characters. What the person wants to run. - `where`: string, optional, one of `own`, `cloud`, `both`. Their own machine, Arca Cloud, or both. - `door`: string, optional, one of `mac`, `linux`, `os`, `agent`, `cloud`, `phone`. The button of the page the person came in by, when you know it. Any other value is refused. - `machines`: object, optional, a whole number from 0 to 99 for each of `laptop`, `desktop`, `minipc`, `server`, `mac`, `phone`. The machines the person owns, when they said: how many of each kind. `minipc` is a mini PC. Each count is a JSON number: a count written as text (`"2"`) is refused. Leave out a kind they did not name: 0 is the same as left out. Any other kind, and any other count, is refused. `machines` is not a door you can name: a join that carries at least one count above 0 is stored with the door `machines`, whatever `door` says. `door` is still checked. - `machine`: string, optional, at most 200 characters. The machine they have, in their own words. - `today`: string, optional, at most 200 characters. What they use or pay for today. - `email`: string, required, at most 254 characters. One plain address, of the person who confirms. - The tool's answer is one text item that holds JSON with a `status`: - `check_email`: accepted. Ask the person to open the link in their email. - `invalid`: an argument was refused. `error` names it. When `error` is `email_plain`, the address has an accent or another character outside ASCII, and those are not taken yet: ask the person for an address written with plain letters. - `daily_limit`: Arca early access is full for today. Try again tomorrow. - `mail_failed`: the email could not be sent, and nothing was saved. - `unavailable`: Arca early access is not taking requests right now. - The person gets one confirmation link by email. It works once and is valid for 24 hours. A join that is not confirmed in that time is deleted. - The answer is the same whether or not the address was already on the list. An address that is already on it gets no second mail. - Too many requests in a minute from one address are refused with HTTP 429. - Submitted text is stored as data. It is never opened, fetched or run. Without an MCP client, one POST does it. Send `Content-Type: application/json` and `Accept: application/json, text/event-stream`, with this body, and put the person's address in place of `THE_PERSONS_ADDRESS`: ``` {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"join_waitlist","arguments":{"wants":"A database and two small services","where":"cloud","door":"cloud","email":"THE_PERSONS_ADDRESS"}}} ``` ## The form - [Arca early access, as a form on the page: it asks for the email](https://automagik.si/arca/#first) ## The page and the code - [The page](https://automagik.si/arca/) - [The page as plain text](https://automagik.si/arca/index.md) - [The code](https://github.com/automagik-si/arca)