FenxARC™ began as a privacy-first router. The Hosted Platform runs on a zero-access architecture. Queries and responses pass through the router in encrypted form, and FenxLabs does not access, read, inspect or decrypt query content. What FenxLabs processes is the routing metadata a service needs to run and to bill: timestamps, model selections and token counts.
Last reviewed August 20, 2026. Owner: FenxLabs.
Policy determines which models, tools and route options are permitted. ARC ranks only those permitted options.
A list groups the models, tools and rules approved for a team or use case.
01
Confirm who is calling and which list governs the request.
02
Classify the task, complexity, sensitivity, format and any custom categories.
03
Remove models and tools that do not meet access, privacy, capability, limit or budget requirements.
04
Build the permitted route options and order them using the objective defined for the active list.
05
Execute the highest-ranked approved route. If none qualifies, stop the request.
Unauthorised requests are blocked before any tokens are consumed.
FenxLabs resells no inference and holds no commercial relationship with any model vendor. The router has no commercial reason to prefer one destination over another.
Each provider you approve arrives with its own terms, data controls and charges, and those remain yours to review.
ARC keeps privacy evaluation in the routing decision, but your organisation defines what private means. Apply that policy across model routing or to a specific list, and ARC enforces it before ranking a route.
Name a category your organisation works with, define the conditions that make a request match, then choose the model, model group or deployment approved for that work.
marketing
Work the organisation defines as brand-facing
Route to the approved marketing model or model group
legal-review
Work the organisation defines as legal review
Route to the model and tool set approved for legal work
classified
Work the organisation defines as classified
Restrict to the approved self-hosted or air-gapped destination
The policy model is the same wherever ARC runs. What changes is where the handling executes: on the Self-hosted Licence it can run entirely inside your own environment before anything reaches an external provider, and a hosted deployment performs the same workflow inside a different trust boundary.
The Hosted Platform runs on a zero-access architecture. Queries and responses pass through the router in encrypted form, and FenxLabs does not access, read, inspect or decrypt query content.
What FenxLabs processes is the routing metadata a service needs to run and to bill: timestamps, model selections and token counts.
ARC does not retain or log request data beyond what you configure. On the Hosted Platform the router holds the operational metadata it needs to make a routing decision and to bill the call.
Your data is not used to train or fine-tune any model.
What crosses which boundary is decided in the design and written down before anything is deployed. We do not assume it.
On the Self-hosted Licence, ARC request handling runs inside infrastructure you control.
A request sent to an external model or tool leaves for that destination. ARC cannot make an external destination part of your private network.
ARC controls what each provider is sent. What a provider then retains or trains on is set by that endpoint and its terms, not by the router.
This supports your compliance position. It does not deliver compliance on its own, and any vendor who says otherwise is selling you a problem for later.
ARC governs how users, applications and agents access models, tools and approved data sources. It does not govern an agent's reasoning, planning, application logic, runtime or business accountability.
ARC is live in commercial deployments. What sits in the published column is checkable from this site today, and what sits beside it has to be asked for.
Ask for the security, reliability, operational and contractual evidence your evaluation needs. Material moves into the published column once it is approved and can be kept current.
No delivery dates. A date we miss costs more than no date.Bring a workload and a constraint. We will tell you whether routing changes anything for you.