Getting Started
Start with the generic CLI path, then continue into a concrete worked example.
Planning software in Rust
Build planning systems your team can inspect, control, and run.
SolverForge helps teams turn scheduling, routing, allocation, and dispatch rules into production software. Domain models, constraints, and runtime control stay in ordinary Rust code, so the behavior remains explicit from the first prototype to the running system.
Runnable app scaffold
Readable domain constraints
Hospital, lessons, delivery, and FSR examples
Write constraints like you write code
Readable rules, explicit tradeoffs, real application shapes.
Model shifts, routes, tasks, workers, vehicles, and inventories as ordinary application code. SolverForge keeps rule definitions, score analysis, and solver control close to the domain types your team already understands.
let required_skill = ConstraintFactory::<Plan, HardSoftDecimalScore>::new()
.shifts()
.filter(|shift: &Shift| shift.employee_idx.is_some())
.join((
Plan::employees_slice,
equal_bi(
|shift: &Shift| shift.employee_idx,
|employee: &Employee| Some(employee.index),
),
))
.filter(|shift: &Shift, employee: &Employee| {
!employee.skills.contains(&shift.required_skill)
})
.penalize(HardSoftDecimalScore::of_hard_scaled(1_000_000))
.named("Required skill");
Open source implementation
Solver core, app scaffolding, UI controls, and routing helpers you can inspect.
solverforge-cli
Scaffold a neutral project shell, then grow the domain with generators.
solverforge-ui
Ship scheduling views, retained-job controls, and embedded frontend assets.
solverforge-maps
Model matrices, route geometry, and map-backed planning systems.
Core Solver
Inspect the zero-erasure runtime, phases, moves, and score analysis tools.
Use cases
Four planning surfaces you can watch, inspect, and run.
Hospital coverage, school timetabling, delivery routing, and field service routing. Each case carries its data shape, its constraints, a narrated walkthrough of the running app, and annotated screenshots of the same retained solve.
688 shifts / 50 employees / 28 days
Hospital
Coverage, qualifications, rest, availability, preferences, and fairness across dense workforce schedules.
300 lessons / 20 teachers / 10 rooms
Lessons
Two scalar decisions per lesson: which weekly timeslot fits the timetable, and which room fits the class.
82 deliveries / 10 vehicles / ordered routes
Deliveries
Route ownership, capacity, time windows, recommendations, and REST workflows on one inspectable surface.
48 visits / 6 technicians / road routes
Field service
Technician routes, skills, parts, shifts, territories, time windows, and road geometry in one retained workflow.
Proof before a call
Review the docs, code, releases, and examples before trusting the work.
The documentation shows the operating model, the source shows implementation quality, the examples show behavior, and the release notes show active maintenance. You do not have to wait for a sales conversation to understand how SolverForge works.