◆ NEW · v1.0 self-hosted YAML-based €99 one-time

Service Map · Developer Tools

Always know how your services connect.

An interactive microservice dependency visualiser that gives your team a live map of every service, dependency, and integration — ready in minutes, no backend required.

€99€149 · one-time · 1 year updates · unlimited internal use
Service Map – interactive dependency graph for your microservice architecture
1 YAML file → 1 live graph updates on every change

The Problem

Your architecture docs are out of date. Again.

Tribal knowledge in heads, stale Confluence pages, and Slack-thread archaeology are not a system. Service Map turns your YAML service definitions into a living, interactive graph that always reflects the real state of your stack.

  • Confluence diagrams haven't been updated since the last reorg.
  • New engineers spend days manually tracing service → service calls.
  • Stakeholders ask questions you can only answer by reading source code.
  • SaaS service maps charge €40 per seat and send your topology to a third party.

What's included

A dependency map built for real engineering teams.

Six capabilities, one YAML file, zero infrastructure. Drop the static build on any host and go.

01 — Layout

Auto-Layout

Graph nodes are arranged automatically by a layout engine. No manual positioning. Ever.

02 — Filter

Filter & Focus

Narrow down by product area, status, tech stack, or team. Zoom into any sub-graph with one click.

03 — Trace

Hover Tracing

Instantly highlight all upstream and downstream dependencies from any node.

04 — Share

Shareable URLs

Every filter and node selection is encoded in the URL. Copy and share the exact view.

05 — Config

YAML-based

Describe services in simple YAML files. The graph updates automatically on every change.

06 — Deploy

Deploy Anywhere

Pure static files. Host on Netlify, Vercel, S3, or GitHub Pages — at zero hosting cost.

How It Works

YAML in. Live graph out.

Edit a config file, push, deploy. The graph mirrors the truth in your repo — not a slide someone last updated in 2023.

services/checkout.yamlYAML
id: checkout-svc
area: orders
team: payments
tech: node-20
# all dependencies →
depends_on:
  - cart-api
  - stripe-bff
  - inventory-svc
consumes:
  - order-events
pnpm build · deploy · share URL
$ pnpm build && pnpm deployshell
→ bundling 38 services
→ rendering dependency graph
→ static build ready · 412 KB
→ deployed to S3 · 3.2 s
Service Map detail panel – dependent services, tech stack and team ownership

↑ Click any node — full dependency chain, tech stack, team ownership, related services.

Who It's For

Built for the whole engineering team.

Three perspectives on the same graph. One single source of truth.

01 / ENGINEERSDEV

Onboard in hours, not days.

Understand the whole system before touching a line of code. Trace call chains before making changes.

  • System overview
  • Impact analysis
  • Safer refactors
02 / ARCHITECTSARCH

Diagrams that stay up to date themselves.

Present accurate dependency diagrams to stakeholders without maintaining slides. Filter, share URL, done.

  • Always-current docs
  • Subsystem deep-dives
  • Stakeholder views
03 / EM & STAFF+MGT

The whole organisation, at a glance.

Track service ownership, migration status, and technical debt across the org — without dashboards.

  • Ownership overview
  • Migration tracking
  • Tech debt visibility

Try it first

See the microservice dependency visualiser live.

Explore a real multi-service architecture with filtering, focus mode, and hover tracing. No sign-up, no email, no cookies. Just the tool.

What's included

Everything to start today.

One purchase. Source code, pre-built artefact, sample data, documentation.

  • Full source codeTypeScript · Vite · Cytoscape.js
  • Pre-built static filesdeploy on any host immediately
  • Sample service dataworking graph straight out of the zip
  • Documentationconfiguration · adding services · deployment
  • 1 year of updatesfeatures & fixes via git pull

Technical requirements

Runs anywhere static runs.

No server, no database, no runtime dependencies after the build.

  • Deploy onNetlify · Vercel · GitHub Pages · S3
  • Build requirementsNode.js ≥ 20 · pnpm · one-time setup
  • No runtime backendpurely static after build · zero hosting cost
  • Browser supportChrome · Firefox · Safari · Edge
  • Your data, your infratopology never leaves your environment

FAQ

Six honest answers.

If something's missing, just ask.

hello@wallstrdev.de

Yes — you own the deployment completely. No accounts, no SaaS, no vendor lock-in. Your topology data never leaves your infrastructure.
No. You describe your services in YAML files; the visualisation is generated automatically. React is the technical foundation — you don't need to touch it.
Yes — colours, icons, area labels, and edge types are all configurable via a single YAML config file. No code changes required.
All new features and bug fixes released in the first year, applicable with a simple git pull.
One purchase covers unlimited internal use within your organisation — no per-seat fees, no higher tier when your team grows.
Service Map runs entirely on your own infrastructure. Your architecture data never leaves your environment — no third-party servers, no subscriptions, no privacy concerns. And it's a one-time price of €99, not a monthly per-seat fee.
◆ one-time · yours forever

Service Map · v1.0

99

No subscription. No usage fees. No expiry date.

1 yearfree updates
unlimitedinternal use
fullsource code
pre-builtstatic bundle