One gateway, every AI model: APIPark gives your applications a single, consistent API for OpenAI, Anthropic, Google Gemini, DeepSeek, and 100+ other models, and gives your team a portal to publish and share whatever gets built on top. Standardized request and response formats mean swapping a provider or rewriting a prompt never touches client code. Pair a model with a prompt template and it becomes a ready-made API for sentiment analysis or translation, listed in the developer portal with its own readme and generated API docs. Model Fallback swaps in the highest-priority available model when one misbehaves. API key balancing spreads traffic across several keys for the same provider. Already have REST services? Import an OpenAPI document, file the service under a category and tags, and let consumers subscribe, with optional manual review before anyone gets access. Any service can be switched on as an MCP tool that AI assistants can discover and call, and local open-source models can be deployed and exposed the same way. Usage charts follow requests, traffic, and tokens per service and consumer. Request logs flow out to files, HTTP endpoints, Kafka, NSQ, or Syslog. 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.

Fusio turns the data and services you already run into a managed API that partners, apps, and AI agents can actually use. The workflow starts small: add a database connection and a table becomes a REST endpoint, or proxy a remote service and route traffic between internal microservices. Each operation pairs an HTTP path with an action and a schema, so requests are validated and an OpenAPI specification plus client SDKs for major languages come out without extra effort. Custom behavior lives in reusable actions, and an AI assistant can draft actions and schemas from a plain-language prompt. Native Model Context Protocol support then offers those actions to autonomous agents as tools. Third-party developers get a self-service portal with documentation, testing tools, and their own keys. Every endpoint can be protected with scopes and rate limits. Asynchronous work runs through events, webhooks, cronjobs, and triggers. When the API becomes a product, plans, quotas, and transactions handle billing, and analytics follow usage, performance, and errors. A marketplace installs ready-made actions and apps, and the generator and test panels speed up development. 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.

Doorman puts one controlled front door in front of every API you run, instead of teaching each service to reinvent keys, quotas, and abuse protection. It routes REST, SOAP, GraphQL, gRPC, gRPC-Web, and AI traffic through a single gateway while its control plane handles the surrounding work. Catalog APIs in a visual builder, configure protocols and endpoints, validate schemas, and manage semantic versions with deprecation and sunset dates as interfaces evolve. Control who may call what through users, roles, groups, and subscriptions, then attach credit tiers and quotas so heavy consumers stay inside the plan you sold them. Slow abusive clients with rate limits, throttling, and bandwidth caps, and keep flaky upstreams from cascading through retries and circuit breaking. Follow every request in searchable logs, review security controls and audit activity, and move configuration between environments with import and export. Start in a self-contained in-memory mode for a small deployment, then switch to shared MongoDB and Redis when several gateway instances need the same counters, revocations, and routing state. 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 endpoint for every MCP server you run: MCPHub gathers local and remote Model Context Protocol servers behind stable URLs, so AI clients connect once and see what you allow. Claude Code, Cursor, and Cherry Studio can use four routes: everything at /mcp, a named group at /mcp/{group}, one server at /mcp/{server}, or semantic tool search at /mcp/$smart. Smart routing runs vector search on PostgreSQL with pgvector and an OpenAI-compatible key, so the model gets a shorter tool list. Servers attach over stdio, SSE, or streamable HTTP, OpenAPI services can be wrapped as MCP tools, and changes apply without downtime. In the other direction, MCP tools can be exported as an OpenAPI 3.0.3 spec for OpenWebUI and other OpenAPI clients. Bearer keys, OAuth 2.0 (client and server modes), and GitHub or Google sign-in in database mode control access, with per-user visibility for servers and groups. Encrypted per-user credentials let one shared server use each person's own key. Logs show tool-call activity, request status, and latency, health checks track each connection, and the dashboard controls which tools, prompts, and resources each server exposes. Large text tool results can be compressed, interactive MCP Apps are proxied through MCPHub routes, and a built-in market lets you browse a server catalog. Typical uses include a team-wide gateway, per-project groups, and direct single-server routes for debugging. 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.

