Procurement leverage
When the model is a dropdown, you negotiate with vendors from strength — or route through Microsoft and AWS agreements you already hold.
Run agents on the AI providers you choose — with your own keys or ours — and make your SIS, CRM and proprietary systems agent-ready through hosted connectors and the open Model Context Protocol.
Connect a provider and the platform asks it which models it can actually serve — including your own Azure deployments and Bedrock custom models. IT then enables exactly the models each tenant may use, and builders pick only from that list.
| Provider | Chat | Embeddings | Notes |
|---|---|---|---|
| OpenAI | ✓ | ✓ | Custom base URL, organisation and project |
| Anthropic | ✓ | — | Native web search, web fetch and code execution tools |
| Amazon Bedrock | ✓ | ✓ | Foundation and custom models; reranking |
| Google Gemini | ✓ | ✓ | Live model discovery |
| Microsoft Foundry | ✓ | ✓ | Entra ID or API key; discovers OpenAI, Claude and DeepSeek deployments |
| OpenRouter | ✓ | ✓ | The OpenRouter catalogue |
| Custom | ✓ | ✓ | Any OpenAI-compatible endpoint, including self-hosted — gated by an origin allowlist |
Institutional AI shouldn’t be a one-way door. Neutrality is a procurement, resilience and governance decision — not a technical nicety.
When the model is a dropdown, you negotiate with vendors from strength — or route through Microsoft and AWS agreements you already hold.
Adopt a better or cheaper model by changing a setting. Prompts, knowledge, tools and workflows stay exactly where they are.
Institution-owned keys keep inference inside contracts you already signed — for example, Microsoft Foundry within your Microsoft tenancy.
Beyond chat and embeddings, the platform supports dedicated models for the steps where general-purpose models are a blunt instrument.
22+ built-in integrations today, each with an in-console setup guide — with more added all the time, and unlimited reach through MCP, webhooks and custom code.
New built-in integrations ship regularly — and the catalogue is never the limit. Anything with an API can be made agent-ready, with the same per-agent grants, guardrails and tracing.
Product names are trademarks of their respective owners and are used to identify supported integrations.
Gecko hosts production MCP servers for the systems universities run on, with security models built for an IT architect’s scrutiny.
Read and query Ethos resources — the integration layer in front of Banner and Colleague — through Ethos’s governed Proxy API, never SQL.
Connect production and sandbox orgs with OAuth, and let the hosted Salesforce MCP server act with each person’s own Salesforce permissions through per-user sign-in.
The whole student-engagement suite becomes agent-callable: 45 tools across contacts, calls, events, forms, campaigns, templates, users and files — plus read-only database queries.
MCP is the open standard for exposing tools to AI agents. Register any remote MCP server — yours, a vendor’s or one Gecko builds with you — and IT decides exactly which agents may use which tools.
Your SIS, your CRM and the system nobody else integrates with — all agent-ready through one open standard. Agents get tools one checkbox at a time.
Every provider ships with a numbered, deep-linked setup walkthrough — and credentials are handled the way your security team expects.
Step-by-step guides for every integration, with generated webhook and OAuth callback URLs to paste where they belong.
The console writes the complete Slack app manifest for you — paste it into Slack and go. Teams uses a guided Azure Bot registration.
Keys and secrets are AES-256-GCM encrypted at rest and never returned after save — not to the UI, not to the API, not to admins.
Bring your model agreements, SIS, CRM and the systems nobody else integrates with. We’ll map the fastest governed path to each.