yokai
Yokai is a modular Go framework designed to simplify backend application development by providing pre-built observability (logging, tracing, metrics), dependency injection, and extensible module system. It abstracts boilerplate infrastructure concerns so teams can focus on application logic.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | ankorstore/yokai |
| Owner | ankorstore |
| Primary language | Go |
| License | MIT — OSI-approved |
| Stars | 836 |
| Forks | 29 |
| Open issues | 3 |
| Latest release | fxhttpserver/v1.8.0 (2026-06-19) |
| Last updated | 2026-06-22 |
| Source | https://github.com/ankorstore/yokai |
What yokai is
Yokai provides a core module system built on Fx (dependency injection), Echo (HTTP), gRPC-go, and OpenTelemetry, with integrated configuration management via Viper. It exposes a private infrastructure HTTP server for health checks and debugging, and supports extension modules for HTTP/gRPC servers, workers, ORMs, and custom functionality.
Get the yokai source
Clone the repository and explore it locally.
git clone https://github.com/ankorstore/yokai.gitcd yokai# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Go ≥1.20; verify runtime compatibility before adoption.
- Strongly opinionated on dependency injection (Fx) and observability patterns; team must buy into the framework's structure rather than choose components à la carte.
- Extension modules (contrib, custom) expand functionality but add maintenance surface; evaluate stability and support of third-party modules before production use.
- Configuration management via Viper requires upfront setup; ensure configuration strategy (env, files, remote) aligns with deployment topology.
- Module initialization order and lifecycle management (via Fx hooks) must be understood to avoid startup failures and resource leaks.
When to avoid it — and what to weigh
- Lightweight single-file services — Yokai's modular architecture and built-in observability introduce overhead unnecessary for simple, stateless services where minimal dependencies are preferred.
- Strict vendor lock-in concerns — While built on standard libraries, Yokai's opinionated structure around Fx, Echo, and OTEL may limit flexibility if your org requires alternative DI frameworks or HTTP routers.
- Mature, established projects mid-migration — Refactoring existing Go applications to adopt Yokai's module system and DI patterns requires significant rework; better suited for greenfield or new service lines.
- Go versions < 1.20 — Project explicitly requires Go ≥1.20; older deployments cannot adopt without upgrading runtime.
License & commercial use
MIT License. Permissive OSI-approved license allowing commercial use, modification, and distribution with attribution. No patent or trademark clauses restrict usage.
MIT is a permissive open-source license compatible with commercial use. However, verify that any contrib modules or extensions your project depends on also use compatible licenses, as Yokai itself does not impose restrictions but downstream dependencies may.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
No explicit security audit, penetration test results, or vulnerability disclosure policy stated in available data. Depends on security posture of underlying libraries (Echo, gRPC-go, OTEL, Viper). Private infrastructure HTTP server must be isolated from public networks. Dependency management and supply-chain security require vendor review of contrib modules. No claims of cryptographic or security hardening beyond standard library usage.
Alternatives to consider
gin-gonic/gin
Lightweight HTTP framework; lower overhead but requires manual setup of logging, tracing, DI, and metrics. Suitable for teams preferring à la carte component selection over opinionated structure.
uber-go/fx (standalone)
Fx is Yokai's DI foundation and can be used directly. Offers maximum flexibility but requires hand-assembly of observability, configuration, and server patterns.
go-kit/kit
Mature microservices framework with middleware patterns, transport abstractions, and observability. More battle-tested but heavier and less modular than Yokai.
Build on yokai with DEV.co software developers
Explore Yokai's templates, documentation, and showroom demos. Assess fit with your team's DI and observability patterns. Contact Devco for guidance on adoption and integration planning.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
yokai FAQ
Can I use Yokai with my existing Go HTTP codebase?
What observability platforms does Yokai support?
Is Yokai suitable for gRPC-only applications?
How does Yokai handle multi-module releases?
Software developers & web developers for hire
Adopting yokai is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source observability software in production.
Ready to reduce Go backend boilerplate?
Explore Yokai's templates, documentation, and showroom demos. Assess fit with your team's DI and observability patterns. Contact Devco for guidance on adoption and integration planning.