Product
Five parts. One place for all your apps.
Your agent talks to the CLI. You and your people use Studio and the app store. Runners run the apps on the machines you choose. Everything else, from certificates to backups, is handled for you.
For your AI · the CLI
The tool your agent drives
Every app starts with a guide written for agents: how the app must start, where data lives, how to deploy and how to prove it works. Your agent reads it and gets on with the job.
- Create, deploy, publish and roll forward
- Read logs and app status
- Set secrets without pasting them into chat
- Update the server and Runners
# what your agent runs, so you don't have to $ automaton deploy build · upload · start · health check ✓ lunch-poll is live $ automaton logs lunch-poll --tail $ automaton server update --wait ✓ 0.2.46 healthy
For you · Studio
Your control room in the browser
See every app and who can open it. Invite people, approve what apps may access, add Runners and catalogs, and check backups.
- Per-app access: private, members, or public
- Invites only; no open sign-up
- Permission requests you approve or decline
For everyone · App store and catalogs
Share apps like products
Publish an app with a cover and a description to your own store. Add catalogs from GitHub so your team can install ready-made tools in one click.
- Your store at store.your-domain
- Catalogs from any GitHub repository, public or private
- Fork an app to make it your own
Untranslatable
Bluffing word game
Website Monitor
Outage alerts
Under the hood · Runners
Each app in its own container, on the machine you pick
A Runner is a small agent you install on a server. Start with one on the same machine; add more in other places when you need room or a different country.
- A new version goes live only after its health check passes
- App data survives redeploys
- Scheduled Actions for jobs and reports
- runner
- office-1 · online
- apps
- 14 running · 2 scheduled
- deploy
- new version healthy → switched
- data
- kept across redeploys
- install
- 31–32 s in recent tests
Operations · security and recovery
The boring parts, done
Certificates, secrets, backups and updates are part of the platform, not a weekend project.
- Automatic HTTPS for every app
- Secrets vault per app and project
- Nightly backups; restore to a clean server tested
- Server updates with one request and a health check
- https
- automatic, renewed
- secrets
- encrypted, never in logs
- backups
- nightly · 7 days kept on the server
- restore
- tested on a clean server
- update
- backup → update → health check
Good to know
What Automaton does not do (yet)
We would rather you know before you install.
No autoscaling
Each app runs on one Runner. Add machines yourself; there is no automatic failover.
Bounded live connections
Server-Sent Events and WebSockets work, with a cap on how many one app keeps open and a request body limit.
You run the server
Updates are one request, but the machine, DNS and off-site copies of backups are yours.