Docs Product

Architecture

See how your browser or application connects through Eco to Orbio.

On this page

Learn where Eco sits between your application and Orbio, and where data goes.

The system#

The playground and your own application use the same Eco API. Eco makes routing decisions. Orbio validates your key and runs model calls.

Eco system flow

Preparing diagram…

Diagram source
eco@docs mermaid
flowchart LR
    Browser["Browser: Eco playground"] -->|"HTTPS: message + your key"| Eco["Eco API: routing"]
    App["Your application"] -->|"HTTPS: message + your key"| Eco
    Eco -->|"Selected model + request"| Orbio["Orbio gateway"]
    Orbio --> Models["Model providers"]
    Models --> Orbio
    Orbio -->|"Answer or stream"| Eco
    Eco -->|"Answer + route headers"| Browser
    Eco -->|"Answer + route headers"| App

The website lives at https://orbioeco.sh. The API lives at https://api.orbioeco.sh. The playground calls the API directly from the browser.

What each part does#

PartRole
Playground or your appSupply a key, messages, and model preference. Display the result.
Eco APICheck the request, choose an eligible model for auto modes, and relay the answer.
OrbioValidate the user's key, handle credits, and call the model provider.

For an auto mode, Eco replaces the request's model id with its selection. For an exact model id, it forwards the request unchanged. Streaming replies pass through as they arrive.

Health, catalog, and model-list requests are public and do not call Orbio. Preview returns a decision instead of an answer, but may call the classifier through Orbio.

Data boundaries#

The playground saves your key and recent route metadata in your browser. Prompt text and replies stay in browser memory while you use the page.

The Eco API processes requests in memory. It has no account database or server-side conversation history. Its logs contain request metadata, not prompt or completion bodies. Orbio and model providers have their own data policies.

Next: Installation & usage or Privacy & keys.