Skip to main content
aria-router sits in front of one or more aria-engine instances and routes requests to the right model based on request metadata (model slug, quant, capability). Ship it standalone or embed the FFI shared library.

Install

Fetch the latest release for your platform:
On the China site the same endpoint mirrors from Gitee at https://ariacompute.cn/api/download/router-latest.

Configure

Provide a routing config that lists each backend engine and the models it serves:
router.yaml

Run

Clients then send requests to http://<host>:9090/v1/chat/completions and set the model field to a slug listed in the config. aria-router forwards the request to the matching backend.

Embed with libaria-router_ffi

Each release ships libaria-router_ffi-<platform>.{so,dylib,dll} and a C header. Link it from any language with a C ABI.
router.c
Refer to the bundled include/aria_router.h for the full FFI surface: reload config at runtime, hot-swap backends, and inspect routing metrics.

When to use aria-router vs aria-engine directly

  • Single model, single process: run aria-engine serve and point clients at it.
  • Multiple models on one host: run one aria-engine per model and put aria-router in front so clients pick a model by slug.
  • Multi-host, multi-tenant: use aria-router as the ingress and configure per-backend health checks and weights.