01What kind of product is Spare?
An AIGE solution (AI-Generated Engineering). AIGE engineering agents work across CAD, CAM, CAE, EDA and other industrial software, replacing the multi-engineer, cross-software workflows that typically take several days of coordination. One instruction, one person, output files ready to use. Activated per application, such as Spare CNC Programming or Spare PV Plant Design.
02How is this different from ChatGPT or Codex?
ChatGPT and Codex generate scripts and recommendations that a person still has to run, passing files between tools. Spare reads and writes models, runs simulations and produces drawings directly, completing the entire workflow in sequence.
03Which software and versions are supported?
500+ industrial software products are covered, and every workflow lists the software it uses. Connectors are configured for the software and versions your company actually runs.
04Does it work with software that has no open API?
Yes. Connectors use APIs and MCP first; where no interface exists they use the software's own scripting and macros, such as AutoLISP, VBA, NX Open or Python add-ins; UI automation is the fallback.
05What happens to existing processes and templates?
Configured to match your current processes. Title blocks, layers, tool libraries, post-processors, report templates and company standards are imported into the knowledge base and used as is.
06Which large language models are used?
Claude and GPT by default; regional providers are available in other markets. Private deployments can connect to a designated provider, and offline deployments use a local model.
07Can workflows not listed here be supported?
Yes. Submit the workflow's inputs, the software involved and the output files, and Spare will propose an integration plan.
08Can processes outside the preset workflows be supported?
Yes. Deep customization and integration covers your industry, discipline, internal standards and actual workflows, connecting company software (including in-house and niche tools), templates, title blocks and layers, tool libraries, post-processors, company standards and past projects. The process is: map the workflow, connect software and standards, customize the workflow, then pilot and go live.