Section 1: Why an Organisation Needs a GenAI Gateway
- What goes wrong when everyone uses AI their own way: shadow AI, scattered keys and invisible costs
- The gateway's role: one place for access, cost, policy and logs
- A reference architecture for an in-house AI platform, from users to models
- An overview of open source tools and cloud gateway services to inform the decision
- Workshop: map your organisation's current AI use and its risk points
Section 2: Workshop: Data Classification and Model Policy
- Classify data, for example public, internal, confidential and personal data
- Match each data class to permitted models: enterprise cloud APIs or in-house models
- Read AI providers' data terms on retention and use for training
- PDPA considerations when sending personal data for processing
- Workshop: draft a policy table of which data may be used with which model
Section 3: Lab: Installing LiteLLM, Routing and Fallbacks
- Install LiteLLM with PostgreSQL and Redis using Docker Compose
- Define the model list in config.yaml, combining cloud APIs and in-house models through Ollama under organisation-wide names
- Call every model through one OpenAI-compatible endpoint and keep provider API keys as secrets
- Load balancing, fallbacks, retries and timeouts when a provider is down or over quota
- Routing by data class, and caching with Redis to cut cost
- Lab: switch off one provider and test that the system fails over to the backup
Section 4: Lab: Virtual Keys, Teams and Budgets
- Issue virtual keys to users, teams and apps instead of handing out real provider keys
- Restrict which models each team can call according to data policy
- Set budgets, rate limits and key expiry dates
- Admin roles in LiteLLM and the features that need an enterprise licence
- Lab: simulate a team going over budget and see how the system responds
Section 5: Lab: An Organisation Chat Interface with Open WebUI
- Install Open WebUI and connect it to LiteLLM rather than directly to providers
- Connect SSO through OIDC, with an overview of LDAP or Active Directory integration
- Group users and set access to models, features and knowledge by department
- Create model presets with system prompts for each team's work
- The Open WebUI licence and branding terms to know before using it in an organisation