Define which models, tools and approved data sources each user, application or agent may reach. FenxARC™ applies your privacy, usage, routing and spending policy before it ranks a route.
Free tier on the Hosted Platform. No card required.
A list groups the models, tools and rules approved for a team or use case. It defines what users, applications, workspaces and agents may reach before a request is classified or ranked.
Assign users, teams, applications, workspaces, agents or use cases to the boundary designed for their work.
Choose the models, model groups, tools and data sources they are permitted to use.
Apply privacy, usage, budget and routing rules before each request runs. Cost can reorder approved routes but never relax access, privacy or capability.
Define the kinds of work your organisation recognises. ARC identifies when each category applies, then gives the request the right resources, handling and routing policy.
As priorities change, update the category, matching logic or destination centrally. Applications continue using the same ARC integration.
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.
At the model-routing level, the policy applies to everything your organisation sends through ARC.
On a list, the policy applies to that team or use case, so work that is more sensitive can be governed more tightly than the organisation as a whole.
A cost objective reorders routes that already meet your privacy policy. It cannot reach one that does not.
Categories you define yourself, written as plain-text rules describing what counts and what does not.
A test bench sits beside the rules. Run sample requests through a category and see how it classifies before it touches live traffic.
A rule you write is evaluated from the day you write it, and whether it changes a routing decision is a separate switch. Watch it against real traffic before you let it enforce anything.
Where ARC runs changes where handling executes, not which policy model you set. On the Self-hosted Licence, handling can run inside your environment before any external provider receives anything. Hosted ARC performs the same workflow inside a different trust boundary.
Start free with one OpenAI-compatible integration. Talk to an engineer if access policy, data boundaries or deployment need to be settled first.