How Routic works
See how a request enters Routic, moves through the gateway layer, and reaches published model capabilities.
This diagram no longer needs to carry the homepage on its own. It lives here in docs, where people can read the product story first and then look at the delivery path in context.
From your app to routed model delivery
Routic is not here to push internal architecture into the homepage. It is here when you need a clearer view of how requests, policy, and delivery come together as one product path.
Layout matches the usual “app → gateway → models” story.
How to read this diagram
Think of it as a product-level operating view: your app on the left, Routic as the unified gateway in the middle, and published model capabilities on the right.
- Your application keeps a familiar integration path and gets to a first request quickly.
- The gateway layer centralizes auth, policy, observability, and delivery in one place.
- Published models stay understandable and manageable as a product surface for the team.
Next steps
Once the path makes sense, move on to the first request or browse the published model catalog.