Connectivity

Connectivity

Source

Eden's Connectivity category gives applications, agents, services, models, and data systems a secure, protocol-aware way to communicate.

Connectivity begins with an endpoint and becomes operational through gateways, APIs, interlays, routing, mirroring, protocol translation, identity, and private transport.

Capabilities

CapabilityWhat it coversStart here
EndpointsRepresent servers, functions, applications, APIs, LLMs, and databases as governed resources.Endpoints
Service gatewaysPlace one authenticated, policy-aware entry point in front of a system.Gateway model
APIsCompose, publish, version, and authorize reusable interfaces.Published APIs
Routing & mirroringDirect, duplicate, and compare traffic across eligible targets.Traffic Mirroring
Protocol translationBridge client and backend protocols through an explicit gateway contract.Gateway model
Identity & accessControl which human, service, runtime, or agent identity may use a connection.Authentication

Endpoint families

Eden can represent databases, caches, vector stores, LLMs, applications, HTTP services, functions, servers, storage systems, and cloud platforms as governed endpoints. Endpoint type controls configuration and protocol behavior; identity, permissions, credentials, telemetry, and audit remain consistent.

How Eden implements connectivity

  • Gateway supplies endpoints, gateways, APIs, routing, identity, policy, and

protocol-aware request handling.

  • Data Plane extends the data plane with additional routing and execution

capability.

API surfaces

Help improve Eden Docs

Find something unclear or incomplete? Review the source and propose an update.

View on GitLab Updated July 27, 2026