Why Syntax?
The reasons teams pick Syntax over rolling their own AI deployment stack.
There are plenty of ways to call an LLM from a coding tool or product. The reason teams pick Syntax — and stay on it — is that it solves a handful of hard problems together that are usually solved separately and badly.
1. Predictable Costs
dUX bills hourly for compute, not per token. Billing is decoupled from token consumption entirely, so autonomous agents can't quietly run up a bill — costs are capped by the hourly rate of the hardware you've provisioned. The Syntax platform itself is provided at zero additional cost; you pay the underlying provider plus dUX's premium and nothing else.
2. Private & Secure
Managed remote deployments run on WireGuard-based internal networks. Endpoints are not reachable from the public internet unless you explicitly opt in by issuing a public exposed bearer; private exposures stay entirely within your perimeter.
Neither Syntax nor dUX will ever access your machines, data, logs, files, or code. Integrate dUX with your own secrets manager and that becomes a technical guarantee — not a vendor trust statement — that no one outside your org can reach your infrastructure. Enterprise tenants run in fully isolated environments; on-premise and air-gapped deployments are first-class.
3. Optimized deployments
Choosing how to run a given model is a real engineering problem. The right combination of hardware SKU, cloud instance type, serving engine, attention backend, quantization format, and parallelism strategy differs for every model — and a model that's "supported" by two different engines may only run well on one of them. Syntax's autotuner navigates that decision space for you, across the catalog and across the available hardware.
When you deploy a multi-model party, the same autotuner plans the whole party: packing co-tenants where it saves cost, isolating models that would harm each other's latency, and propagating your Performance vs Cost-optimized tier across every model. You choose a tier and a target; everything below is handled automatically and scales from zero to whatever sustained traffic demands.
→ Differentiators → Multi-engine inference
4. Use the harness you already love
Syntax doesn't ask you to switch editors or learn a new IDE. Codex,
Claude Code, OpenCode, Pi, and the Syntax-native syntax-cli all
work out of the box. The integration is reversible: syntax connect
edits the harness's own configuration to point at Syntax, and
syntax disconnect puts it back exactly the way it was.
The point isn't just compatibility — it's that you can keep the tool you already trust while shifting the workload underneath it onto cost-efficient OSS models you deploy yourself. The harness doesn't care; you get the same UX with a fraction of the per-task cost.
→ Differentiators → First-class inter-compatibility
5. Pick the best model for the job
A real workflow needs a strong main model, a cheaper sub-agent, and sometimes specialists for things like image understanding, OCR, search, embeddings, or image generation. Syntax's Models Party lets you compose those into a single deployment with one main agent, one default sub-agent, and up to six specialists — and the main model can call specialists as tools.
This is where the cost story compounds. Most "frontier model" workloads are actually a mix of simple, routine, and genuinely hard sub-tasks. A well-composed party routes the simple and routine work to small, cheap models and reserves frontier capacity for the small fraction of tasks that actually need it.
→ Differentiators → Multi-model parties
6. Scale to the cloud without managing infrastructure
For team and production workloads, the same model name you ran locally resolves on managed remote infrastructure via dUX, with autoscaling from zero to whatever traffic demands already wired in across dozens of public cloud providers. dUX provisions the hardware inside your own cloud accounts — you remain the sole admin, and you describe what you want; dUX handles placement, drivers, autoscaling, ingress, and lifecycle.
And one bonus: AI-agent-friendly
These docs ship as a normal website and as a Markdown corpus an AI
agent can ingest in one fetch. Every page has a raw-Markdown sibling
URL. There's a llms.txt index, a full
corpus, and a JSON sitemap.
When an agent in your codebase needs to reason about Syntax's
capabilities, point it here.