With 2,600+ GitHub stars, MetaMCP solves the MCP server sprawl problem by aggregating any number of upstream servers into a single authenticated endpoint that any MCP client connects to once. Group servers into namespaces — development tools in one, data sources in another — then publish each namespace as its own SSE, Streamable HTTP, or OpenAPI endpoint with API-key authentication in headers or query parameters, or full OAuth per the MCP Spec 2025-06-18 standard. The aggregation engine discovers tools, resources, and prompts from all active servers in parallel, prefixes tool names with server identifiers to prevent collisions, and applies configurable middleware including tool filtering to reduce context-window bloat and description overrides to improve LLM comprehension. The web management UI lets you configure MCP servers with stdio, SSE, or Streamable HTTP transports, toggle servers active or inactive per namespace, create and revoke API keys per endpoint, and inspect discovered tools with their schemas. Nested MetaMCP support enables hierarchical architectures where one MetaMCP instance consumes another, creating multi-level tool organization with automatic name resolution. Compatible with Claude Desktop, Claude Code, Cursor, Open WebUI, and any MCP-compatible client through a single connection URL. The Docker container packages the TypeScript backend with PostgreSQL for configuration persistence, exposing the management UI on port 12005 and MCP endpoints on configurable ports. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Connecting autonomous AI assistants to internal enterprise databases and legacy systems is streamlined by AnythingMCP, a visual Model Context Protocol gateway with automated knowledge graph generation and granular access controls. Engineers can import OpenAPI specifications, Postman collections, SOAP WSDL files, or raw database credentials to generate standardized Model Context Protocol tools in minutes without writing custom code. The built-in knowledge graph automatically maps entity relationships across disparate databases and software platforms, teaching agents how to correlate customer records in CRM tools with live order histories in enterprise resource planning software. System administrators can enforce fine-grained access policies by restricting tool execution permissions to specific roles and scoping database operations to read-only queries with strict row limits. An interactive web console provides real-time tool inspection, payload testing, request tracing, and comprehensive audit logs that capture every upstream invocation with full parameter visibility. Enterprise teams can integrate identity providers through OAuth2, SAML single sign-on, and SCIM automated user provisioning while protecting sensitive credentials using AES-256-GCM encryption at rest. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GNU AGPLv3 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.

Webhooks, cron schedules, and app events trigger chains of nodes that fetch, transform, and route data: n8n is a workflow automation platform built around a visual, node-based editor. It ships with 400+ built-in integrations covering databases like Postgres, SaaS tools like Slack and HubSpot, and every major AI provider. When a pre-built node does not exist, the HTTP Request node calls any REST API, and the Code node runs JavaScript or Python inline, so you are never blocked by a missing connector. Workflows execute as directed graphs with branching, loops, error handling, and sub-workflows, and every run is logged for inspection and replay during debugging. It also includes LangChain-based nodes for building AI agents with tool calling and memory. Self-hosting on RepoCloud gives you unlimited workflow executions with no per-task pricing, and all data stays on your instance. Runs on Node.js with SQLite by default; add Postgres and Redis queue mode when you need to scale workers horizontally.

Zapier's job, on your own server: Activepieces is an open-source workflow automation platform built to be exactly that replacement. Flows are built in a visual no-code editor with triggers, actions, loops, conditional branches, auto-retries, raw HTTP steps, and code steps that run JavaScript or TypeScript with full npm package support. Integrations are "pieces" - type-safe TypeScript npm packages with hot reloading for local development - and the catalog spans 600+ services, with the large majority contributed by the community. The platform is AI-first in two directions: native AI pieces call OpenAI, Anthropic, Google, and Azure models inside flows, and every piece automatically doubles as an MCP server, so assistants like Claude Desktop and Cursor can invoke your integrations and workflows through natural language. A built-in MCP server also exposes 30 tools for building flows, managing tables, and running tests agentically. Flows are fully versioned with draft and locked states. The core is MIT-licensed and runs on TypeScript with PostgreSQL and Redis.

Wire nodes together in a browser, deploy in one click, and real-time data flows from sources through transformations to outputs: Node-RED is the OpenJS Foundation's flow-based programming tool for event-driven applications. Born at IBM as a proof-of-concept for manipulating MQTT topic mappings, it has become the lingua franca of IoT and automation glue - home automation, industrial control, edge data collection - with a community library of over 5,000 contributed nodes and flows covering protocols, devices, and services. Where visual wiring runs out, JavaScript function nodes written in a rich in-editor code editor take over, and every flow serializes to importable, exportable JSON that shares cleanly and version-controls sensibly. Version 5.0 (2026) delivered the largest editor overhaul in the project's history: a rethought layout with Explorer and Information panels in a split sidebar, a native dark theme with theme variants, improved accessibility, and refreshed node appearance. The runtime is lightweight Node.js, exploiting the event-driven non-blocking model so the same flows run on a Raspberry Pi at the network edge or a cloud VM. Apache-2.0 licensed with 240+ contributors, it pairs naturally with dashboard nodes for live charts and controls.

The integrations your SaaS product offers its own users - that is what Nango, an open-source product-integrations platform, exists to build. It solves the repetitive infrastructure work behind every third-party API connection: OAuth flows, API key handling, token refresh, encrypted credential storage, rate-limit backoff, retries, and multi-tenant connection management. It ships pre-built auth configurations for 800+ APIs. Your users connect their accounts through an embeddable, white-label Connect UI, and your backend then reads or writes data through Nango's proxy, SDKs, or REST API without ever touching raw credentials. Integration logic is written as TypeScript functions covering actions, scheduled data syncs, and webhook processing - all running on one runtime with retries, checkpointing, and per-connection logs built in. Syncs pull records incrementally on a schedule, one-way or two-way, which suits RAG pipelines, search indexing, and keeping local copies of external data current. Selected actions can also be exposed as tool schemas or through a built-in MCP server, so AI agents operate on user-connected accounts without ever handling provider credentials. Auth support spans OAuth 2.0, OAuth 1.0a, API keys, basic auth, and JWT, and observability - logs, metrics, failure detection, and a reconnect flow for expired credentials - is scoped per customer connection for easier support debugging. Works with any backend language. Self-hosting on RepoCloud keeps all customer credentials and synced data on infrastructure you control, which matters for data residency and compliance requirements.

