Editions
Editions
Section titled “Editions”XrmGhost ships in two editions. Standard is the local-first foundation: run and debug your Dataverse plugins and Custom APIs on your own machine. Pro includes everything in Standard and adds read-only integration with live Dataverse environments, so a local run can read real data instead of mocked data.
Both editions share the same core workflow — author a scenario, run it locally, inspect the result. The difference is where the data a run reads comes from.
Standard
Section titled “Standard”Standard covers the full local development loop for Dataverse server-side code.
- Run plugins and Custom APIs locally. Execute your server-side C# on your own machine, in a runtime shaped to match the Dataverse plugin pipeline. (Support for custom workflow activities — CWA — is on the roadmap.)
- Headless execution. Run a scenario and read the result straight away — ideal for a fast write-run-fix loop, for automation, and for CI.
- Line-by-line debugging. Attach a debugger to your own code as it runs locally — in Visual Studio, Debug → Attach to Process onto the XrmGhost host — and step through your plugin exactly as you would any local program. No deploy, no remote profiler.
- Scenario-driven data. The data a run reads is supplied by the scenario itself (mocked data), so a run is fully self-contained and reproducible.
Use Standard when you want to develop, debug, and verify Dataverse plugins and Custom APIs locally with data you define.
Pro includes everything in Standard, and adds live integration with real Dataverse environments.
- Read-only access to live Dataverse environments. This is the defining Pro capability, and it is strictly read-only: XrmGhost reads from the environment only to satisfy the queries your code makes during a local run, and never writes anything back. Your live data is never modified.
- Environment and connection library. Register, organize, and switch between multiple Dataverse environments and connections, so you can point a run at whichever environment you need.
- Live data instead of mocks. You design your scenario, pass the real id of the specific record or user you care about, and run your code locally — but every read query (
Retrieve/RetrieveMultiple) resolves live against the environment. You no longer have to mock the data the code reads; XrmGhost fetches it from the real environment as the run executes.
This is the auto / live data source described in Using the Skills: on Standard a run reads only mocked scenario data; on Pro it can read live, read-only data from a configured environment.
Use Pro when you want to reproduce and debug real, live cases locally without hand-building the data — for example investigating a production issue against the very environment that produced it.
On the Pro roadmap
Section titled “On the Pro roadmap”- Scenario from a trace log. Generate a runnable scenario directly from a Dataverse trace log, turning a real, live incident into a local run with even less manual setup — less work for a human, and less for an AI agent, to debug a real case.
Choosing an edition
Section titled “Choosing an edition”| If you want to… | Edition |
|---|---|
| Run and debug plugins / Custom APIs locally with data you define | Standard |
| Read live, read-only data from real Dataverse environments during a run, and manage multiple environments | Pro |
Pro is a superset of Standard: everything you can do in Standard, you can do in Pro.
XrmGhost is distributed for evaluation, so you can install it and try the local workflow before activating a Standard or Pro license — see Getting Started.
Related pages
Section titled “Related pages”- Overview — what XrmGhost is and why it exists
- How It Works — the local-first execution model
- Using the Skills — how a run uses mocked vs live data day to day
- Getting Started — installation and first-run guidance