Aeon is an autonomous agent framework that runs recurring work on your own GitHub Actions: monitoring, code review, research digests, security scans. Set a task once and it runs on schedule without you.
Hivra hosts Aeon's dashboard on a small managed computer. Connect with a GitHub token after launch, and the computer sets up your own fork of Aeon on GitHub. Then configure tasks inside Aeon's own dashboard. The heavy lifting happens on your fork's GitHub Actions, not the computer.
Because the computer is so light, Aeon does not draw on your plan's shared CPU and RAM. Plans start at $9.99 a month.
What you get
- Tasks run on your own GitHub Actions, not on the computer.
- Near zero compute. It does not draw on your plan's CPU and RAM.
- Connect a GitHub token on the computer after launch.
How it works
- Sign up and launch AeonLaunch opens with Aeon selected. Choose where it runs and a plan, and name the agent. Aeon barely uses any compute.
- Hivra provisions a small computerIt hosts Aeon's dashboard behind an authenticated gateway.
- Connect your GitHubEnter a GitHub token on the computer. The computer uses it to create your Aeon fork (or sync the one you have), turn on its Actions, and store your task secrets there. Give the token Read and write access to Secrets, Actions, Contents and Workflows.
- Schedule tasks in Aeon's dashboardDaily digests, PR review, recurring scans. They run on your GitHub Actions, unattended.
Self-hosted vs managed, honestly
- You can self-host Aeon's dashboard on any server. Then you own uptime, updates, and the reverse proxy.
- Hivra stands the dashboard up behind an authenticated gateway.
- Either way the tasks run on your own GitHub Actions with your own credentials.
- On Hivra it barely touches your plan's compute, so there's little to save by self-hosting.
Common questions
What does Aeon cost on Hivra?
Plans start at $9.99 a month. The computer only hosts Aeon's dashboard, so it does not draw on your plan's shared CPU and RAM. Task minutes run on your own GitHub Actions account.
What do I need to connect?
A GitHub token, entered on the computer after launch. The computer uses it to create an Aeon fork in your GitHub account (or sync the fork you already have), turn on Actions for it, point the dashboard at it, and store your task secrets on it as repository secrets. The token needs Read and write access to Secrets, Actions, Contents and Workflows on that fork, or the connect stops and tells you what to change. Credentials may be stored on that computer, and Hivra administrators keep infrastructure access to Hivra-managed hosts.
Where do Aeon's tasks actually run?
On your own GitHub Actions, in your Aeon fork. The Hivra computer hosts the dashboard; the recurring work runs in your GitHub account with credentials you control.
What kind of work does Aeon do?
Recurring, unattended tasks: daily research digests, automatic pull-request review on your repos, and recurring security or market scans.
What happens when I close my laptop?
Nothing changes. The dashboard stays hosted and the tasks run on GitHub's infrastructure on their schedule.
Is this a modified version of Aeon?
No. The computer runs the Aeon project exactly as it ships. Hivra is an independent hosting service and isn't affiliated with the Aeon project.
Hivra is independent and is not affiliated with the Aeon project.