yomo
Library Listed
A QUIC-based runtime for AI-LLM tool routing and serverless execution
- Downloads
- 26
- Dependents
- 0
- Stars
- 1,930
- Forks
- 150
- Contributors
- 3
- Commits
- 202
- Latest release
- 2.1.6 ·
About
YoMo is an open-source LLM Function Calling Framework for building scalable and ultra-fast AI Agents. 💚 We care about: Empowering Exceptional Customer Experiences in the Age of AI
We believe that seamless and responsive AI interactions are key to delivering outstanding customer experiences. YoMo is built with this principle at its core, focusing on speed, reliability, and scalability.
🌶 Features
| Features | ||
|---|---|---|
| ⚡️ | Serverless LLM Tools | Deploy and Manage LLM Tools / Skills seamlessly. |
| 🔐 | Enhanced Security | TLS v1.3 encryption is applied to every data packet by design, ensuring robust security for your AI agent communications. |
| 📸 | Effortless Agents DevOps | Streamline the entire lifecycle of your LLM tools, from development to deployment. Significantly reduces operational overhead, allowing you to focus exclusively on creating innovative AI agent functionalities. |
| 🌎 | Geo-Distributed Architecture | Bring AI inference and tools closer to your users with our globally distributed architecture, resulting in significantly faster response times and a superior user experience for your AI agents. |
🚀 Getting Started
Let's build a simple AI agent with LLM Function Calling to provide weather information:
Read the full README
Step 1. Install CLI
curl -fsSL https://get.yomo.run | sh
Verify the installation:
yomo --version
Step 2. Start the server
Use Ollama as the LLM provider:
ollama pull ornith
Launch the server:
yomo serve
You can also use the --config flag to specify a custom coniguration yaml file.
Step 3. Implement the LLM Function Calling
yomo init
Finished, now, let's run it:
yomo run -n get-weather ./app
Done, let's have a try
curl http://127.0.0.1:9001/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"messages": [
{
"role": "user",
"content": "I am going for a hike on the Yarra Bend Park Loop. What should I wear?"
}
]
}'
You'll receive a helpful response like this:
Yarra Bend Park is on the Yarra River and gets misty/foggy when it overflows from its channel into the park—this typically occurs on damp autumns around November. Today's conditions are mild, warm, dry, with no fog expected today but a chance of light rain or drizzle possible tomorrow afternoon.
**Clothing for your hike:**
- **Base/mid-layer:** A long-sleeve top is enough. If it gets chilly at the river bank (a 2°C drop is possible), add a fleece mid-layer rather than relying on just an autumn outer shell.
- **Pants:** Jeans are okay if you want them, but light hiking pants or athletic wear are more comfortable and dry faster.
- **Footwear:** You'll be on forest trails around the Yarra River—sturdy sneakers will do for the loop today. If there's rain tomorrow afternoon, bring a pair of boots.
- **Rain gear:** Carry an umbrella just in case you get caught on the trail after the rain passes this weekend.
**Don't worry about mosquitoes this month.** They arrive in March/April when it gets hot and dry—and that's right around the time summer solstice fog starts forming (June). In November, no mosquitoes at all.
Explore More Examples
Check out our Servereless LLM Function Calling Examples for more use cases and inspiration.
📚 Documentation
Read more about YoMo on yomo.run.
🎯 Focuses on Geo-distributed AI Inference Infra
It’s no secret that today’s users want instant AI inference, every AI
application is more powerful when it response quickly. But, currently, when we
talk about distribution, it represents distribution in data center. The AI model is
far away from their users from all over the world.
If an application can be deployed anywhere close to their end users, solve the problem, this is Geo-distributed System Architecture:

