Skip to content

Reference

Reference is the map of the codebase. One page per module under src/, listing every exported class, function, constant, interface, and type with its signature, what it is for, and where it lives. It is written for people who read, extend, or review the gateway’s internals.

  • Contributors adding a feature, a plugin, or a policy.
  • Reviewers checking whether an internal is used correctly elsewhere.
  • Anyone integrating against the gateway as a library rather than running it as a process.
  • Find the exact signature of anything exported from src/.
  • Follow a symbol back to its file and see what it depends on.
  • Understand the module boundaries — what belongs in core, pipeline, identity, and so on — before adding code.

Each page covers one module. It opens with a one-paragraph summary of the module’s responsibility, then a table of every export, then notes on the non-obvious ones. Signatures are copied from source; if a signature here disagrees with the source, the source wins — open an issue.

Pages are ordered by dependency, not alphabetically. Entrypoints and Types are the best starting points because everything else depends on them.

ModuleDescription
EntrypointsGateway bootstrap and top-level exports
Core EngineHTTP server, radix router, connection pools, cache
PipelineMiddleware policies and execution chain
PluginsPlugin lifecycle hooks and built-in handlers
IdentityAPI key crypto and consumer management
ConfigSchema validation and auto-tuning
TypesCore interfaces and contract types
UtilsLogger, object pool, and metrics buffers
ProfilingV8 CPU profiler and heap snapshots
MonitoringPerformance monitors and alerts
ObservabilityPrometheus exposition format
AdminAdministrative management endpoints
TestingTest suites and benchmark harnesses
  • Deep Dive explains behaviour and configuration; Reference explains structure and signatures.
  • Guides is the place to start if you only want to run the gateway.