ARC
Pricing
Discord
Talk to an engineerStart free
Start free
ARCby FenxLabsCollective Intelligence

Platform

  • How it works
  • Custom routing and governance
  • Use cases
  • Example architectures

Deployment

  • Hosted Platform
  • Managed Service
  • Self-hosted Licence
  • For ISVs
  • Open the portal

Services

  • Assessment and planning
  • Architecture and integration
  • Model Adaptation
  • EU AI Act readiness
  • Managed Service operations

Resources

  • Cost modeller
  • Compare approaches
  • Pricing
  • FAQ
  • Transparency
  • Get started
  • Discord community

Legal

  • Privacy notice
  • Terms and conditions
  • Sub-processors
  • Accessibility

For individuals

  • FenxChat

FenxLabs. KvK 91762782.

Herengracht 320, 1016 CE Amsterdam, Netherlands

+31 85 060 5273contact@fenxlabs.ai

© 2026 FenxLabs. All rights reserved.

Managed Service

Run governed AI without running the environment

FenxLabs operates the agreed FenxARC™ and model environment inside your infrastructure or hosts it for you, so your people, applications and agents gain governed access without a full internal operations team.

Discuss your requirementsChoose where ARC runs

Scoped and quoted per engagement. Boundaries, responsibilities and handover are agreed before operations begin.

Choose where FenxLabs operates

Use your infrastructure or a FenxLabs-hosted environment. In both patterns, FenxLabs operates only the responsibilities agreed for the engagement.

Illustrative scenario

Inside your environment

Your infrastructure

Placement

Agreed FenxLabs operating boundary

ARC
Routing operations
Agreed model environment

Hosted for you

FenxLabs-hosted infrastructure

Placement

Agreed FenxLabs operating boundary

ARC
Routing operations
Agreed model environment
You retain
ModelsDataRouting intentBusiness accountability

Boxes show operational responsibility, not ownership.

Final placement, access, request-data boundaries and responsibilities are documented during design.Operating boundary

Request-data boundary

What crosses which boundary is decided in the design and written down before anything is deployed. We do not assume it.

Where ARC runs
Your environment, or FenxLabs-hosted for you
Who operates ARC
FenxLabs
Who manages the infrastructure
FenxLabs within the agreed operating boundary
Customer operating effort
Low. FenxLabs owns the agreed day-to-day operations

Decide what FenxLabs takes on

The service can cover ARC and routing operations, training and inference operations, model updates, endpoints, providers, incidents, optimisation and reporting.

FenxLabs can operate

  • ARC and routing policy day to day
  • Agreed model training and inference systems
  • Model updates, endpoints and providers
  • Monitoring, incident response, optimisation and reporting

You retain

  • Your models
  • Your data
  • Your routing intent
  • Your business accountability

FenxLabs owns only the operational responsibilities agreed for the engagement. Handover terms are agreed before operations begin, so your team can take over the documented environment.

See Managed Service operations

Choose this service when

The Managed Service fits when operating responsibility matters as much as where ARC runs.

  • You want FenxLabs to own agreed day-to-day AI operations
  • Placement, access boundaries and retained responsibilities need to fit your environment
  • Your team wants governed AI without building the full internal operating function

Need hosted ARC only?

Choose the Hosted Platform when FenxLabs should host ARC but your team will operate the connected model environment.

Start on the Hosted Platform

Ready to operate it yourself?

Choose the Self-hosted Licence when your team can deploy, maintain and operate ARC and the wider model environment.

Explore the Self-hosted Licence

Define the boundary before FenxLabs operates

Thirty minutes with an engineer. Your numbers. A straight answer.

Discuss your requirementsChoose where ARC runs