No cloud surface to evaluate. No always-on data feed. No live telemetry. Nothing to whitelist, no SaaS to security-review, no SOC-2 exception to negotiate. In practice, IT teams have consistently found this the simplest part of the procurement conversation — not the hardest.
SCModeling installs and runs entirely on the modeler's machine. The model — your network, your sourcing strategy, your costs, your demand — lives in files on disk that you control with your normal file infrastructure. Nothing is uploaded to us. There is no SCModeling cloud where your data goes; there is no live connection to our servers for the product to function.
"Where does our network data live?" — On the modeler's machine. That's the architecture, not a feature flag.
The implications follow:
Windows / macOS. Signed binaries. Standalone — no runtime dependency on our cloud. The modeler runs it like any other desktop application.
No forced auto-updates pushing changes during quarter-end. New releases are announced; you update when it's the right week.
Models are files on the modeler's machine. Wherever your laptop / desktop already complies, this complies — by inheritance, not by configuration.
The model is a file. If your laptop is backed up, your model is backed up. No new backup system to integrate.
Shared model files via your existing Git, OneDrive, SharePoint, or shared-drive infrastructure. Optional managed collaboration layer that does not store model contents — only versions metadata.
Models live in files you control, not in a vendor account. Standard handoff applies. License is re-issued to the replacement modeler.
In our experience, once an IT or security reviewer sees that there's no SaaS surface and no live data feed, the conversation typically resolves quickly:
→ "Is there a cloud component?" No, the product runs locally. There is no SCModeling cloud for the product to call home to.
→ "Does it phone home with our data?" No telemetry of model contents. The product can check for available updates if the modeler enables that; nothing else leaves the machine without an explicit user action.
→ "What about the public website / sandbox at scmodeling.com?" That's a marketing surface with sample-data demos. It is not the product. The product is desktop software that runs offline.
→ "Sign our MSA / DPA / NDA?" Yes. We've signed the standard ones at large enterprises.
If your IT team has a specific compliance regime (regulated industries, defense-adjacent, M&A-active perimeter), we'd rather talk through your specifics on a call than make blanket claims here. Direct outreach is the fastest path.
If you'd like the deployment story laid out for your specific IT environment — Windows-pinned, macOS-pinned, BYOD, regulated, restricted-network, anything — request access and we'll walk through it directly. There are no PDFs to download first.
Request access → Or try the live sandbox