Comments
>log in to commentKeeping track of every HTTP, gRPC, queue or DB link across many repos is hard. Kuuhaku scans your code, builds an interactive service map with file/line evidence, and adds pull‑request checks that flag broken calls before merge. It updates automatically and works from the CLI. I’d love your thoughts 😊
Kuuhaku scans your repositories and generates an interactive map of all service calls, routes, queues and shared databases.
- for
- Developers and teams that need visibility into inter-service communication and pull-request safety.
- pricing
- paid · free trial
Key features
- Repository scanning — Scans multiple repos to discover HTTP, gRPC, queue and DB connections with file and line references.
- Interactive map — Displays repos as nodes and connections as edges with pan, zoom and in-place expansion.
- Pull-request checks — Compares branch changes to detect broken routes, missing queues or model fields before merge.
- Review inbox — Groups unresolved calls and suggests fixes, turning each decision into a declaration.
- Import diffs & history — Shows what routes, queues or models were added, removed or changed between scans.
- Compliance data — Tags model fields and routes with LGPD/GDPR categories and can export CSV records.
- Alerts & digest — Sends Slack/Teams alerts and weekly email digests of architecture changes.
- CLI & CI integration — Run scans locally or in CI; only the graph is uploaded, supporting Windows, macOS and Linux.
Use cases
- Detect breaking API changes across microservices before merging a PR.
- Visualize and audit communication patterns in a multi-repo monorepo.
- Track added or orphaned queues and websockets in event-driven systems.
- Generate compliance reports for personal data flowing through services.
Kuuhaku vs alternatives
 Kuuhaku |  Hookdeck |  Render |  Railway |  Vercel | |
|---|---|---|---|---|---|
| Best for | Architecture maps with call-site evidence | Event gateway for event-driven apps | Deploying apps and services | One-click app deployment | Frontend deployment platform |
| Pricing | Paid | Free | Subscription | Subscription | Subscription |
| DevHunt upvotes | 1 | 30 | 0 | 0 | 0 |
| Launched | Oct 2026 | Mar 2024 | — | — | — |
- Kuuhaku vs Hookdeck: Hookdeck focuses on routing and managing events, not visualizing code-level service maps.
- Kuuhaku vs Render: Render provides cloud hosting and deployment, not architecture discovery or PR safety checks.
- Kuuhaku vs Railway: Railway automates deployment and databases but does not map inter-service calls.
- Kuuhaku vs Vercel: Vercel specializes in frontend hosting, lacking code-level call-graph analysis.
Kuuhaku FAQ
How does Kuuhaku detect service calls?+
It parses the code in your repositories to find HTTP routes, gRPC calls, queue publishers/consumers and shared database accesses, recording file and line numbers.
Can Kuuhaku run in CI pipelines?+
Yes, the CLI can be used in GitHub Actions or Bitbucket Pipelines to run scans and post pull-request checks.
What happens to unresolved calls?+
They appear in the review inbox with a suggested answer; accepting the suggestion records a declaration for future scans.
Is any data sent to Kuuhaku’s servers?+
Only the graph (names, paths, line numbers and surrounding context) is uploaded; the source code itself stays on your machine.
Do I need a credit card for the trial?+
No, every plan offers a 14-day free trial without requiring a credit card.
What compliance information does Kuuhaku provide?+
It tags model fields and route parameters with LGPD/GDPR categories and can export a CSV of personal data processing.
Summarized by DevHunt from kuuhaku.dev · Oct 16, 2026. Details may change; check the official site.
