Agenda
01
Where the migration stood still
02
The agent-audited rollout plan
03
Six weeks, in numbers
Specialized beats generic now.
Why the old platform couldn't flex
Bent to fit generic SaaS
Dispatch rules lived in spreadsheets because the platform couldn't express them.
Single-vendor lock-in
One cloud provider held every workload — no leverage, no fallback.
Audits happened once a quarter
By the time an issue surfaced, three sprints had shipped on top of it.
Before and after
| Before | After | |
|---|---|---|
| Audit cadence | Quarterly, manual | Continuous, agent-run |
| Provider | Single vendor | Self-hosted core, portable |
| Dispatch logic | Spreadsheet macros | Purpose-built service |
Six weeks
{{ r.week }}
{{ r.title }}
What we run
One config, continuous audit
agent: audit-nightly
trigger: on_merge
checks:
- policy: soc2-controls
- policy: cost-guardrails
- provider: self-hosted-first
on_finding: open_pr(review: platform-team)Six weeks, in numbers
{{ m.value }}
{{ m.label }}
“
We stopped bending our dispatch logic to fit software that was never built for freight. Now the software is ours, and it's audited every day, not once a quarter.
Erik Solheim · VP Operations, Nordic Freight AG
Who ran this
{{ t.initials }}
{{ t.name }}
{{ t.role }}