Core product Core runtime

The runtime underneath the approved AgentJack app portfolio.

AgentJack Core connects the cloud account, Mac Desktop app, Linux Runner, and Windows Bridge without turning local execution into another public vertical.

The problem

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.

The solution

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.

Approved app launcher

Only the current AgentJack apps are presented as public 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 approved 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.

Ship the outcome

Use product access, Verduona implementation, or done-for-you delivery depending on the scope.

Plan AgentJack Core

See pricing

Review how Verduona scopes training, consultation, implementation, and delivered outcomes.

Open pricing

Book a call

Scope the right lane before committing to product access or delivery work.

Book call

Email Verduona

Send the use case, segment, and desired outcome so the work can be priced correctly.