Tracked Workspaces

Finally know what's deployed
where — and when to update it.

Real-time visibility across every environment. Every install, sync, and update logged automatically — so you always know what's running, when it changed, and who touched it.

Start Free Trial See How It Works →
zsh — prod-client-12 
➜  prod-client-12 ipm init --associations 4baf8889 --local-name "prod-client-12"
IPMHub Cli v0.14.0
Initialization of workspace '/src/prod-client-12' started...
Workspace initialization completed.

➜  prod-client-12 ipm sync
IPMHub Cli v0.14.0
Started synchronizing 3 packages with sync mode 'KeepAllChanges'...
Package 🛡 acme/landing-zone version 2.1.0 synchronization completed in ⚡ 41 ms.
Package 🛡 acme/networking version 1.4.2 synchronization completed in ⚡ 25 ms.
Package 🛡 acme/monitoring version 3.0.1 synchronization completed in ⚡ 18 ms.
Synchronization completed.
Real-time
Version visibility across every workspace
Full history
Every revision logged — nothing lost
SOC 2
Audit-ready trail out of the box
1 query
To answer "what ran on March 15th?"
The reality today

You can't manage what you can't see.

Every environment drifts. Every deployment is a question mark. And when an auditor or client calls, the answer is always the same: someone starts digging through logs.

01
"Which version is actually deployed in production?"
Spreadsheets, Slack messages, manual checks. Nobody really knows the live state.
02
"A client called — we need to roll back. Which version were they on?"
No point-in-time record. Rollback becomes a guessing game.
03
"Auditor wants a compliance report for last quarter"
2 weeks of archaeology through git logs, tickets, and memory. Every audit is a fire drill.
How Tracked Workspaces works

Three steps to complete
deployment visibility.

01 — Create
Create a tracked workspace in the IPMHub portal
Give it a name and link it to an environment — production, staging, or a named client. The workspace record lives centrally, ready to receive state from any linked local environment.
# Portal: Organization → Tracked Workspaces → Create Name: prod-client-12 Association ID: 4baf8889 ✓ Tracked workspace created
02 — Link
Run ipm init --associations in the local environment
All subsequent package operations are recorded automatically. No deployment process changes required — just one command to activate tracking from that point forward.
➜ ipm init --associations 4baf8889Workspace initialization completed.
03 — Track
Every install, sync, and update is logged automatically
See real-time state from the portal or CLI. Query the full history at any point. Answer compliance questions in seconds — not weeks.
➜ ipm syncPackage 🛡 acme-msp/azure-landing-zone version 2.1.0 synchronization completed in ⚡ 41 ms.Package 🛡 acme-msp/networking-base version 1.4.2 synchronization completed in ⚡ 25 ms.Synchronization completed.
What you get

Complete lifecycle visibility,
no extra tooling required.

Real-time version visibility
See the exact package and version running in every workspace, updated on every operation. No staleness, no guesswork.
Complete revision history
Every install, update, and sync recorded with timestamp and actor — the full lifecycle in one place, always queryable.
Multi-workspace overview
View all environments — clients, teams, regions — in one dashboard. Filter by package, version, or status to find drift instantly.
Point-in-time queries
Answer "what was deployed on March 15th?" in one query — no git archaeology, no ticket spelunking, no memory required.
Drift detection
See which workspaces have fallen behind the latest version before it becomes a support call. Proactive, not reactive.
SOC 2 / compliance-ready
Immutable audit log satisfies SOC 2, PCI DSS, and ISO 27001 audit requirements out of the box — no extra tooling or manual documentation.
In production

From infrastructure blindness
to complete visibility.

MSP · 40+ client environments
Per-client visibility changed support completely

Before Tracked Workspaces, answering "what version is the client running?" meant checking multiple systems, asking colleagues, and often still being uncertain. Now the answer is one command. Support calls that used to take hours to diagnose resolve in minutes.

Minutes
To answer version questions (was hours)
0
Rollback guesses — exact version always known
"We always know exactly what's deployed where. Support calls that used to spiral into archaeology now resolve before the client gets off the phone." — Senior Platform Engineer, MSP
Enterprise platform team · 50+ dev teams
Audit prep: 2 weeks → 1 day

Quarterly compliance audits used to mean two weeks of manual reconstruction — pulling git logs, cross-referencing tickets, interviewing engineers. Tracked Workspaces turned that into a single query. The audit trail was already there, immutable and complete.

1 day
Audit prep (was 2 weeks)
96%
Compliance visibility across all environments
"Compliance is one query away now. The auditor asks a question, we run a query, we have the answer. What used to be our most stressful quarter is now routine." — Platform Engineering Lead, Enterprise
Common questions

Tracked Workspaces answers.

What is a tracked workspace?
A named link between an IPMHub workspace record and a local deployment environment. Every package operation in that environment is recorded centrally — installs, updates, syncs — with timestamp and actor, forming an immutable history of that environment's state.
Does this require changes to my deployment process?
No. Run ipm init --associations Run ipm workspace link once per environmentlt;idRun ipm workspace link once per environmentgt; once per environment. After that, all existing ipm add, ipm sync, and ipm publish commands automatically log to the tracked workspace. No pipeline changes, no new steps, no extra configuration.
What compliance standards does the audit trail support?
SOC 2, PCI DSS, and ISO 27001. The immutable log records who did what, when, and to which version — sufficient for most audit requirements without any additional tooling or manual documentation effort.
Can I track workspaces across multiple organizations?
Yes. Each workspace is scoped to an organization but you can have multiple organizations and view cross-org state from the portal dashboard. Useful for MSPs managing separate client organizations or enterprises with distinct business units.

Ready for full infrastructure
visibility?

Stop guessing what's deployed where. Start free — full access from day one, no credit card required, cancel anytime.

Start Free Trial Book a Demo
➜ ipm init --associations 4baf8889Workspace initialization completed. ➜ ipm syncStarted synchronizing 3 packages with sync mode 'KeepAllChanges'...Synchronization completed.