Skip to content
Fenwave
en
Service Catalog

Every service, its owner, and what breaks if it stops

A live inventory built from your repositories rather than maintained by hand. Open any component to find its owner, its APIs, its docs and its dependency graph — which is the difference between a two-minute answer and a Slack thread that ends in nobody knowing.

Catalog & docs
The Fenwave service catalog as a table: systems and components with their owner, lifecycle and documentation.

In this capability

  • Ownership on every component — no orphan services
  • API reference for REST, GraphQL and gRPC, generated from source
  • Architecture Explorer: an interactive dependency canvas
  • TechDocs published beside the code it documents
  • Tech Radar showing what your organisation has adopted

In Fenwave

Explore›Catalog›checkout-api

Built on

  • Backstage
  • OpenAPI
  • TechDocs

Where teams use it

Platform engineering

Know what breaks before you deprecate it

An interactive dependency canvas built from your repositories, not from memory.

2 weeks2 minutesService Catalog
Platform engineering

Documentation that is wrong in the pull request, not in production

TechDocs built from the repository, published beside the service it describes.

14 monthsper commitService Catalog
Data & analytics

Find which service owns the field before you model it

Search the catalog for the API, read its schema, see who owns it.

4 days3 minutesService Catalog

More in Catalog & docs

All features

See Fenwave on your own projects

Thirty minutes, on your repositories and your clusters. We will point out three requests your platform team would stop receiving as soon as next week.