Skip to main content
← Back to projects
Actual NexusCanvas interface showing a service topology and graph-analysis panel 04 / POOYA LABS
PROJECT / 04Visual system architecture

NexusCanvas

Public demo

A service-topology studio for building architecture graphs, checking dependency cycles and structural risks, and exporting snapshots or Docker Compose starters. Performance values are illustrative simulations.

Next.jsTypeScriptSVGDocker Compose
Open demo ↗ View source ↗
UI /Interface captures
NexusCanvas architecture studio on mobile
NexusCanvas architecture studio on mobile
01 /The challenge

In system architecture, complex service relationships can hide dependency cycles, isolated services, or bottlenecks. The tool turns those structures into a visual, inspectable model.

02 /Approach

A browser-side canvas supports node and edge editing, graph-structure analysis, a canvas/rack view switch, and versioned snapshot import/export.

03 /Role & attribution

The README identifies Pooya as the author.

04 /Technical architecture

A browser-side tool built with Next.js 16, React 19, TypeScript, Tailwind, and SVG; BroadcastChannel syncs only same-origin tabs and versioned JSON provides manual snapshot portability.

Graph design and validation flow
The graph and simulation are local; Compose output is a starter, not an automatic deployment
05 /Implementation details
  • 01Create gateways, services, AI workers, databases, and caches with dependencies.
  • 022D canvas and mobile-friendly rack view.
  • 03Detect isolated nodes, invalid endpoints, cycles, under-replication, and modeled bottlenecks.
  • 04Compute latency path only for acyclic graphs.
  • 05Local 2.2× stress simulation with baseline restoration.
  • 06Versioned snapshot import/export and Docker Compose starter generation.
06 /Engineering decisions
  • 01CPU/throughput/latency are simulated inputs, not real measurements.
  • 02BroadcastChannel is not remote collaboration or cross-device sync.
  • 03Compose output is a starter; review secrets, ports, networks, and volumes before deployment.
07 /Verification & evidence
  • 01Pages deployment for commit df05f90 succeeded on November 1, 2026.
  • 02The README has no consolidated recent browser/accessibility/performance test report.
09 /Capabilities & highlights
  • 01Create gateways, services, AI workers, databases, and caches
  • 02Detect isolated nodes, invalid endpoints, and dependency cycles
  • 03Calculate longest-path latency only for acyclic graphs
  • 04Validate JSON snapshots before replacing current state
  • 05Generate Docker Compose starters from valid graphs
10 /Scope & boundaries

The app is client-side: it has no live infrastructure telemetry, remote collaboration, server, accounts, or shared rooms. Throughput, CPU, and latency are modeled inputs/simulations, not measurements from real containers.