OmniRoute is an AI gateway, aggregating 338 LLM providers including OpenAI, Anthropic Claude, Google Gemini, DeepSeek, Kimi, MiniMax, and GLM into a single OpenAI-compatible endpoint at localhost:20128. The gateway catalogs over 1,200 models across 90 free-tier providers and 40 free-forever providers, automatically rotating through tier-1, tier-2, and tier-3 fallback chains when any provider exhausts its quota or returns errors. RTK plus Caveman stacked token compression reduces eligible context by 15 to 95 percent before forwarding requests, cutting API costs dramatically without degrading output quality. OmniRoute exposes its full routing engine through a built-in MCP server with 104 tools across 31 scopes over stdio, HTTP, and SSE transports, plus an A2A protocol server with six autonomous agent skills and JSON-RPC 2.0 streaming. The gateway integrates directly with Claude Code, Cursor, GitHub Copilot, Codex CLI, OpenCode, and Cline through standard base-URL configuration. Seventeen routing strategies include latency-optimized, cost-minimized, and auto-scoring modes that evaluate candidates on success rate, context fit, model fitness, quota state, and circuit-breaker health. The Next.js dashboard provides real-time provider status, usage analytics, combo chain configuration, and model catalog browsing via a responsive PWA. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Preloop is a self-hostable control plane that governs every AI agent tool call and model call, and can run ticket-triggered agent work that returns as reviewable pull requests. An MCP firewall can allow, deny, or hold any tool call for approval, with require-justification rules written as YAML and CEL policy. Human approvals arrive on mobile, watch, Slack, Mattermost, email, webhook, or the command line, and agents can ask a person a question before continuing. The model gateway speaks OpenAI, Anthropic, and Gemini formats, applies budgets and allowed-model lists, and attributes token spend by model, agent, session, API key, flow, and user. Flows start agents from GitHub, GitLab, Bitbucket Cloud, Jira, webhooks, or CI jobs, in hosted containers or on private runners that connect over an outbound WebSocket. Twenty-one presets review pull requests, implement issues, triage tickets, scan for vulnerabilities, and collect evidence packs. Operators can steer a running agent from the console, phone, or watch with notes, then review the resulting pull request. One session timeline records tool calls, model calls, policy decisions, approvals, spend, outcomes, and synchronized recordings. Fleet Map shows people, devices, agents, models, and observed work in one view. An account kill switch blocks gateway and tool traffic and stops managed runs, with audited recovery. 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.

OpenMA lets you build and run AI agents with the model, harness, and sandbox you choose, on infrastructure you control, while it handles the sessions, execution, and recovery around them. Create an agent in the console, give it work, and come back later to the same session, because conversation history, streamed progress, and execution attempts are preserved rather than tied to one process that might die. Agents start with shell, file, web, and browser tools, then grow through MCP services and reusable Skills, while resources such as GitHub repositories, uploaded files, and shared memory attach to the work that needs them. Deployments run agents manually or on schedules you define, environments carry their own networking and package configuration, and model cards keep provider settings in one place instead of scattered environment files. If a sandbox fails, the session survives it; a replacement harness can rebuild context from durable events and workspace checkpoints. Operate everything through the console, the API, or the CLI, and plug in the database, queue, and object storage your deployment already trusts. 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.