Search Results for "glew source code"

Agent Stack is an open infrastructure platform designed to take AI agents from prototype to production, no matter how they were built. It includes a runtime environment, multi-tenant web UI, catalog of agents, and deployment flow that seeks to remove vendor lock-in and provide greater autonomy. Under the hood it’s built on the “Agent2Agent” (A2A) protocol, enabling interoperability between different agent ecosystems, runtime services, and frameworks. The platform supports agents built in...

DeployStack is an open-source framework that helps developers and teams define and deploy production infrastructure stacks using modular, reusable templates, often with IaC (infrastructure as code) principles. It provides a structured way to compose resources such as cloud networking, compute, and managed services into coherent deployment blueprints that can be versioned and reused across projects.

Bifrost is an LLM gateway designed to provide a unified OpenAI-compatible API front for many different model providers. It abstracts away the complexity of working directly with multiple backend providers (OpenAI, Anthropic, AWS Bedrock, Google Vertex, etc.), enabling you to plug in providers and switch between them without touching your client code. It is built to be high performance: in benchmark tests at 5,000 requests per second, it reportedly adds only microseconds of overhead and...

MCP Konnect is a Model Context Protocol (MCP) server implementation that enables AI assistants and agents to interact with Kong Konnect, the API management and gateway platform from Kong. This server exposes Kong Konnect’s APIs through standardized MCP interfaces so that tools like conversational AI or agent systems can query analytics, inspect configuration, and manage Kong Gateway resources using natural language or programmable agents. By bridging MCP clients to Kong’s control plane, the...

Unla is a lightweight, highly available MCP gateway written in Go that turns existing MCP servers or ordinary HTTP APIs into MCP-compliant services through configuration, not code changes. Its goal is to let teams “wire up” tools they already run—internal REST endpoints, third-party APIs, or local MCP servers—and present a single, reliable MCP interface to clients like Claude Desktop, Cursor, and IDEs. The gateway focuses on operational concerns you’d expect in production: multi-instance...