Local Execution. Central Control.

Keep the target private.
Bring AXQA to the test.

Smart Agent extends AXQA execution into approved local machines, internal labs, private networks, and restricted environments. The test is designed and tracked in AXQA, executed where the target actually lives, and returned as structured results without forcing the target into a public testing path.

See the execution path Run the simulation

Interactive flows on this page are simulations designed to explain Smart Agent behavior and policy enforcement.

AXQA Cloud Test Orchestration
CaseStepsValidationResult
encrypted execution channel
Customer Environment Private network
Smart Agent Local Execution Node
Connected & ready
Private Target Internal API 10.20.0.15 · Local only
Local path available
Cloud Control
Keep test design, assignment, status, validation, and reporting inside AXQA.
Local Execution
Run approved test steps from the machine or network that can actually reach the target.
Policy Guard
Evaluate the requested target against local execution policy before the request is allowed to continue.
One Audit Trail
Return execution state and test results to the same QA workflow instead of creating a disconnected local process.
The Smart Agent execution model

AXQA stays in control. The execution moves closer to the target.

Use Smart Agent when the system under test cannot or should not be reached directly from the AXQA server. The agent provides an approved local execution path while AXQA remains the source of the test case, execution logic, validation, status, and reporting workflow.

01
Control plane

AXQA Cloud

Execution #AX-2048
TEST CASEINT-042 · Validate private order service
EXECUTIONSmart Agent
STATEReady

AXQA prepares the ordered steps, validation rules, and execution context.

02
Local execution

Smart Agent

AGENT
Agent authenticated
Execution context received
Target policy evaluated
03
System under test

Internal API

10.20.0.15:8443 POST /orders/validate Reachable from the approved local environment, not from the public test path.

Only the local environment needs network reachability to the target used by the test.

04
Results return to AXQAResponse data → validations → execution status → history → reporting
Execution should not mean unrestricted access

A local path with a security gate in the middle.

Smart Agent is designed around approved execution. Before a simulated request reaches the target, the flow below shows a policy decision. Allowed targets continue to local execution; a target outside the configured policy is stopped before the request is sent.

Authenticated executionThe execution path is tied to the connected Smart Agent.
Target policy evaluationRequests are evaluated against the local execution controls before continuing.
Traceable result flowExecution outcomes remain connected to the AXQA workflow and history.
ZERO-TRUST POLICY SIMULATIONLocal Execution Guard
ALLOWED
Target requested 10.20.0.15:8443
Agent identityConnected agent recognized
Target networkMatches approved private range
Execution decisionRequest may continue locally
Interactive Smart Agent mission control

Watch one test travel from AXQA into a private environment and back.

Choose an environment, then run the simulation. The animation follows the execution job through cloud orchestration, local policy evaluation, target execution, validation, and result synchronization.

Smart Agent MissionAX-2048
READY
AXQA Cloud Orchestrate
Policy Guard Authorize
Smart Agent Execute locally
Internal API 10.20.0.15
response + validation data return to AXQA
PolicyWaiting
Local Requests0
Validations0
Result—
execution.log IDLE
$ Smart Agent simulation ready...
Where local execution changes the workflow

Different environments. The same AXQA control model.

01

Private APIs & Services

Execute against internal endpoints from an approved machine that already has access to the private network.

AXQAAgentPrivate API
02

Mobile & Device Labs

Keep the test workflow in AXQA while a local control interface reaches devices or tools available only inside the lab.

AXQAAgentLab
03

Developer & QA Machines

Run against localhost or machine-specific environments when the target exists only on the tester or developer workstation.

AXQAAgentLocalhost
04

Restricted Client Networks

Use an authorized local execution path when the customer environment is intentionally isolated from public access.

AXQAAgentClient Env
A clear responsibility boundary

Smart Agent extends reach. It does not remove authorization.

Smart Agent should only be installed and used on environments, systems, applications, devices, APIs, and networks the customer is authorized to test. Local execution gives AXQA a controlled path to approved targets; it is not a mechanism for bypassing network or access restrictions.

Authorized environmentExecute through approved local policy
Outside policyStop before target execution
Cloud QA without cloud-only limitations

Test where your systems actually live.

Design the workflow in AXQA. Execute from the approved local environment. Bring the result back into one connected quality operation.

Create your workspace See how AXQA works