Analysis updated 2026-05-18
Add a durable AI agent backend to a multi-tenant app without building the agent loop yourself.
Let each tenant or customer run a differently configured agent built fresh from your own database.
Self host the service on Google Cloud Run or as a single process against your own Postgres database.
Call the same agent runtime from a Go, TypeScript, Python, or Rust client library.
| deepnoodle-ai/nvoken | 42wim/fabio | 42wim/go-xmpp | |
|---|---|---|---|
| Stars | 0 | — | — |
| Language | Go | Go | Go |
| Last pushed | — | 2018-02-04 | 2020-01-24 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 3/5 | 3/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a Postgres database and AI provider API keys, the project is still an early, evolving implementation.
nvoken is an early stage, open source backend service that gives an app the plumbing needed to run AI agents, the kind of assistant that can carry on a conversation, use tools, and complete multi step tasks, without the app's own developers having to build all of that infrastructure themselves. Instead of running its own agent inside your app's code, your app sends nvoken a description of the agent it wants, called a spec, along with the user's message, and nvoken carries out that one conversation turn, handling things like streaming the response back, saving checkpoints so work is not lost if something crashes, and pausing for a human to approve a step when needed. The project's central design choice is that nvoken deliberately does not store the definition of your agents, things like their instructions, their tools, or which AI model they use. Instead, your app is expected to build that description fresh from its own database every time it calls nvoken, so if you support many customers with slightly different agent behavior, you never have to register, update, or migrate a separate copy of each agent inside nvoken itself. nvoken only stores the ongoing conversation sessions, the record of what happened during a turn, and optionally an encrypted copy of the API credentials used to pay for AI calls. The README compares this directly against several other agent hosting options, arguing that most of them either only run on one company's cloud, are not fully open source, or still expect you to register your agent definitions with them, while nvoken avoids all three. Right now nvoken works with Anthropic's and OpenAI's AI models, and the project ships generated client libraries for Go, TypeScript, Python, and Rust so an app in any of those languages can talk to it the same way. It can be self hosted, either as a small packaged deployment on Google Cloud Run with its own database, or as a single combined process you run yourself against your own Postgres database. The project describes itself explicitly as an early implementation, with some pieces, like the full checkpoint and steering system, still being built, and it points readers who find gaps between its stated design and current behavior to open an issue. The code is released under the Apache-2.0 license.
An open source backend service that runs AI agent conversations for an app without storing the app's agent definitions itself.
Mainly Go. The stack also includes Go, TypeScript, Python.
Free to use, modify, and distribute, including commercially, under the Apache-2.0 license.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.