Compatibility
Does it work with Azure OpenAI and Microsoft Copilot?
Yes for Azure OpenAI Service, Vidai sits in front of it like any other provider, with the same identity, routing and guardrails. Microsoft 365 Copilot itself (the in-app assistant) has no API and is licensed per user by Microsoft, so no gateway can sit in front of it; teams that want Copilot-class models programmatically use Azure OpenAI, which we fully support. Custom Copilot Studio agents can be integrated on request.
Which AI providers does Vidai support?
OpenAI, Anthropic, Azure OpenAI, Amazon Bedrock, Google Vertex and Gemini, and the Google ADK. Adding or switching a provider is a configuration change, not a rebuild.
Do we have to rewrite our code to OpenAI format like other gateways?
No, and this is a real difference. Most gateways only accept the OpenAI dialect, so an app built on the Anthropic SDK or Google ADK has to be rewritten to use them. Vidai translates in both directions: your code keeps speaking the Anthropic SDK, Google ADK or Gemini natively, and we convert to and from whatever the target model speaks. The change is a one-line endpoint update, not a refactor.
Can different teams use different SDKs through one Vidai?
Yes. One team can stay on the Anthropic SDK, another on the Google ADK, another on OpenAI, all through the same Vidai, each in its own native dialect. Vidai is the common layer underneath, not a lowest-common-denominator everyone has to adopt.
Does it work with LangChain, LlamaIndex and agent frameworks?
Yes. Common orchestration and agent frameworks work through Vidai unchanged, including LangChain, LangGraph and the Google ADK.
Deployment & security
Where does Vidai run?
Inside your own network, your cloud account, your data centre, or fully air-gapped. It is not a hosted service your traffic passes through.
Does it send any data back to Vidai?
No. There is no telemetry, no usage callback and no outbound beacon. It does not phone home, and you can verify that on the wire.
Can it run in an air-gapped environment?
Yes. No outbound connectivity is required to operate, so it can be deployed where there is no internet access at all.
Does it integrate with our SSO and identity model?
Enterprise identity is something we handle per deployment. Contact us to discuss SSO and your identity integration directly.
How big is it to deploy?
The part that sits in your AI traffic is a single small binary. The dashboard and management layer run separately. There is no large platform to stand up.
Commercial
How is Vidai priced?
A flat licence. There are no per-request fees and no usage markup, so the bill doesn't grow just because your traffic did. See the Pricing page for the tiers.
Is Vidai open source?
Vidai, the control plane, is a commercial product. Vidai.Mock, the LLM mock server for CI, is open source.
Is there a free or community edition?
Yes. The Community edition is the full self-hosted control plane, free, no expiry. Sign in at portal.vidai.uk to generate your licence and download the latest release from github.com/vidaiUK/vidai-quickstart. Commercial use is by approval, granted case-by-case. Start at /community.
Do you offer a trial or proof of concept?
Yes. Most engagements start with a short walkthrough on a deployment that looks like yours. Talk to us and we'll scope it.
Working with us
Do you help us deploy it?
Yes. Our services team handles deployment, policy and cost setup, and can build custom guardrail models or migrate a legacy stack. Every engagement ends with something you own and run.
Where are you based?
Glasgow, UK. The team's production experience spans operators like Amazon, GE and Tata.
How do we start?
Request a demo, or start with a Sovereignty & Cost Audit to see where you stand. No procurement process to begin a conversation.
Still have a question.
The fastest answer is a 20-minute conversation, on a real deployment.