# Hookway > Hookway is an MIT-licensed, self-hosted gateway for verifying and routing webhooks, handling HTTP requests, and exposing selected APIs as authenticated MCP tools. Hookway is MIT-licensed. Operators run their own infrastructure. The public builder exports configuration; it does not deploy a server. ## Product and documentation - [Hookway | Self-hosted webhook gateway](https://www.gethookway.com/): Verify and route webhooks to queues, streams, databases and APIs. Run Hookway in your infrastructure, with YAML flows, a visual builder and optional MCP tools. - [About the open-source Hookway project](https://www.gethookway.com/about/): Hookway is an MIT-licensed project maintained by Jason Giroux. Learn about self-hosting, the public builder, project boundaries and operational evidence. - [Self-hosted API-to-MCP gateway | Hookway](https://www.gethookway.com/mcp-gateway/): Expose selected API operations as MCP tools with explicit caller permissions, API keys or OAuth, separate upstream credentials and reviewable YAML. - [Run your first signed webhook](https://www.gethookway.com/docs/get-started/): Run Hookway locally, verify a signed webhook, and inspect its delivery to RabbitMQ with the disposable Docker Compose walkthrough. - [Route verified webhooks to RabbitMQ, Kafka or SQS](https://www.gethookway.com/docs/guides/webhooks-to-queues/): Follow a working signed-webhook-to-RabbitMQ example, then choose Kafka or SQS with explicit acknowledgement, retry and consumer boundaries. - [Import OpenAPI operations as MCP tools](https://www.gethookway.com/docs/guides/openapi-import/): Run a local customer API, import one read operation, grant an MCP caller access, and verify a tool call through Hookway with reviewable YAML. - [Durable MCP event subscriptions](https://www.gethookway.com/docs/guides/mcp-events/): Expose named events alongside tools on an authenticated MCP endpoint. Hookway stores active subscriptions and accepted pending deliveries in PostgreSQL, then sends matchi - [Security](https://www.gethookway.com/docs/reference/security/): Choose a sender authentication scheme, protect credentials, and restrict the interfaces your deployment exposes. Authentication happens before event delivery; flows using - [Delivery guarantees and recovery](https://www.gethookway.com/docs/operations/delivery-guarantees/): A successful HTTP response describes the configured flow's acknowledgement contract. It does not always mean the destination received the event, and does not by itself es - [Performance results and methodology](https://www.gethookway.com/docs/evidence/performance/): Measured on 2 vCPU and 4 GiB , passed three 5,000 requests/s, 20-second bursts and a continuous 500 requests/s, 30-minute mixed workload against a synthetic destination. ## Project - [Source and license](https://github.com/jaysongiroux/hook_way): maintained by Jason Giroux.