MOVEdot

MOVEdot is aimed at a specific and expensive problem: engineering organisations that own mature tools and mature data, and still lose weeks to correlation runs, durability post-test analysis and report assembly. What makes it credible rather than another AI-in-engineering deck is that the agents are wired to the applications engineers already run. The homepage runs live task cards showing an agent operating Adams, then VI-grade, then MATLAB, then Canopy inside a single vehicle correlation campaign, with progress and status per job. The blog record backs it up: 5,000+ multibody simulations dispatched overnight with no human in the loop and a surrogate model as output; a sim-to-test correlation agent launched July 2026; a Canopy Simulations correlation campaign where every parameter is checked against logged test data; and a durability case study covering one prototype SUV, four terrain blocks and 93 channels with post-test analysis ready the next morning.The second differentiator is team context. A personal assistant helps one engineer; MOVEdot Projects are shared workspaces with one brief that is summarised daily and injected into every chat, shared instructions, and published chats usable as context. From there, an analysis that works becomes a Workflow — versioned code with revisions, dependencies and file bundles that runs on a schedule or a trigger without an agent present. The Telemetry Channel Extractor shown on the site is described as a base dependency for downstream telemetry workflows, which is exactly the pattern a second vehicle program wants to inherit.Governance is unusually well specified for this category. Deployment into your own AWS, Azure or GCP account, bring-your-own model keys on zero-data-retention endpoints, SOC 2 Type I, encryption in transit and at rest, managed key rotation, per-user grants and revocations via user groups, an audit log spanning chats, runs and key rotations, and per-team credit accounting with per-turn cost visibility and limits. That last pairing matters: per-turn cost visibility only exists because MOVEdot is metering model usage, so budget controls are part of the operating model rather than an afterthought.The honest constraints. MOVEdot assumes data plumbing you may not have — the company itself frames it against no-code simulation tools by saying it expects Parquet files, databases and API access to build on. The underlying model is not named anywhere in the material we could see, so you cannot evaluate model provenance from the public site. And the value is workload-specific: if your slow part isn't correlation, durability post-test analysis or multi-run comparison, the platform has less to grip. Note too that engineering teams at the Smart Prototypes Summit said the run itself is rarely the slow part — which is MOVEdot's own thesis, and also a reminder that the gain shows up in analysis and reporting hours, not in solver speed.