01
Scheduling And Rostering
Shift schedules that respect union rules, shift limits, coverage requirements, and fairness constraints — with logic your operations team can actually inspect.
Built in Public. Delivered by the Architect.
Optimization that doesn't hide its logic.
Most vendors deliver a black box. We deliver the constraint logic your team can read, argue with, and own. Built on SolverForge — the open-source optimization framework forged from operational necessity, not product assumptions.
What We Solve
Planning problems that outgrew their workarounds.
You already know you have a constraint problem. The question is whether your current solver (or spreadsheet) will tell you *why* it made each decision.
02
Routing And Allocation
Vehicle routing and resource allocation where the "why" behind each dispatch matters as much as the dispatch itself. No black-box optimizations.
03
Timetabling And Operations
Conflict-free schedules for schools, manufacturing, conferences — with explainable constraint violations and human-readable output.
04
Product-Embedded Optimization
Solver logic inside your SaaS or API that your engineering team can extend, debug, and version — because they can read the constraint model.
In Practice
154 jobs. 14 furnaces. 22 crew members.
A production heat-treatment scheduling system in active use. 154 jobs scheduled across 14 furnaces — chamber, pit, aluminum, mobile hearth — with 22 crew members across 4 shift types. Thermal limits, changeover rules, and process constraints modeled as readable logic. Operators see exactly why each job lands where it does.
01
Multi-Constraint Optimization
Furnace capacity, thermal limits, changeover rules, due dates, and priority classes (standard/urgente/express) — all modeled as interacting constraints. The solver optimizes; the logic stays readable.
02
Workforce + Assets
22 crew members across 4 shift types (Mattina, Pomeriggio, Notte, Riposo). Furnace capacity meets labor availability. Both modeled as interacting constraints — not separate spreadsheets.
03
Domain Fluency
Tempra, Rinvenimento, Cementazione, Nitrurazione — we model the actual heat-treatment processes, not generic "jobs." Temperature ranges, soak times, and thermal compatibility rules built in.
04
Ownable System
Built on open-source SolverForge. Their engineers can extend it without vendor lock-in or support tickets.
Production schedule: 154 jobs, 14 furnaces (chamber, pit, aluminum, mobile hearth), 22 crew members across 4 shifts. Thermal limits, changeover rules, and priority classes enforced. Score visible. Italian interface.
How We Work
Constraint logic first. Implementation second.
Before we write code, you see your constraint model. You can argue with it, refine it, and approve it. Only then do we build. The result: systems your team understands, not vendor magic you inherit.
Discover
Map your operational rules, edge cases, and business logic before touching code.
Model
Translate your constraints into a readable, arguable specification. You see what you're buying.
Build
Implement the solver layer on the open-source SolverForge framework. Transparent. Auditable.
Own
Your team can extend, debug, and modify. No vendor lock-in. No support ticket required.
Open By Design
Built in public. Auditable by default.
SolverForge AI is the commercial practice on top of solverforge.org — the open-source optimization framework. Every system we deliver is built on public code your engineers can inspect, fork, and extend. No proprietary black boxes. No hidden logic.
See The Logic Yourself
The framework is public. So is the process.
# Clone and run the quickstart
cd solverforge-quickstarts/rust/employee-scheduling
# See constraint logic in plain Rust
cargo run --release
Server running at http://localhost:7860
Schedules generated with readable constraints
No vendor magic. Just logic you can read.
Start The Conversation
Bring your constraints. We'll map them first.
Before we write code, you'll see your constraint model. Argue with it. Refine it. Approve it. Then we build a system your team can actually own. No black boxes. No vendor magic. Just logic you can read.
Discuss Your Problem