Product
Ship, govern and measure from one record
Lanestep ships the work your teams choose to Power Platform and Dynamics 365. A workspace holds your environments and tracks, and every part of it reads from the same record, so the release, the evidence and the reports agree.
Ship
Ship the work you choose
Each work item becomes a change that moves along its track, one checked step at a time. At Stage, you choose which changes go to Prod, one or many.
Whole solutions or single components
A change holds whole solutions or single components: a table, a column, a form, a view, a relationship, a flow, a web resource or a plug-in step.
One export, every environment
Lanestep exports each change once, as a managed and an unmanaged solution. What was tested is what ships. A rebuild makes a new export.
Tracks
A track is a path from a build environment through its test environments. Use a feature track and a hotfix track, or as many as you need.
One Stage, one Prod
Every track feeds the same release line: Stage, then Prod. Stage shows what it holds that Prod does not, and you pick what goes on.
Guards
Before Prod, guards check readiness, versions, older copies, retests, work of other changes, unmanaged layers, approvals and freezes. Each finding says what it caught and how to clear it.
Sync
When a release reaches Prod, Lanestep syncs it into every track it did not come from. It checks for clashes before the import, and a person decides each one.
Overlaps, flagged early
Lanestep flags changes that touch the same component as soon as they are exported, well before release day.
Rebuild and retest
When other work overtakes a change, Lanestep marks it Needs rebuild or Needs retest. A rebuild exports it again with the fixes from Prod, and a retest confirms it again in Stage.
Version numbers
Lanestep sets the version of each export. It refuses to import a solution older than the one an environment already holds.
Govern
Show who did what, who approved it and why
Governance is part of the release, not a meeting after it. Each release carries its approvals, its findings and its evidence.
Sign-in with Microsoft Entra ID
People sign in with your own Microsoft Entra ID, and every record names the person who made it.
Roles
Admin, Release manager, Maker, Tester, Approver and Viewer. Everyone can read. Roles decide what each person can change, and a refused action names the role that allows it.
Separation of duties
An approval counts only from someone who built none of the changes in the release. If a change is exported again after a decision, the decision is marked outdated.
Approvals by track
Set how many approvals Prod needs on each track, such as two for features and one for hotfixes.
Stage booking and the hotfix rule
A release can book Stage to keep other changes out. A hotfix can still take Stage, and changes that share its components are marked Needs retest.
Freezes
Stop deployments to chosen environments for a set period, such as a year-end close. An exempt track can still deploy.
Pass a finding, with a reason
Where your policy allows a finding to pass, the person who passes it writes why. Who, when and why stay on the release.
Audit trail
Every export, deployment, approval, passed finding and sync is an entry: who, when and what. Entries are added, not changed or removed.
Evidence pack
One document per release for the change board: the policy, the decisions, the findings, the work items, every deployment and the audit trail. Print it, save it as a PDF or download it as JSON.
Recover
Put things back where Dataverse allows
Dataverse does not roll back cleanly. Lanestep restores what it can from the record, and says plainly what stays and why.
Baselines
Each change that ships single components leaves a solution of its own. A baseline folds those back into your base solutions, one environment at a time, after checking that the source and Prod agree.
Compensating releases
A compensating release undoes a release. It restores the earlier version of each component the release changed, where Dataverse allows, taken from the record.
Insights
Measure what reached Prod
Delivery and risk come from the record, week by week, not from what people reported. Each delivery figure shows the median and the 85th percentile, and how many cases it is based on.
Delivery
How often releases reach Prod, lead time from a change’s start to Prod, time to restore after a failed deployment, and which releases a hotfix followed within a week.
Risk
The components behind the most overlaps, rebuilds and failed deployments, so you can see where work tends to go wrong.
AI suggestions
AI suggests, people decide
Lanestep can ask AI for three things. Each is marked as a suggestion and changes nothing by itself: a person decides what to do with it.
Release risk in plain words
A plain summary of a release’s risk for the approver, based on its guard findings, its overlaps and earlier changes to the same components.
Draft release notes
Draft notes from the work items in a release. A person reviews, edits and saves them.
An order for overlapping changes
A suggested order for changes that share components, based on their tracks and how far each has come. A person decides whether to follow it.
Work items
Keep the board you have
Work items stay in Azure Boards or Jira, where your teams already keep them. Lanestep links each change to its work item.
Title and state
Each change shows the title and state of its work item, as Azure Boards or Jira holds them.
A comment at each step
As the work reaches each environment, Lanestep posts a comment on the item, so anyone reading it sees where the work stands.
Never edited
Lanestep never changes the item itself. Its title, state and fields stay as your team keeps them.
Integrations
Works with the tools you run
Lanestep works beside the pipelines, checks and channels your teams already use.
Azure Pipelines and GitHub Actions
Deployments can run through your own pipelines, with their own identities. Lanestep starts each run, then checks that the environment holds every solution at its version.
A gate before Prod
Azure DevOps checks and Power Platform Pipelines can ask Lanestep whether a release may go to Prod. The gate answers from the guards, approvals and freezes, and changes nothing.
Teams, Slack and ServiceNow
Channels in Teams and Slack hear about approvals, failures, freezes and clashes, with a link to act in Lanestep. In ServiceNow, a change request follows each release.
See your own tracks in Lanestep
Book a demo to walk through your environments, tracks and change board with the team building Lanestep.