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 presented as usable product surfaces.
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 product access, Verduona implementation, or supervised pilot work depending on the scope.
Plan AgentJack Core
Request checkout route
Use the controlled Verduona shop path when you are ready to buy or activate. WooCommerce handles checkout; Sphere controls entitlements and provisioning.
Request checkoutSee pricing
Review how Verduona separates product access, metered usage, training, consultation, implementation, and delivered outcomes.
Open pricingBook a call
Scope the right lane before committing to product access, checkout, or delivery work.
Book call