yokai
From public sourcesSimple, modular, and observable Go framework for backend applications.
Overview
- backend
- dependency-injection
- framework
- go
- golang
- grpc-server
- http-server
- kubernetes
- mcp
- mcp-server
Installation
Commands are shown, never run by the marketplace. Check them against the official documentation.- Official websiteFrom public sourcesfrom catalog metadataankorstore.github.io/yokai ↗
- Build from sourceFrom public sourcesfrom catalog metadata
Build from source: no validated build recipe — follow the repository instructions.
github.com/ankorstore/yokai ↗
Compatibility
Unknown means no evidence was found — not that the product is incompatible.| Platform | Status | Architecture | Evidence | Confidence |
|---|---|---|---|---|
| Claude (web & desktop) | Unknown | — | — | — |
| Claude Code | Unknown | — | — | — |
| Cursor | Unknown | — | — | — |
| VS Code | Unknown | — | — | — |
| Windsurf | Unknown | — | — | — |
| ChatGPT | Unknown | — | — | — |
Releases
checked Oct 29, 2026Files in 1.17.0
This release has no attached files.
Release history
- v1.16.0Jun 19, 2026Official source ↗
- v1.8.0Jun 19, 2026Official source ↗
- v1.7.0Jun 19, 2026Official source ↗
- v1.6.0Jun 19, 2026Official source ↗
- v1.5.1Oct 21, 2026Official source ↗
- v1.5.0Jun 19, 2026Official source ↗
- v1.4.0Jun 19, 2026Official source ↗
Quality profile
algorithm quality-v1.0 · assessed Oct 15, 2026Score components
License
MITThis is the catalog policy status, not legal advice.
Sources
Reviews
No reviews yet.
Alternatives
README
From ankorstore/yokai · license MIT · fetched Oct 29, 2026Yokai
[License: MIT] [Go version] [codecov] [Documentation] [Awesome Go]
Simple, modular, and observable Go framework for backend applications.
- Goals
- Documentation
- Overview
- Architecture
- Foundations
- Extensions
- Getting started
- Showroom
- Contributing
Goals
Building backend applications with Go is amazing.
But to build production-grade applications, you need to put in place a bunch of efforts and boilerplate code, introducing complexity not even related to the logic of your application (like dependencies wiring, configuration management, observability instrumentation, etc.).
To solve this, Yokai was created with the following goals in mind:
Simple: it is easy to use, configure and test, enabling you to iterate fast and deliver quickly maintainable applications.Modular: it can be extended with the available Yokai modules, or with your own, to build evolvable applications.Observable: it comes with built-in logging, tracing and metrics instrumentation, to build reliable applications.
In other words, Yokai lets you focus on your application logic, while taking care of the rest.
Documentation
Yokai's documentation is available at https://ankorstore.github.io/yokai.
Overview
Architecture
- Yokai
core modulespreloads logging, tracing, metrics and health check instrumentation, and expose a private HTTP server for infrastructure and debugging needs. - Yokai
extensions modulescan be added to enrich your application features, like public HTTP / gRPC servers, workers, ORM, etc. You can also add the contrib modules or your own. - Those are made available in Yokai
dependency injection system, on which you can rely to build your application logic.
Foundations
Yokai was built using robust and well known Go libraries, such as:
- Echo for HTTP servers
- gRPC-go for gRPC servers
- Viper for configuration management
- OTEL for observability instrumentation
- Fx for dependency injection system
- and more.
Extensions
Yokai's extension system enables you to enrich your application features with:
- the Yokai
built-inmodules - the Yokai contrib modules
- your own modules
Getting started
Yokai provides ready to use application templates to start your projects:
- for gRPC applications
- for HTTP applications
- for MCP applications
- for worker applications
Showroom
Yokai provides a showroom repository with demo applications, ready to run, to see it in action:
Contributing
This repository uses release-please to automate Yokai's modules release process.
[!IMPORTANT] You must provide atomic and conventional commits, as the release process relies on them to determine the version to release and to generate the release notes.