What it is
A self-hosted generative AI platform for a company that cannot send its data to public AI services. Everything runs on the company's own GPU server: the models, the gateway, the vector store and the monitoring.
Teams and applications use one endpoint and one key, exactly as they would with a public API, so tools built for cloud AI work unchanged against the private platform.
What it does
- Serves open models for chat, document vision and OCR, and text embeddings, all behind a single OpenAI-compatible API.
- Keeps the models that must answer instantly resident in GPU memory, and loads larger models on demand, swapping them in and out automatically.
- Provides retrieval-augmented generation (RAG) over company documents with a vector database.
- Gates every browser-facing console behind the company's single sign-on, while programmatic clients use keys with per-team budgets and rate limits.
- Monitors the host, GPUs, containers, database and model servers, with alerts by email.
How it works
- A request arrives over TLS at the reverse proxy and is passed to the gateway.
- The gateway chooses the model backend by name, so clients never need to know where a model runs.
- Always-on models answer directly; an on-demand request starts the larger model and frees the GPU memory it needs.
- RAG queries embed the question, search the vector store and hand the matching passages to the chat model.
- Every component is a container with a defined boot order, so the whole stack can be rebuilt from its runbook.
Design choices
- One API for everything: decoupling clients from models made every later model change invisible to users.
- Always-on versus on-demand: a small set of models stays hot; everything else shares the remaining memory.
- Security at the edge: single sign-on is enforced by the proxy, not re-implemented in each tool.
- Documented for handover: build guide, component guide, operations and recovery runbooks, so the platform does not depend on one person.