Run cufemlab against one of your motors.
A focused engagement: you send a motor brief, we deploy cufemlab on an RTX-class node, run the integrated magneto-thermal-mechanical pre-analysis, and deliver a signed report with full provenance — all within a fixed scope and timeline.
Three engagement models.
All tiers are by request. cufemlab is proprietary software — there is no public download. Pilots are scoped, priced individually, and operated under NDA on request.
Read-only access to documentation, sample notebooks, and the v0.3.0 benchmark report. For teams comparing methods and deciding whether to fund a pilot.
- Full documentation site
- Sample notebooks (download)
- Frozen v0.3.0 benchmark report
- Email Q&A within 5 business days
We deploy cufemlab to your workstation or a GPU node we provision, ingest one motor design, and deliver a signed report — magnetics, thermal, mechanics, and an integrated motor PDF.
- Hosted Docker image (RTX-class GPU)
- One integrated pre-analysis
- Signed report (PDF + JSON + Markdown)
- SHA-256 provenance on every output
- Engineering review call (60 min)
- 30-day exclusivity on findings
- Typical timeline: 2–4 weeks
Multi-motor programme, custom benchmark suite, on-prem deployment, or licensed integration into your CAD/PLM pipeline.
- Multi-month engagement
- Custom benchmarks & materials
- On-prem or cloud deployment
- Joint roadmap input on v0.4
- NDA available
- Dedicated engineering contact
What's in, what's out.
In scope
- One motor topology (induction, PMSM, SynRM — radial-flux 2-D plane).
- Magnetics (2-D, linear or B-H nonlinear).
- Thermal (transient, with conjugate heat if forced cooling).
- Mechanics (linear elasticity, rotor centrifugal stress, safety factor).
- Integrated verdict and signed report.
- One engineering review call (60 minutes) covering results and limitations.
Out of scope (this tier)
- 3-D simulation (deferred to v0.4 — quote separately if needed).
- Full Re>0 Navier-Stokes (v0.4).
- Eddy currents, full Maxwell, turbulence (out of cufemlab scope).
- ASME/IEC certification (not what cufemlab does).
- Production sign-off (use ANSYS / Maxwell / Star-CCM+).
- CAD import (v0.4 — geometry can be supplied as YAML in the meantime).
What you get at pilot close.
| Artifact | What it carries |
|---|---|
| Signed PDF report | Full verdict trail, cited references, declared tolerance, measured error per check, SHA-256 provenance hash. |
| JSON result file | Machine-readable verdict record; suitable for CI ingestion. |
| Markdown summary | Drop-in for pull-requests, reviews, or internal docs. |
| Notebook bundle | The exact notebook used to produce the run — re-runnable on your end. |
| Review call (60 min) | Walk-through of results, candid limitations discussion, v0.4 roadmap alignment. |
From brief to signed report.
Brief (week 0)
You send a one-page brief: motor family, what you want measured, available CAD/geometry, comparison data, timeline. We reply within 5 business days with a fixed scope, price, and timeline.
Run (weeks 1–3)
We deploy cufemlab on a GPU node, ingest your geometry, run the integrated workflow, and iterate against any internal sanity checks you supply.
Deliver (week 3 or 4)
You receive the signed report, the notebook bundle, and a 60-minute review call. Findings are exclusive to you for 30 days.
Honest about the cost.
cufemlab pilots are quoted per engagement. The Sandbox tier is free for qualified labs and academic groups; the Pilot tier carries a fixed fee covering engineering time + GPU node provisioning; Partner programmes are scoped over multiple months. Email info@secrotec.com for an indicative number for your scope.