Not a video. You drive this one.
Below is a fully working sample of what Softinel builds from a real repository. Every click is honest — no scripted paths, no hidden state. Try to break it.
Not a video. You drive this one.
A working sample of what Softinel builds from a repository — pick a project, click through the map, and try the simulations. Nothing here is scripted; the graph reacts to what you do.
The model is being built. Once it settles, click a node or run a simulation to see what Softinel would surface.
Everything you see is deterministic: same click, same result. In the real product, Softinel builds this same map from your repository, keeps it updated as you change code, and signs every finding with evidence.
A short guided tour, if you like.
Click the gateway node
See every service the request path touches — from public entry to Stripe. The 'called by / calls' list is the same view an engineer would want.
Click crypto-utils@2.1
Notice it's a package, not a service, and see who depends on it. This is where a vulnerability enters the system.
Run 'Show vulnerability blast radius'
One CVE fires red through every service transitively affected. The blast radius is the neighbourhood, not the file.
Run 'Change file: payments/webhook.go'
See the exact set of services and tests that need re-verification. Every other verdict stays valid.
Connect your software. Softinel builds the model.
One canonical, connected model of your software. Every question about security, correctness, architecture, and change becomes a query against it — with evidence attached.