Zoltraak Gateway has three client surfaces. Each is a distinct integration pattern with different expectations and communication styles.
OpenWebUI is the primary user interface for conversations, image viewing, and model interaction. It communicates with the gateway via the Ollama-compatible REST API. From OpenWebUI's perspective the gateway is an Ollama instance. It has no awareness of GPU lifecycle management. All pod warmup, queuing, and routing is transparent to it. OpenWebUI handles conversation history, file storage, and user sessions independently. It is not a managed component of the gateway.
Connection: OpenWebUI settings point the Ollama base URL at the gateway address and port rather than a real Ollama instance.
The Telegram bot is the conversational operational interface for managing the gateway. Users interact in plain English rather than rigid commands. The bot understands natural language questions and instructions such as "is the pod running", "how much have I spent today", or "shut it down". Intent is classified by a small lightweight model running in the local Ollama instance on the home server. This means the bot works and responds intelligently even when the GPU pod is completely off.
Telegram delivers messages to the gateway via a webhook POST to a configured endpoint. The gateway classifies intent via local Ollama, executes the appropriate internal service call, and replies via the Telegram Bot API. Long running operations receive an immediate acknowledgement followed by a result message when processing completes.
Connection: Telegram webhook configured to POST to https://your-gateway/api/v1/bot/telegram
The intent classifier is designed as an interface with the below implementation:
IntentClassifierPort
|-- LlmIntentClassifier local Ollama on home server
Any HTTP client including curl, Postman, or a future mobile or web application can interact with the gateway directly via its REST API. All endpoints require a JWT Bearer token except the health endpoint. This surface is the intended integration point for future applications that consume fantasy mode, coding assistant, or other gateway features directly.
Connection: Standard HTTPS REST with Authorization Bearer header.