Syntax × dUX

Syntax integrates with dUX to provide managed remote inference without you having to manage cloud GPU infrastructure. Managed remote is available to all users; you can also keep using local and self-hosted remote serving without involving dUX at all.

What Syntax brings to dUX

When you choose a managed remote deployment, Syntax sends dUX a deployment intent: which model (or party), which target tier (Latency or Throughput), how many replicas, what exposure (private vs public), what isolation level. The intent is logical — "I want this model deployed at this tier" — not a description of how to deploy it.

Syntax also brings:

• Catalog metadata. The right serving images, the right parameters, the right hardware requirements per model.
• Party-level planning. When the deployment is a multi-model party, Syntax composes the placement intent so dUX sees a coherent multi-model deployment rather than N independent requests.
• Authentication. Bearer-token-based auth for the deployed endpoint, including the per-deployment exposed-bearer flow.

What dUX brings to Syntax

dUX is the orchestrator that provisions and manages the hardware your workloads run on — inside your own cloud accounts, with you as the sole admin:

• GPU placement and scheduling.
• Driver compatibility and provisioning.
• Autoscaling.
• Multi-replica weight distribution.
• Ingress and load balancing.
• Per-organization isolation.
• Lifecycle (start, scale, stop, replace, upgrade).

dUX returns concrete endpoint URLs and status updates back to Syntax as the deployment progresses. The underlying machines remain under your administrative control: dUX operates them on your behalf and you can step in directly whenever you need to.

What stays with Syntax

A few things stay on the Syntax side regardless of where the model ends up running:

• Bridge. Your harness still talks to the local Bridge. The Bridge routes requests to the dUX-managed endpoint behind the scenes.
• Tools and skills. The agent's tool list and skills framework live in Syntax — dUX is purely about serving the underlying model.
• Sessions and memory. Your session history, your memory, and your Plan-Mode plans are all client-side or in your home directory. dUX never sees them.
• Budgets and approvals. Token and compute budgets are computed in Syntax against the active org policy.

This separation of concerns is intentional: dUX orchestrates the cloud GPU hardware on your behalf — in your cloud accounts, with you as the sole admin — and Syntax is your control surface and your developer experience.

What dUX never sees

Putting it the other way: dUX never sees your session content, your prompts, your code, your tool calls, or your harness. It sees model weights to load, deployments to scale, and endpoints to serve — and nothing else.

Where to go next

• Managed remote (dUX) — the developer-facing flow.
• Permissions and IAM — identity boundaries between the two systems.
• Differences vs self-managed — when to pick which path.