🦸 Contributing
First off, thank you for considering making contributions. It's people like you that make YoMo better. There are many ways in which you can participate in the project, for example:
- File a bug report. Be sure to include information like what version of YoMo you are using, what your operating system is, and steps to recreate the bug.
- Suggest a new feature.
- Read our contributing guidelines to learn about what types of contributions we are looking for.
- We have also adopted a code of conduct that we expect project participants to adhere to.
Devleopment
Build
cargo build --release ./target/release/yomo --helpUse Ollama as the LLM provider:
ollama pull ornithRun YoMo server:
./target/release/yomo serveInitialize a Serverless LLM Tool project:
./target/release/yomo initthen edit
./app/src/app.tsin the project.Run YoMo serverless tool:
./target/release/yomo run --name get-weather ./appSend a request to the LLM agent:
curl \ --request POST \ --url http://127.0.0.1:9001/v1/chat/completions \ --header 'Content-Type: application/json' \ --data '{ "messages": [ { "role": "user", "content": "How is the weather in London?" } ] }'Send a request to the serverless function directly:
curl \ --request POST \ --url http://127.0.0.1:9001/tool/get-weather \ --header 'Content-Type: application/json' \ --data '{ "args":"{\"city\":\"London\"}" }'
License
Compatibility
- Runs on
- GPU support unknown
What shows it
- no dependency or feature matches a backend row
- Native code
- None found
- No native code found
- Python bindings
- No Python binding crate found
- License
- Apache-2.0
Compare with similar projects
Order: strongest tier first, then most downloads, then name, with unmeasured values last. A library counts downloads over 30 days. An app counts binary downloads per release. An app with none counts its crate downloads over 30 days. ML Rust runs this catalogue, so its closest project always gets a row.
| Project | Downloads | Dependents | Stars | Latest release | Runs on (GPU) | Native code | License |
|---|---|---|---|---|---|---|---|
|
A QUIC-based runtime for AI-LLM tool routing and serverless execution |
26 downloads over 30 days | 0 | 1,930 | 2.1.6 | GPU support unknown | No native code found | Apache-2.0 |
|
agent-client-protocol Featured
Core protocol types and traits for the Agent Client Protocol |
941,949 downloads over 30 days | 145 | 245 | 5.0.0 | GPU support unknown | No native code found | Apache-2.0 |
|
langchain-rust Listed
LangChain for Rust, the easiest way to write LLM-based programs in Rust |
4,306 downloads over 30 days | 4 | 1,362 | 8.0.0 | GPU support unknown | Binds native code: tree-sitter (feature tree-sitter), ort-sys (feature fastembed), ring (feature surrealdb), tree-sitter-language (feature tree-sitter). Build uses a native toolchain: cc (feature tree-sitter) | MIT |
|
prompty Listed
Prompty is an asset class and format for LLM prompts |
337 downloads over 30 days | 0 | 1,286 | 2.1.0 | GPU support unknown | No native code found | MIT |
|
bamboo-agent Listed
A fully self-contained AI agent backend framework with built-in web services, multi-LLM provider support, and comprehensive tool execution |
331 downloads over 30 days | 10 | 22 | 2026.11.14 | GPU support unknown | Binds native code: libsqlite3-sys, mac-notification-sys, openssl-sys, ring, tree-sitter and 1 more | MIT |
|
Rust-native, library-first coding-agent runtime and terminal CLI inspired by Pi, with composable LLM providers, tools, sessions, and plugin ABI |
16 binary downloads per release | Not applicable | 231 | Not measured | Not measured | MIT | |
|
An open protocol that gives AI agents a secure, sandboxed place to run code and use tools — with lean context usage. AXP works alongside MCP |
Not measured | Not applicable | 3 | Not measured | Not measured | Not measured | Apache-2.0 |
Why ListedNo archive, New or Featured rule places it, so it is Listed.
What it lacks for Featured
- It has 0 active dependents and 0 new dependents in 365 days. Featured needs 11 active dependents or 9 new dependents in 365 days. The repository route reads 1,930 stars, 150 forks and 3 contributors. It needs 4,539 stars, 434 forks and 79 contributors together.
What else the check found
- The last activity is on 7 Nov 2026, 2 days ago. The rules expect an update within 700 days. Dormancy rule
Exact rules: Listed, Featured library. The check on applied thresholds version 9.
Every rule outcome, as the check records it
expected-interval: version 2.1.6 base 700: E = 700 daysdormancy: last activity 2026-11-07, 2 days ago, E = 700: activefeatured: not featured: active_users 0 < 11 and new_adopters 0 < 9 and repository route stars 1930 (needs 4539), forks 150 (needs 434), contributors 3 (needs 79)listed: listed: no archive, new or featured rule applies
Measurements and sources
Each signal row shows the raw value, its source and the fetch date. The Sources list gathers every distinct source on this page. Movement needs more history.
Sources6 sources
- Description: the crates.io description
- crates.io database dump, fetched
- RustSec advisory database, fetched
- GitHub repository, fetched
- crates.io package, fetched
- GitHub contributors, fetched
Adoption0 active dependents, 0 new dependents in 365 days1 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Active dependents | 0 | crates.io database dump | Yes | |
| New dependents (365 days) | 0 | crates.io database dump | Yes | |
| Peak active dependents | 0 | crates.io database dump | Yes | |
| Active dependents as a share of the peak | 1 | crates.io database dump | Yes | |
| Binary downloads per release | Not measured | Yes |
MaintenanceLatest human commit: 2 days ago3 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Latest human commit | 2026-11-07 | GitHub repository | Yes | |
| Latest release | 2026-10-21 | crates.io database dump | Yes | |
| First release | 2026-03-29 | crates.io database dump | Yes | |
| Latest version | 2.1.6 | crates.io database dump | Yes | |
| Days the oldest outside issue waits for a reply | 0 | GitHub repository | Yes | |
| Maintainer replies over 365 days | 1 | GitHub repository | Yes | |
| Repository archived | false | GitHub repository | Yes | |
| Repository gone | false | GitHub repository | Yes | |
| Release commit or manifest in the repo | true | crates.io package | Yes | |
| Published docs | true | crates.io database dump | Yes | |
| Latest release fails cargo check | Not measured | Yes | ||
| Build check date | Not measured | Yes | ||
| Build check toolchain | Not measured | Yes |
SecurityUnpatched vulnerabilities: none
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Unpatched vulnerabilities past the grace window | none | RustSec advisory database | Yes | |
| RustSec unmaintained advisory | none | RustSec advisory database | Yes | |
| Deprecation notice | none | crates.io database dump | Yes | |
| Deprecated requirement | none | crates.io database dump | Yes |
Distribution26 releases, 26 downloads over 30 days5 not measured
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| Releases | 26 | crates.io database dump | Yes | |
| Downloads over 30 days | 26 | crates.io database dump | Yes | |
| Binary downloads over the last 3 releases | Not measured | Yes | ||
| Homebrew installs on request over 365 days | Not measured | Yes | ||
| Repology repository families | Not measured | Yes | ||
| Docker pull growth over 90 days | Not measured | Yes | ||
| Docker pulls at the growth baseline | Not measured | Yes | ||
| Every version a prerelease | false | crates.io database dump | Yes | |
| Every version 0.0.x | false | crates.io database dump | Yes | |
| Every version yanked | false | crates.io database dump | Yes | |
| Crate deleted from crates.io | false | crates.io database dump | Yes |
Repository1,930 stars, 150 forks, 3 contributors, 202 commits. Stars alone never qualify a project.
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| GitHub stars | 1930 | GitHub repository | Yes — one part of the repository route | |
| GitHub forks | 150 | GitHub repository | Yes — one part of the repository route | |
| Contributors with a GitHub account | 3 | GitHub contributors | Yes — one part of the repository route | |
| Commits on the default branch | 202 | GitHub repository | No | |
| Repository's main crate left out of the entry | none | crates.io database dump | Yes |
Facts that never count
| Signal | Value | Source | Fetched | Counts |
|---|---|---|---|---|
| License | Apache-2.0 | crates.io database dump | No | |
| Runs on, from listed crates and their direct dependencies | GPU support unknown | crates.io database dump | No | |
| What shows each backend | no dependency or feature matches a backend row | crates.io database dump | No | |
| Native code, from listed crates and their dependencies | No native code found | crates.io database dump | No | |
| Python bindings, from direct dependencies of listed crates | No Python binding crate found | crates.io database dump | No | |
| Crates that depend on a listed crate directly | 0 | crates.io database dump | No |
Corrections and review history
No correction applies to this entry.
Judgments
A judgment enters only through an approved issue and a merged pull request.
No judgment applies to this entry.