Concepts
Apian Labs Relay is designed around a few core concepts that keep routing deterministic and explainable. This page defines the building blocks so you can design your first routing policy with confidence.
Workspaces and API keys
A workspace represents an environment and billing boundary. Apian Labs Relay API keys are scoped to a workspace and should only be used from trusted backend services.
Segments
Segments are labels that group traffic with the same reliability rules. For example, you might route transactional and incident traffic differently without changing your application code.
Routing policies
A routing policy defines provider ordering, retry behavior, and cooldown windows. Apian Labs Relay applies policies deterministically so that the same conditions produce the same routing decision every time.
Traces and receipts
Every message generates a trace timeline and receipts for each attempt. These proof artifacts let you audit provider behavior and explain delivery outcomes to stakeholders.
Providers
Apian Labs Relay orchestrates providers that you connect, such as Twilio and Telnyx. It does not replace your provider contracts, it sits on top and coordinates failover.