Four things separate a control plane from a gateway, a cloud AI stack or an internal build: your network boundary, your existing models, your data, and where the fee is taken.
Where FenxARC™ runs, what it can reach and how FenxLabs is paid are decided differently by each approach. Check all four against your own shortlist.
ARC request handling runs inside your VPC, on your own hardware, or fully air-gapped. Internal routes can remain inside your network; an approved external route still receives the context it needs.
Self-hosted Licence. The Hosted Platform runs on FenxLabs infrastructure.Fraud scoring, demand forecasting, document classification. The machine learning and deep learning models you already run become routing destinations alongside your language models.
Self-hosted Licence.Connect vector storage directly to the router. It sits between the models and the data, and a model reaches only what it has permission to see.
Self-hosted Licence.Inference stays a direct relationship between you and your providers, at their rates. We take no margin on it.
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.Three of these four belong to the Self-hosted Licence. Where ARC runs is one decision and what it enforces is another.
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.
Applications keep their workflows. Providers keep serving inference. ARC evaluates each governed request against the active list, applies your eligibility and privacy rules, then ranks whatever survives them.
A list groups the models, tools and rules approved for a team or use case.
See how a request is handledWhat separates them is where the governing rule lives, and who is on the hook for keeping it right.
Eligibility runs before ranking, so nothing in the ordering step can reach a destination the policy excluded.
These separate an operating approach from a feature list. Put them to every option on the shortlist, ARC included.
One provider, one model and application-level controls may cover everything you can foresee. A second control layer would then be cost without a return.
ARC is built for the case where workload categories, model choice, privacy handling, access policy and deployment boundaries have to change across teams without rewriting each workload.
Bring a workload and a constraint. We will tell you whether routing changes anything for you.