Skip to content
Learn · How it works

Four steps. No black boxes.

You keep control of your code, your decisions, and the reasoning behind them. Softinel adds the intelligence layer that has been missing.

Walk through it

Every stage in detail. Move through at your own pace.

Each of the four stages below is worth understanding on its own — they are where the differences between Softinel and a scanner actually live. Click the tabs (or use the arrow keys) to move through them.

Step 01

Connect your software

Softinel accepts a repository URL, a git snapshot, or an uploaded archive. The CLI can push straight from your working directory.

Only the code you send is analysed. Softinel never crawls upstream projects, and never fetches dependencies beyond the manifest declarations you already ship.

1 / 4 · arrow keys work too
git snapshotacme/paymentsSoftinelingest
What runs where

Where Softinel meets your infrastructure.

You can run Softinel entirely as a hosted platform or bring the heavy analysis inside your own network. Either way, your source code, contracts, and secrets never need to leave the environment you already trust.

  • ▸Hosted. Point Softinel at a repository or push a snapshot. Managed model, managed analysis, evidence returned to you.
  • ▸Self-hosted analysis. The model and analysis layer run inside your VPC; only aggregate metadata leaves the boundary.
  • ▸Air-gapped. A fully offline mode for environments where nothing may cross the perimeter.
Continue reading
See it in action

The interactive playground — pick a project and drive the same flow yourself.

Evidence system

The six fields every finding carries — and why.

Continuous verification

What happens when your software changes after the first verification.

Ready when you are

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.

Start modelling your software →Sign in