JOURNAL / CATEGORY

Edge AI.

Inference placement, model delivery, and request routing are related decisions with different responsibilities. These guides help you decide where a model should run, how the release reaches that environment, and which eligible service should handle each task.

Where does the complete result become ready?

Measure the path from input preparation to a usable output, including transfer and initialization. A fast execution benchmark is only part of that experience. Establish device support, data permissions, model compatibility, and a fallback that the application can explain before optimizing an individual stage.

  • Distinguish moving model bytes from running inference.
  • Check cold and warm behavior on representative hardware.
  • Treat all retries and fallback attempts as part of one request budget.

For the broader architecture, explore Edge AI. Follow the articles below as a reading path, or use the guide directory to connect this topic with the rest of the stack.

Articles in Edge AI

Versioned ONNX model packages moving through a CDN to a browser with verification and rollback steps

Delivering ONNX models through a CDN: a deployment guide

Reliable model delivery requires more than uploading an ONNX file. Build a release process that binds models to runtime assets, verifies downloaded bytes, handles browser compatibility, and activates updates only when a complete working package is ready.

An LLM request router selecting among model endpoints using quality, latency, and cost criteria

LLM request routing: balance quality, latency, and cost

A useful LLM router chooses among eligible models, budgets the entire request, and measures successful outcomes. Build a practical policy for deadlines, retries, streaming, evaluation, and gradual rollout without hiding quality failures behind lower request prices.

A device, edge server, and cloud connected by inference paths with latency and privacy indicators

Edge AI vs cloud AI: where should inference run?

Inference placement starts with the job a model must do. Learn how to compare local devices, nearby servers, and cloud services using complete latency budgets, realistic memory measurements, privacy boundaries, and explicit fallback rules.