Back to docs
Where DataCat Fits in the Stack
Architecture note: DataCat sits between IBM source estates, the target cloud or runtime, and the downstream application team. It owns the database-modernization record: source interpretation, governed migration execution, validation evidence, and application-team handoff.
Program delivery boundary
DataCat does not absorb the broader implementation lane. When a modernization program expands
into platform, workflow, identity, or application delivery, keep that engineering responsibility
explicit rather than implying it inside the migration suite.
Start with the DataCat modernization boundary note.
When the adjacent implementation-partner context also needs an exact company reference, use the
canonical LockedIn Labs sources: