OpenLLM serves any large language model as an OpenAI-compatible API endpoint from a single CLI command, handling model download, backend selection, quantization, and port binding automatically. It supports the full spectrum of popular models including Llama 3.3, Qwen2.5, DeepSeek, Mistral, and Phi3, choosing between vLLM and PyTorch inference backends based on hardware capabilities. When vLLM is available, continuous batching with PagedAttention achieves up to 23x throughput improvement over naive serving, while GPTQ and bitsandbytes quantization reduces memory requirements for GPU-constrained deployments. The server exposes a RESTful API on port 3000 with full OpenAI client library compatibility, enabling drop-in replacement for commercial providers in any application using the standard chat completions format. A built-in web chat UI at the /chat endpoint provides immediate interactive testing without external clients. Custom model repositories allow teams to maintain private catalogs of fine-tuned models alongside the default repository that tracks the latest releases. Deployment workflows generate production-ready Docker images automatically, with Kubernetes manifest support for orchestrated scaling. Native integration with LangChain and LlamaIndex supports RAG pipelines, Transformers Agents enables tool-calling workflows, and HuggingFace Hub handles model discovery. Server-Sent Events enable real-time token streaming across all API endpoints. Backed by BentoML's production ML infrastructure. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

One binary. A fleet of machines. One calm endpoint for inference. Paddler balances large language model traffic across whatever hardware you already own, instead of renting tokens by the million. The balancer exposes an inference service, a management service, and a web admin panel from a single self-contained program. Agents on separate machines generate tokens and embeddings through slots, each carrying its own context and KV cache. Inference runs on the built-in llama.cpp engine, CPU or GPU. Need a different model? Swap it dynamically, no rebuild, no redeploy. Capacity follows demand: agents join the fleet when traffic grows and leave when it fades, and request buffering holds early work in a queue so scaling up from zero hosts drops nothing. Operators watch fleet health through observability metrics, configure models, chat templates, and inference parameters in the admin panel, and test prompts graphically before users ever see a change. A desktop edition drafts office workstations into service beside the rack servers. For medical, financial, or otherwise sensitive prompts, everything stays inside your own network, and predictable hardware replaces per-token pricing exposure. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache License 2.0 licensed.

Your inference server should not sit mostly idle while a model crawls along at ten tokens per second, so ReadyLLM gives you a visual way to deploy, watch, and tune LLMs until the hardware is actually earning its keep. Add the machine under your desk or a remote box over SSH, let hardware detection read its GPU, VRAM, CPU, and memory, and get model recommendations that fit what you own instead of wishful downloads. A model store catalogs text, image, and video models with parameter counts, precision, resolutions, and real weight filenames, background downloads from multiple sources, and integrity checks when they land. One click starts or stops llama.cpp, vLLM, or SGLang services, installs a missing engine matched to your GPU backend, and leaves runtime parameters open for manual tweaks. Live curves track GPU utilization, memory, throughput, and latency as requests flow. When speed disappoints, two-phase auto tuning searches the knobs that matter, checks VRAM feasibility before it wastes your time, and benchmarks honestly against latency, throughput, or prefill goals; an AI tuning mode can reason through the same loop across several rounds. Beyond chat models, ComfyUI generation covers text-to-image and text-to-video, storyboards, shot-by-shot long video, and upscaling, with prompts optionally expanded first. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 48,000 GitHub stars and monthly releases since March 2023, LocalAI is the self-hosted AI engine that replaces every OpenAI endpoint with a single Docker container running on your own infrastructure — serving chat completions, image generation, text-to-speech, speech-to-text, embeddings, vision, video generation, and function calling through identical API schemas that require zero application code changes. The composable backend architecture isolates each inference engine as a separate gRPC service running in its own OCI container, so llama.cpp, vLLM, SGLang, transformers, whisper.cpp, diffusers, MLX, Stable Diffusion, and Flux install on demand without touching the core, can run on separate machines, and a fault in one never affects others. Hardware acceleration spans NVIDIA CUDA 12 and 13, AMD ROCm, Intel oneAPI/SYCL, Apple Silicon Metal, Vulkan, and NVIDIA Jetson L4T — or runs entirely on CPU without any GPU. Built-in AI agents support autonomous tool use, retrieval-augmented generation, Model Context Protocol integration, and skill-based workflows directly in the web interface. The model gallery provides curated YAML configuration files for hundreds of models that install with a single command, while P2P federated inference distributes model shards across multiple machines for running models larger than any single node's memory. Multi-user API key authentication with quotas and role-based access enables team deployments. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Imp runs large AI chat models privately on one NVIDIA RTX 50 or RTX PRO graphics card, exposing them through OpenAI and Anthropic compatible APIs plus a built-in browser chat. Start it with a single Docker command, point it at a model, and the chat opens in your browser with saved conversations and a live readout of generation speed. Coding agents such as Claude Code and Codex connect by changing one base URL, so your editor talks to the model on your own hardware instead of a rented cloud endpoint. Tool calls, structured JSON output, streaming responses, and reasoning models all work over the wire, and requests can be protected with an API key, per-IP rate limits, and concurrency caps. Load GGUF files you already have or NVFP4 and FP8 SafeTensors checkpoints straight from Hugging Face with no conversion step before the first answer. When a model is bigger than the card, mixture-of-experts weights stay in system RAM while the busiest experts are cached on the GPU, so a 123.6 GiB model still answers from a 32 GB card. Supported models can also read images alongside text, and tokenize, health, and model listing endpoints make the server easy to wire into scripts and monitors. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Ollaya serves decision models that answer typed questions about a message, ticket, or document with calibrated probabilities, through a self-hosted API shaped like the hosted service it can replace. Send a state, which can be an email, a support ticket, or any JSON, plus typed choice, score, and yes or no questions, and the model answers in one forward pass in milliseconds without generating text. Pull models by name the way Ollama users already know, with run, list, ps, show, copy, and remove commands managing the local store. Downloads verify every layer against its sha256 digest, resume when interrupted, and share blobs between models so storage stays lean. Existing TypeSafe code keeps working by changing one environment variable, because the /v1/systemone and /v1/decisions endpoints are wire-identical and the official SDK sends its key the same way. The native /api adds routing information and timings, model loading and unloading, and streamed pull progress for your own tooling. Put it to work triaging inboxes, routing requests to the right model or team, screening prompts for injection and jailbreak attempts, or replacing per-token LLM classification calls with a local answer. Agents reach the same engine through the bundled MCP server, and LiteLLM, LangChain, DSPy, LlamaIndex, n8n, and Dify connect through their existing integrations. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Running local models usually means choosing between a polished app that hides the engine and a terminal full of flags you half remember. LlamaForge refuses the trade: it installs and drives the official llama.cpp release itself, then puts a browser panel over all of it, every one of the 200-plus llama-server flags your build supports, grouped, searchable and editable per model. Before you load anything, each model is drawn into your GPUs at its real footprint, so the out-of-memory surprise happens on screen instead of in a crashed server; before you download anything, every quant on Hugging Face gets a fit rating for your VRAM, FITS, TIGHT or CPU OFFLOAD. Auto-Forge then measures placements, KV cache types and speculative drafters on your own hardware and keeps the fastest configuration, checking that a drafter still produces identical tokens before applying it with one click, and undoing it with one click. Keep several models loaded at once and a planner places each on the GPUs that fit it; when a game launches, Game Mode unloads your models and brings them back when you quit. Chat in llama.cpp's own interface, join from your phone by QR code, duel two models blind in the Arena under an Elo board, and let Embers, small local agents, keep a wiki and write scheduled briefs counting only facts they can quote verbatim. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

One endpoint for every inference box you own: Olla is a proxy and load balancer that fronts your self-hosted LLM backends and routes each request to a healthy node. Your apps keep calling a single OpenAI-compatible address on port 40114, and Olla picks the backend by priority, response rate, and live health. When a node drops, requests retry on the next endpoint automatically and the failed node rejoins after recovery, with circuit breakers keeping bad nodes out of rotation. Multi-turn conversations stick to one backend so its KV cache stays warm across the chat. Model lists from every provider merge into one catalogue, and the same model served by several nodes appears once, ready to route anywhere. Backends with native Anthropic support receive Messages API calls untouched, and other backends get automatic translation, so Claude Code and similar tools can drive your local models. Text embeddings and rerank requests route to the host that serves them, and outbound authentication covers backends that expect API keys. The embedded Herd Dashboard shows fleet health, per-endpoint latency, and the discovered model inventory from the binary itself. The whole proxy runs in under 50 MB of RAM. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Inference Gateway puts a single OpenAI-compatible API endpoint in front of OpenAI, Anthropic, Groq, Cohere, Ollama, DeepSeek, Google, Mistral, MiniMax, Moonshot, Nvidia, and llama.cpp, so your application code never changes when you switch models or providers. The Go binary starts on port 8080 and normalizes authentication, streaming protocols, and response formats across all backends transparently. Native Model Context Protocol support auto-discovers tools from connected MCP servers and injects them into LLM requests without client-side management, enabling server-side tool execution across any provider that supports function calling. Agent-to-Agent protocol integration allows distributed agent communication through a declarative Agent Definition Language that generates production-ready Go or Rust servers from a single YAML manifest. The dedicated Kubernetes Operator manages Gateway, Agent, MCP, and Orchestrator custom resources with automatic HPA scaling, OIDC authentication, and service discovery that rebuilds MCP configurations when the discovered server set changes. Prometheus metrics and OpenTelemetry tracing provide full request-level observability across the entire inference pipeline. Middleware controls enable per-request provider selection, model routing, and fallback strategies. Official SDKs in Go, Python, TypeScript, and Rust provide typed client interfaces with streaming support. Docker Compose deployment requires only environment variables for API keys. A CNCF Sandbox applicant. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

FreeLLMAPI collapses the chaos of 29 free LLM providers — Google AI, Cerebras, Groq, Mistral, OpenRouter, GitHub Models, Cohere, Cloudflare Workers AI, NVIDIA NIM, HuggingFace, SiliconFlow, Reka, Z.ai, and more — into a single /v1 endpoint that speaks both OpenAI and Anthropic protocols. The smart router selects the best available model for each request, automatically fails over to the next provider when rate limits hit, and tracks per-key token consumption so you never exceed a free-tier cap. Keys are stored with AES-256-GCM encryption and clients authenticate using a single unified bearer token, never exposing upstream provider credentials to downstream applications. The catalog tracks 251 model families across 358 provider/model endpoints with approximately 4 billion tokens per month of aggregate free-tier capacity, auto-refreshing from a signed manifest at freellmapi.co twice daily without requiring git pulls. Beyond chat completions, the proxy handles embedding, image generation, and audio/TTS endpoints, plus structured outputs with JSON schema forwarding, JSON healing, and format-ignore failover. An integrated MCP server at /mcp provides gateway introspection for coding agents, while the self-hosted OpenAPI reference at /v1/docs documents every route. Compatible with OpenAI SDKs, LangChain, LlamaIndex, Continue, Claude Code, and Hermes — just change base_url. Deploy via Docker, npm, or build from source. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