Development teams hand their outgoing webhooks to Svix, which delivers each event to customer endpoints with retries, signed payloads, and a delivery record for every attempt. Your app makes one API call when something happens, a user signs up, an invoice is paid, a build finishes, and Svix delivers the event to every subscribed endpoint your customers registered. Endpoints that fail get automatic retries on a schedule, deliveries are logged attempt by attempt, and failed messages can be resent instead of vanishing. Customers organize their integrations as applications, subscribe endpoints to the event types they care about, filter by channels, and verify signed payloads so forged requests get rejected. You define the event catalog once, and fanout, throttling, and endpoint bookkeeping stop being code you maintain. Official libraries for nine languages and a CLI make the first integration an afternoon task, and the whole service runs from a Docker Compose stack with Postgres and Redis when you want it on your own infrastructure. Your product gains the webhook system customers expect, without your team becoming a deliverability department. 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 17,000 GitHub stars, 460+ contributors, and deployments across telecommunications, automotive, and financial services running on over 10,000 CPU cores at the largest known installations, Apache APISIX delivers a fully dynamic API gateway achieving 140,000 QPS on eight cores with sub-millisecond latency through NGINX's event-driven architecture and LuaJIT-compiled plugin execution. The 100+ open-source plugins cover authentication (JWT, OAuth 2.0, OIDC, Keycloak, LDAP), observability (Prometheus, Datadog, SkyWalking, OpenTelemetry), traffic management (rate limiting, circuit breaking, canary releases, traffic splitting), and security (CORS, IP restriction, CSRF protection) — all hot-reloadable without process restarts via etcd-based real-time configuration synchronization. Multi-protocol support handles HTTP, gRPC, MQTT, TCP, UDP, and WebSocket traffic for both north-south API access and east-west service mesh communication. AI gateway capabilities proxy requests to 20+ LLM providers with semantic caching, token-aware rate limiting, provider failover routing, and content moderation. Custom plugins extend the gateway in Lua, Go, Java, Python, or WebAssembly. Radixtree route matching handles 100,000+ routes without performance degradation. Functions as a Kubernetes ingress controller with native service discovery for Consul, Nacos, and Eureka. Deploy via Docker or Helm charts with horizontal scaling through etcd cluster coordination. 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.

With over 43,000 GitHub stars and adoption by companies including Nasdaq, Samsung, and Expedia, Kong Gateway is the world's most deployed open-source API gateway, processing billions of API requests daily across hybrid-cloud and multi-cloud architectures. Built on the battle-tested NGINX engine with OpenResty's LuaJIT runtime, Kong delivers sub-millisecond proxy latency while supporting REST, gRPC, GraphQL, WebSocket, SOAP, and Kafka protocols. The plugin architecture includes authentication via JWT, Basic Auth, HMAC, key authentication, OAuth 2.0, and LDAP, alongside rate limiting with configurable windows per consumer, IP address, or API key. The AI Proxy plugin provides a universal LLM API that routes across OpenAI, Anthropic, Google Gemini, AWS Bedrock, Azure AI, Databricks, Mistral, and Hugging Face through a single standardized interface, while MCP proxy capabilities convert REST APIs into MCP tools and provide traffic governance for AI agents. Kong supports declarative configuration via YAML for GitOps workflows, a RESTful Admin API for dynamic configuration, and decK CLI for version-controlled infrastructure-as-code management. Upstream health checking with active and passive probes enables automatic failover, and the ring balancer distributes traffic across upstream targets with consistent hashing, round-robin, or least-connections algorithms. The Kong Plugin Hub hosts over 100 community and official plugins covering logging, monitoring, transformation, security, and traffic control. 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.

Put one governed doorway in front of every service you run: Apache ShenYu is an API gateway that proxies, secures, and manages traffic for HTTP, Dubbo, gRPC, WebSocket, and MQTT backends from a single entry point. Every request flows through an ordered, hot-pluggable plugin chain, so you compose exactly the behavior each route needs instead of accepting a fixed gateway feature set. Selectors give you coarse, service-level routing and rules refine it down to individual methods, matched against headers, paths, and parameters. Authentication and edge security come from JWT, OAuth 2.0, request-signing, and WAF plugins, while rate limiting, circuit breaking, and load balancing protect fragile upstreams from traffic spikes. You reshape calls in flight with request, response, and parameter mapping, and convert protocols so a gRPC or Dubbo service answers ordinary HTTP clients. Newer releases add AI gateway plugins that proxy LLM calls with prompt processing, token limits, and sensitive-word filtering, plus an MCP server plugin for exposing tools to AI agents. The ShenYu Admin console on its own port manages plugins, selectors, rules, users, and permissions, then pushes changes live to every gateway replica over WebSocket, ZooKeeper, Nacos, etcd, or HTTP long polling. Metrics, tracing, and logging plugins stream operational data to Kafka or Elasticsearch, and client SDKs for Java, Go, Python, and .NET let services register themselves automatically. 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.