Open-source app platform · self-hosted

The home for every app your AI builds. On servers you own.

Your AI can put one app on a server. Automaton runs all of them: sign-in, sharing, an app store, a catalog for your team, secrets, backups and safe updates. Your data stays where you decide, and the cost is the server you rent.

Apache 2.0No Automaton accountOne server to start
Your AI agent deploys apps to your Automaton server, which shares them privately with your team, publishes them in your app store and installs apps from catalogs.Automatonyour serverYour AI agentClaude, Codex, anyStudioapps · people · accessApp storestore.your-domainTeam onlysign-in requiredPublic link*.apps.your-domainCatalogsinstall from GitHub

Why not just a server?

Deploying one app is easy. Running fifty, for real people, is the work.

Ask an AI to copy an app to a VPS and you get one app. Automaton gives you the platform around it, so the tenth app is as easy as the first and every app has the same sharing, security and recovery.

AI + a bare serverAutomaton
Address and HTTPSDNS, ports, proxy and certificates wired by hand for each appEvery app gets its own HTTPS address automatically
Who can open itPublic, or a password you build yourselfPer app: private, signed-in members, or public
Sharing and discoverySend a link and hopeYour own app store, plus catalogs your team installs from in one click
Secrets.env files copied aroundA vault per app and project; platform access needs an administrator's approval
UpdatesA bad deploy takes the app downThe new version goes live only after its health check passes
BackupsIf someone remembersNightly backups; restore to a clean server tested
Starting pointYour AI writes every app from scratch, every timeInstall proven apps from catalogs in one click, then fork and adapt
Your AI's instructionsRe-explained every sessionEach app ships with a contract and guide your agent reads

One platform

Everything an app needs after it is built

Built for AI agents

A command line your agent drives, with generated guidance: how to build, deploy and prove an app works.

People and access

Invite people, choose who can open each app, and approve what apps may do.

Your app store

Publish apps with a cover and a description at store.your-domain, for your team or the world.

Catalogs

Point Studio at a GitHub repository of apps. Your team installs from it in one click.

Fork and iterate

Copy an app to try an idea, deploy again in seconds, and keep the version that works.

Data you control

Apps, data and backups stay on your machines. Add more servers when you need them.

See the whole product →

Catalogs

Don't rebuild what already exists

Apps can wait as source code in GitHub repositories until you need them. Add a repository as a catalog, and its apps appear in Studio, ready to install on your server whenever you want. Pick tested, popular open-source apps instead of asking your AI to write everything from nothing.

  • Source stays in GitHub until you install it; nothing runs until you choose
  • Built from source on your own server, so you can read exactly what runs
  • Fork an installed app and let your AI adapt it
  • Packaging an existing open-source app takes one small file your agent can write

Browse the catalog →

// maintenance/site-links/automaton.json
{
  "name": "Automaton Site Links",
  "summary": "Crawls your sites and reports broken links.",
  "application": { "secrets": [ "GITHUB_TOKEN" ] }
}

Who it is for

From one curious builder to a whole company

Creators

Build small things with your AI and keep them in one place.

  • Every idea gets its own link in minutes
  • Publish the good ones to your app store
  • One small server instead of many subscriptions
I build a new tool most weekends. They all live on one small server, and my friends open them from my store.Example use, not a customer quote

Setup

Your AI installs it. You just say where.

Rent a small Linux server, point a domain at it, and hand your agent the address. It follows the public guide and reports back. A working server took 2-3 minutes in test runs.

Rent a server and a domain

Any x86_64 Ubuntu or Debian machine with 4 GB of memory. About €7 a month at common providers.

Ask your agent

Give it SSH access, your domain and an email. It reads automaton.monster/llms.txt and does the rest.

YouInstall Automaton on my server (ssh root@203.0.113.10) at example.com, use me@example.com for certificates, and deploy a small app.

Start building

Open Studio, invite your people, and ask for your first app. It shows up with its own address.

YouBuild a lunch poll for my team and share it with them.

How setup works, step by step →

Open source · Apache 2.0

Own the place where your apps live.

See apps running on Automaton today, read the docs as plain text, or start your own server.