[abhinav00anand]

Project

viento

Checklist

• I read CONTRIBUTING.md - awesome-python is a shortlist, not a catalog
• One project per PR
• PR title format: Add project-name
• Entry format: - [pypi-name](https://github.com/owner/repo) - Description ending with period.
• Display name is the PyPI package name
• Placed in an existing use case (new sections and subcategories are maintainer-only)
• Meets all Quality Requirements: active, stable, documented, at least 1 month old

Which Tier

Pick one:

• Obvious choice - a tool an experienced Python developer would name when asked "what do I use for this?"
• Challenger - not yet the obvious choice, but a credible successor to one. Give adoption-trajectory evidence, not popularity alone.

Explain:
Viento is a lightweight distributed AI inference runtime SDK that connects local inference backends (Ollama, vLLM, llama.cpp) across edge devices and cloud GPUs to a unified OpenAI-compatible mesh without requiring inbound port forwarding or public static IPs.

Displacement

Not applicable — the LLM Inference and Serving use case currently has 3 entries (sglang, vllm, mlx-lm) and adding viento brings it to 4 entries (below the 5-entry cap).

[JinyangWang27]

@abhinav00anand Thanks for you submission. A challenger needs adoption-trajectory evidence as a credible successor to an obvious choice, which isn't there yet. The diff also moves an unrelated entry (openviking) out of its subcategory. See CONTRIBUTING.md.