Modern software systems
rarely fail all at once.
They drift.
System Drift is an independent research publication studying how organizations accumulate platform dependency, concentrate operational risk, and lose reversibility inside the infrastructure they rely on.
Lenses for reading dependency structure. System Drift publishes no dependency scores or rankings.
Recent publications from the institute
Long-form reports, dependency analyses, and operational essays — produced independently, without vendor sponsorship.
The quiet capture of organizational workflows
How small integration decisions compound into platform-defined operating models — and why exit becomes structurally harder long before anyone decides to leave.
Identity providers as single points of governance
When a single identity layer mediates access to every internal system, governance and availability become the same surface.
When SaaS pricing becomes infrastructure policy
Seat, usage, tier and commitment models create economic signals that can shape access, architecture and supplier concentration — read against published vendor documentation.
Observability stacks and the new lock-in surface
Open standards have made telemetry portable. Queries, dashboards, alert logic and operational knowledge are a separate question.
A directory of the platforms whose dependency surfaces we document
Each profile describes where dependency can form around a platform. Profiles do not score organizations: actual dependency is organization-specific, and System Drift publishes no numerical dependency rating.
Microsoft 365
Amazon Web Services
Salesforce
Snowflake
Okta
GitHub
Atlassian
Google Workspace
Documented changes with potential dependency implications
Published observations are based on traceable public sources such as vendor documentation, regulatory disclosures and documented incident reports. System Drift records changes where there is a credible dependency or operational implication.
Two publications, two scopes.
System Drift’s research focuses on software dependency and operational change: the platforms, workflows and controls that shape how organizations run their systems.
Drift Observatory is a separate independent publication. It examines wider structural changes and emerging patterns across technology and infrastructure — a broader remit than the dependency research published here. The two publications are not affiliated, and they do not share a monitoring system, research database or editorial process.
Five lenses for analyzing how organizations become dependent on the systems they use.
Dependency Concentration
How much organizational activity depends on a small number of platforms, suppliers, or control points.
Reversibility
Whether a system can realistically be discontinued or changed while maintaining acceptable operations.
Governance Surface
Where approvals, permissions, policy enforcement and audit are technically implemented.
Operational Capture
How a workflow can become difficult to separate from the platform it runs on.
Exit Complexity
The work, dependencies, constraints and resources involved in leaving a system.
We study modern software the way meteorologists study weather systems — patiently, structurally, and without selling umbrellas. Our work is independent, evidence-based, and written for the people inside organizations who can still steer.
System Drift accepts no vendor sponsorship, publishes no rankings and no dependency scores. Research is published periodically; there is no fixed publication schedule.