Asprova APS vs DO.Impact Core

Asprova APS creates production schedules for factories and manufacturers, integrating sales, manufacturing, inventory, and purchasing plans across multiple items and processes. Its synchronized planning and capacity tools use standard times down to the second and can account for individual machines, molds, and personnel. Planners can create multiple scenarios, adjust parts of an existing plan manually, and reschedule. Charts and graphs show line overloads, delivery delays, and load differences by day, week, or month. Asprova connects to relational database tables and CSV files; users can configure mappings and differential imports and exports. The maker says it can integrate with most ERP, production management, MES, shop floor control, and legacy systems. Optional modules include Sales, Purchasing, KPI, Time Constraint MAX, Resource Lock, Event, and Optimization. The product is paid, with pricing on request; implementation, training, consultation, and integration may add costs. A trial edition can be used with e-learning exercises, but no trial duration is stated. It is self-hosted Windows software. The maker says a maintenance contract is required to upgrade Asprova.

DO.Impact Core is a self-hosted, single-user web app for small manufacturers that covers strategy, commercial work, operations, people, and execution. Its operations module includes daily management, shop-floor workflows, scheduling over 0–12 weeks, supply chain, SIOP, NPI, quality, and risk, alongside a library of more than 250 industrial KPIs. Execution includes A3, 8D, 5 Whys, fishbone, and DMAIC problem-solving methods, plus a Gantt actions timeline. Operators can use a touch-friendly /floor mode, and the TitanScale Template company is pre-loaded to populate modules at first launch. Core is released under the GNU Affero General Public License v3.0 and stores data in the user's own database, machine, or private network, with no accounts, subscriptions, or tracking. Self-hosting requires Bun or Node.js 20+, the Supabase CLI with Docker, and a local or hosted Supabase project. Local single-user mode disables row-level security; the maker says not to expose it publicly without an authentication proxy.