Run the real plugin loop locally
Shorten the gap between change and feedback by executing your Dataverse logic on your machine before you queue another cloud deploy.
Dynamics 365 / Dataverse
XrmGhost gives Dynamics teams a local-first workflow for debugging, validating, and documenting Dataverse behavior before the next cloud deploy slows the investigation down.
No account is required to install the CLI. Use the quickstart when you are ready to validate the workflow in your own environment.
Prefer to inspect the package first? See the XrmGhost.Cli package on NuGet.
XrmGhost gives Dynamics teams a local-first operating layer for debugging, validating, and documenting Dataverse behavior without slowing every iteration down to a cloud deployment cycle.
Shorten the gap between change and feedback by executing your Dataverse logic on your machine before you queue another cloud deploy.
The CLI, host bootstrap, and environment commands give every developer the same starting point, from the first evaluation to a team-wide rollout.
Turn a flaky cloud-only issue into a reproducible scenario you can inspect, rerun, and explain to the rest of the team.
XrmGhost is built for the moments when the platform is fine, the code looks fine, and the delivery loop is still the slowest part of the job.
Deploy-to-debug delays
A simple plugin change still means waiting for packaging, import, and a fresh repro in the tenant.
Run the same logic locally first so the cloud deploy only happens after the behavior is already understood.
Shared sandbox uncertainty
One team's investigation can collide with another team's test data, customizations, or release window.
Work from reproducible local scenarios that isolate the issue before you coordinate a shared validation pass.
Hard-to-explain regressions
A bug disappears by the time someone else looks at it, so the team debates symptoms instead of causes.
Capture the scenario, rerun it on demand, and share the exact command path that produced the failure.
Bootstrap the local runtime with the documented setup flow so every developer starts from the same verified tooling baseline.
Use XrmGhost to run the failing path locally, inspect the behavior, and turn the repro into a repeatable command sequence.
Move from one-off debugging to documented team practice with reusable command groups, attributes, and source-of-truth docs.
The launch story is simple: reduce waiting, keep investigations reproducible, and give every customer-facing release a cleaner proof trail.
Shorten the path from hypothesis to verified fix by moving the first debugging pass off the tenant and onto your machine.
Give support, QA, and engineering a shared repro path instead of a screenshot, a guess, and a meeting invite.
Validate the workflow on one environment first, then carry the same operating model forward without retraining the team.
XrmGhost comes from real delivery frustration: too many plugin changes, too many slow feedback loops, and too much time spent explaining bugs that should have been easy to reproduce.
The product direction stays grounded in practical documentation, local-first workflows, and a source-of-truth mindset that helps technical teams explain what happened instead of debating what might have happened.
Browse the documentation hubEvery option below is built from the live pricing catalog, with amounts and purchase cadences derived from the latest Dataverse price-list items.
Standard
€20 / mo
€200 / yr
Local development and debugging for D365 plugins and Custom APIs.
2 purchase options
Pro
€35 / mo
€350 / yr
Everything in Standard, plus live environment connectivity and catalog management.
2 purchase options
Contact us for volume discounts (min. 25 seats): contact@xrmghost.tech
Not if you want a unit test suite: that is what FakeXrmEasy is for. XrmGhost runs your compiled plugin against one scenario, out of process, so your coding agent can write, run and fix it without deploying. Many teams will want both.
Read the full answerYour compiled plugin, in a .NET Framework 4.7.2 host shaped like the Dataverse plugin model. The context and the data it reads come from a scenario file; on Pro, reads can come read-only from a live environment.
Read the full answerYes. Plugins are .NET Framework assemblies, and the host that runs them is a .NET Framework 4.7.2 process, so a run needs Windows x64. That includes the build agent, if you use XrmGhost in CI.
Read the full answerWith the XrmGhost skills, it writes the scenario, runs xg run, reads the traces and reports what failed, then fixes the code or the scenario and runs again, telling you what it changed. Works with Claude Code, Copilot CLI, Codex CLI and others.
Not to start: runs with scenario data work without an API key, within a 60-day evaluation. xg license status shows Unlicensed until you add a key. Standard covers the local loop, production use included. Pro adds read-only live data, environment management and CI.
No plugin code, no plugin output, no Dataverse records. A machine registration for licensing, and usage telemetry you can turn off with XRMGHOST_TELEMETRY=0. Every field is documented.
Start with the guided quickstart, validate the workflow in your own environment, and keep the reference docs close when you are ready to roll the operating model out across the team.