Skip to main content

Vittorio Distefano

Founder of SolverForge. I build optimization systems, developer tooling, and production software around hard technical constraints.

Primary work SolverForge
Domains Optimization, Systems, Applied AI
Approach Selective, Founder-led

Work
#

I build systems where the easy approach stops working: planning problems with real constraints, technical products needing sharper runtime shape, and AI-assisted systems with solid boundaries underneath.

Optimization and planning
Systems engineering
Applied AI
Rust / Python / Ruby
Optimization and planning
Scheduling, routing, allocation, and combinatorial systems where the model matters as much as the implementation.
Systems engineering
APIs, runtimes, language boundaries, migrations. Structural decisions that keep ambitious software legible.
Applied AI
AI as part of a system, with real orchestration, reliability, and product design.
Architecture and delivery
Work where architecture, developer experience, and delivery constraints have to line up.

SolverForge
#

Start here for the clearest view of the work.

SolverForge is the strongest public artifact here: a constraint-solving project where the modeling, runtime, and product tradeoffs are visible.

  1. Continuity

    Production

    SolverForge carries forward production constraint-solving work after an upstream ecosystem shift. That continuity ties the work to real users, not just greenfield experimentation.
  2. Native Rust core

    Architecture

    A Rust solver focused on type clarity, runtime performance, and a public surface that stays comprehensible as the system grows.
  3. Ecosystem surface

    Proof

    Docs, quickstarts, demos, and blog posts turn the project from a codebase into something people can actually evaluate and use.

Where to look
#


Background
#

I have worked across consulting, product engineering, research, migrations, data-intensive systems, and AI MVPs.

That includes building data pipelines processing hundreds of thousands of daily events, contributing to research platforms at the University of Bern, shipping tooling and interfaces, and years around systems where the wrong abstraction becomes expensive quickly.

The throughline: I am comfortable where hard domains, ambiguous tradeoffs, and technical responsibility meet.


Contact
#