open-gw

Open Gateway

The initiatives

These are separate lines of work. Consequence tiering is one of them. The status on each initiative is the status its repository claims.

Specification

ctier

One Open Gateway initiative: classify an operation by the consequence of getting it wrong, using reversibility, blast radius, data sensitivity, compliance impact, and idempotency. The interface owner declares x-ctier-tier in OpenAPI. The gateway looks it up and may raise the tier, never lower it. No declaration is Tier 4. Specification 1.25.0 includes a worked example where one OAuth scope reaches both a low-tier read and an unclassified export.

GitHub

Reference implementation

ctier-engine

Compiles the specification into configuration for Kong, Apache APISIX, and Apigee, and ships a conformance kit you can point at a running URL. Kong and APISIX are verified. The Apigee bundle is generated from the same compile and has not been executed against an Apigee organization in this repository.

  • Apache 2.0
  • Kong and APISIX verified
  • Apigee generated, not executed
  • Specification DOI
GitHub

Database bridge

gateway-db-mcp

A JDBC bridge that exposes MySQL, MariaDB, PostgreSQL, and SQL Server as MCP tools through Apigee, Kong, or Azure API Management. It ships no policy plane. OAuth, rate limits, and audit logs stay on the gateway that already governs the estate. Queries are read-only by default.

  • Apache 2.0
  • Published
  • Read-only by default
  • io.github.open-gw/gateway-db-mcp
GitHub

Paper 1 artifact

bounded-autonomy

A one-node study of a 30-step agent task that declares which of eight services it needs. The rig measures how many services the task can actually touch, how many credentials are issued, and whether rollback matches the writes. It is a reproducible study, not a product to deploy.

  • MIT
  • Reproducible study
  • Not a product
  • Preprint
GitHub