Skip to main content
Two boundaries define it. Above it: your orchestrator. It owns the conversation, turn-taking, and session state, and it doesn’t call providers directly. It calls the Execution Layer. Below it: the models, both the ones SLNG runs in-region and the ones proxied to external providers. Graph 1 The layer occupies the space in between, and improves the 3 model steps. Your orchestrator asks for a transcript, asks for a response, asks for audio. What runs between the asking and the answering is the Execution Layer, and it can change entirely without your orchestrator noticing. It runs in-region across SLNG regions, next to the models it’s routing to. That’s not incidental. It is done so that there’s no hop, which means no data residency