Guided onboarding
Configure one supported environment and work through one example with your team.
$5,000one-timeSee the scopeA defined path from workload qualification to an accepted deployment. Buy the integration you need, without repeating work already included in an engineering program.
Plan a deploymentOptional, fixed-scope engagements. Start with the help you need, not a mandatory enterprise program.
Configure one supported environment and work through one example with your team.
$5,000one-timeSee the scopeEvaluate one agreed workload against a defined baseline and decide what is worth changing.
$15,000one-timeSee the scopeAddress one tightly scoped bottleneck or standard integration, with a defined engineering-time cap.
$30,000one-timeSee the scopeScopes are confirmed before work begins. Engineering is optional; work already included in a larger engagement is not billed again. Infrastructure, taxes and ongoing production software rights are separate.
One bounded workload, a comparison baseline, results and an acceptance report.
Agree the release, target environment, interface responsibilities, acceptance tests and operational documentation. The statement of work identifies the implementation changes and the handover owner.
Integrate one application into a defined environment, test acceptance and complete the operational handover.
Agree the release, target environment, interface responsibilities, acceptance tests and operational documentation. The statement of work identifies the implementation changes and the handover owner.
Connect several applications with shared measurements, deployment work and an agreed support boundary.
Agree the release, target environment, interface responsibilities, acceptance tests and operational documentation. The statement of work identifies the implementation changes and the handover owner.
A substantial SpinForge workflow integration with deployment, acceptance testing and documentation.
Agree the release, target environment, interface responsibilities, acceptance tests and operational documentation. The statement of work identifies the implementation changes and the handover owner.
Partner-product interfaces, packaging, qualification and support handoff. Distribution rights are agreed separately.
Agree the release, target environment, interface responsibilities, acceptance tests and operational documentation. The statement of work identifies the implementation changes and the handover owner.
Customer-controlled infrastructure, private deployment or a partner product, according to the licensed release and selected interfaces.
Qualify a source format, execution path, returned state and independent-check boundary. Website integration is not evidence of an already deployed multi-tenant solver service.
Explore the scopeScope the interface, accepted inputs and operating responsibilities—not just a collection of algorithms.
Connect the selected SpinForge products to compatible AI clients, coding tools and agent workflows through their available MCP interfaces, with CLI and headless alternatives.
06Add a bounded optimization, configuration-checking or re-planning capability to the product your customers already use. Keep your user experience; integrate the computational capability behind it.
09Use the appropriate SpinForge capability in a supported customer-controlled environment. Choose CPU execution where the product supports it and acceleration where the workload justifies it.
Commission the model, integration and acceptance work needed for your task. Existing products stay independently available.
Commission one supported decision model, a scoped conflict analysis and a comparison of permitted repairs.
02 / Scoped customer programCommission a revision-aware workflow that keeps models, assumptions, results and evidence connected as inputs change.
03 / Scoped customer programCommission a bounded performance improvement with source identity, numerical acceptance and the appropriate checking evidence.
Joint configuration, decision-sensitive computation, checked memory, useful future options, exact reformulation and evidence-led improvement. Explore the role of every product and agree a matched system evaluation.
Customer-specific integration opportunities—not added software entitlements or universal performance claims.
One capability. A connected workflow.
A team to put it into practice.