Supervise with frontier intelligence
Put the strongest model in charge.
A frontier agent can plan the mission, delegate work, inspect evidence, and correct the fleet without doing every routine step itself.
Autonomous AI workforce on hardware you control
Give Grex a mission. It coordinates AI agents across one laptop, one desktop, or a fleet of machines you control — with the browser, filesystem, compute, and tools needed to finish real work.
Use Hermes and the dashboard to check in, steer, and approve while you are away. Use frontier intelligence to supervise, budget intelligence to execute, and supported AI subscriptions instead of paying for every token.
The operating model
Grex turns the computers you already own into an asynchronous AI workforce. Start the work during the day, stay connected from anywhere, and return to outcomes instead of an open chat waiting for its next prompt.
Describe the outcome in Hermes or the dashboard, then define budgets and approval boundaries.
Agents plan, delegate, browse, run code, use files, and operate connected tools across your machines.
Check progress, answer questions, change direction, and clear approval gates from Hermes or the dashboard.
See what finished, what changed, what it consumed, and the evidence behind every material action.
Your compute. Your choice.
A laptop or desktop you already own is enough. Add another computer when you want more capacity or a different role. Cloud machines are optional, not a prerequisite.
Supervise with frontier intelligence
A frontier agent can plan the mission, delegate work, inspect evidence, and correct the fleet without doing every routine step itself.
Execute with budget intelligence
Budget agents perform the volume work under supervision. Mix models by role instead of paying frontier-model rates for every action.
Use supported AI subscriptions you already pay for. Grex can run through authenticated subscription access instead of requiring per-token API billing. Metered APIs remain an option when you want them.
Built for real work
Grex agents can use the browser, filesystem, shell, local compute, repositories, and connected services. They work in the same environment where you work.
One machine can run one or more crews. Add machines as the mission grows. Organize agents around business functions instead of keeping everything trapped in one conversation.
Use supported subscriptions, metered APIs, or both. Assign different models to different roles and change the underlying engine without changing the mission or its controls.
Receipts show what changed, budgets bound consumption, and approval gates stop irreversible actions. Full machine access is paired with an operator-visible record.
What mission would you hand to a fleet of computers working while you are away?
Share your interest