The runtime Verduona uses to deliver real AI work.
AgentJack Core connects the cloud account, Mac Desktop app, Linux Runner, and Windows Bridge without turning local execution into another public vertical.
Teams need an operator surface that survives beyond a prompt session.
Chat-only tools lose context when the task leaves the browser tab.
Cloud, local Mac work, Linux runners, and Windows bridges need clear boundaries.
A portfolio of apps needs one runtime that can launch and coordinate them.
A persistent runtime with clear app and device boundaries.
AgentJack Core provides the execution center, app launcher model, gateway paths, approvals, audit, and operator context used by Brain, Knowledge, Workflows, Security, CourseRoom, Collective, Operator, Creator, Mothership, and Infra Worlds.
App launcher
The current AgentJack apps are internal surfaces, not cash-register products.
Local execution choices
Cloud runs always-on work; Mac Desktop gives a local app; Linux Runner handles headless machines; Windows stays Bridge-only.
Governed device bridge
Bridge grants are scoped by workspace, root, and capability before local files, browser, shell, or runner actions are allowed.
How it is used
Choose the app surface
Start from the AgentJack app that matches the desired work.
Choose the execution lane
Use Cloud, Mac Desktop, Linux Runner, or Windows Bridge depending on where the work belongs.
Prove the workflow
Use a five-door Verduona delivery or supervised pilot work depending on the scope. AgentJack itself is not sold.
AgentJack Core is not a shop door
See the five-door shop
This surface is not a cash-register product. The public shop sells five doors only. Orbit is not sold.
Open shopSee the live book
Review the five doors at live shop.verduona.com prices: CouncilNow, BOZP, audit and workshop, sprint and Ops, translations.
Open pricingEmail scope
Scope a five-door order before any delivery work. Do not treat this page as a checkout.
Email scope