One endpoint, every model you run, and a government-grade paper trail for each request. OpenGateLLM sits in front of your AI infrastructure as the single door: applications call one OpenAI-compatible API, and the gateway decides which backend answers, a self-hosted vLLM cluster, an Ollama box in the corner, a Hugging Face TEI embeddings service, or a hosted provider when you allow one. You publish friendly model names as routers and attach real provider APIs behind them, then load-balance across those backends by shuffle or least-busy so a second GPU node starts earning its keep the moment you register it. Chat completions, embeddings, reranking, OCR, and audio transcription each get their standard endpoint, so existing OpenAI SDK code, LangChain, and LlamaIndex projects point at a new base URL and keep working. Governance is built in rather than bolted on: organizations, users, and roles control who may call which model, API keys authenticate every request, and rate limiting keeps one enthusiastic team from eating the whole cluster. Usage monitoring follows every inference, and carbon footprint estimates attach to models through their hosting zone and parameter counts. Retrieval-augmented generation against Elasticsearch or Qdrant plugs into the same surface. No chat history is stored, which is rather the point when the data is yours. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Backed by 56,000+ GitHub stars and over 240 million Docker pulls, LiteLLM delivers the open-source AI gateway trusted by Netflix, Lemonade, Rocket Money, and thousands of engineering teams to route every LLM request through one unified API. The Rust-core gateway adds sub-millisecond overhead per request with 8ms P95 latency at 1,000 RPS, 15x throughput improvement and 11x lower memory footprint compared to Python-only proxies. A single OpenAI-compatible endpoint connects to 100+ providers and 1,800+ models spanning OpenAI, Anthropic, Google Gemini, AWS Bedrock, Azure OpenAI, Vertex AI, Hugging Face, vLLM, Nvidia NIM, Ollama, and Mistral with day-zero support for new model releases. The Auto Router V2 classifies request complexity across four tiers using rule-based scoring, semantic keyword matching, and adaptive Thompson sampling to route each request to the most cost-effective model without API calls or training data. Virtual API keys enable multi-tenant governance with per-team, per-user, and per-project cost tracking, budget caps with automatic fallback rerouting, and role-based access control. Built-in guardrails provide PII masking, prompt injection detection, and model-graded evaluation before requests reach providers. The Agent Gateway extends routing from model calls to agent workflows with MCP server integration. Observability integrates with Langfuse, Arize Phoenix, OpenTelemetry, and MLflow for complete request tracing. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Instead of scattering provider credentials and vendor-specific SDK logic across dozens of microservices, engineering teams route every LLM call through GoModel, an open-source AI gateway that unifies 34 model providers behind OpenAI-compatible and Anthropic-compatible endpoints. Pointing existing OpenAI or Anthropic SDKs at the gateway unlocks chat completions, the Responses API, Anthropic Messages, embeddings, batch jobs, and realtime audio across OpenAI, Anthropic, Gemini, Bedrock, Azure, Groq, DeepSeek, Ollama, and vLLM. Platform operators publish virtual model aliases that distribute traffic via weighted round-robin or lowest-cost routing while rotating multiple API keys per provider and failing over through circuit breakers during upstream outages. Sticky session routing keeps multi-turn agent conversations on the same target to preserve warm prompt caches, while exact-match and vector semantic caching via Qdrant, pgvector, Pinecone, or Weaviate cut duplicate token costs. Versioned workflows and pre-dispatch guardrails enforce prompt injection rules, rate limits, and hard USD spend budgets across hierarchical tenant user paths before requests are dispatched. The built-in admin dashboard offers live audit logs, per-tenant cost analytics, LiteLLM key migration, an interactive request playground, Model Context Protocol tool aggregation, and OpenTelemetry and Prometheus metrics. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Routerly is the one front door for every AI model your apps use: point your OpenAI or Anthropic client at it, and it chooses the right model for each request, enforces your budget, and keeps the receipts. Nothing in your code changes except the base URL, and from that moment streaming chat completions and messages flow to OpenAI, Anthropic, Gemini, Mistral, Cohere, xAI or your own Ollama models behind a single token. Nine routing policies score every candidate in parallel: cheapest, fastest, healthiest, most capable, biggest context, least rate-limited, fairest, most budget left, and one that asks a small model to judge which model fits the task. When the winner errors or times out, the next candidate takes over automatically, and the recorded routing trace shows exactly why each model won or lost. Guardrails can block or log content that breaks your rules, and phone numbers, card numbers, SSNs, IBANs and emails can be scrubbed out before anything reaches a provider. Every call is logged with tokens, USD cost and latency, and hard limits per model, project and token reject overspending requests before a provider can charge for them. Projects keep separate tokens, model lists and budgets for each team or tool, role-based permissions decide who may change what, and alerts land in Slack, email, webhooks or PagerDuty when budgets or providers misbehave. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

One OpenAI-compatible endpoint, 1,600+ models behind it: Portkey Gateway sits between your app and every major LLM provider, deciding in real time where each request should go. When a provider times out or returns errors, automatic retries with exponential backoff kick in, and fallback rules quietly move traffic to your second-choice model before users notice anything. Load balancing spreads calls across multiple API keys and providers by weight, conditional routing sends each request down a different path based on its content or metadata, and per-request timeouts cut off providers that hang. Guardrails inspect inputs and outputs as traffic passes through: block banned words, screen for sensitive content, and enforce the checks your compliance team asked for, with dozens of pre-built rules ready to attach. Text is only the start: the same API shape reaches vision models, speech-to-text, text-to-speech, image generation, and realtime websocket APIs, so multimodal features stop multiplying your integration work. Routing policies live in JSON configs you attach per request or per client, which means experiments, cost controls, and provider migrations ship as configuration changes, not redeploys. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

New API is a Go-powered LLM gateway that funnels over 40 AI providers, from OpenAI and Anthropic to Google Gemini, Azure, AWS Bedrock, DeepSeek, and Mistral, through a single OpenAI-compatible endpoint with intelligent routing and enterprise cost controls. Bidirectional format conversion translates between OpenAI Chat Completions, Claude Messages, and Gemini GenerateContent APIs transparently, so clients call any provider using their preferred format while the gateway handles the rest. Routing logic supports weighted random channel selection, priority-based failover, and automatic retry on provider errors to maximize uptime. The React admin dashboard shows usage charts, token consumption tracking, per-model cost breakdowns, and real-time request monitoring. Multi-tenant architecture includes three role levels, token-based authentication, per-user quota management, and a three-phase billing system with tiered pricing via a custom expression language. Multimodal support covers text completion, vision, embeddings, text-to-speech, speech-to-text, image generation, and creative task providers like Midjourney-Proxy and Suno-API. The interface ships in five languages including English, Chinese, Japanese, and French. Docker deployment runs with SQLite or MySQL for persistence. 45,000+ GitHub stars. AGPL-3.0 licensed.