Dolt SQL implements the MySQL dialect, and is compatible with its wire protocols. This makes it easy to migrate to using Dolt for MySQL users, and others since most SQL implementations are relatively similar. There are two obvious motivations for migrating to Dolt:
to implement version control features in the application that would be cumbersome to build using traditional SQL
to store and track the lineage of the underlying application data
Building version control features into an application is complicated. It requires implementing brand new schemas that work alongside application code. These schemas are often not a natural fit for SQL. By making robust version control native to the SQL layer, Dolt enables application developers to focus on the application layer and exposing version control features, and frees them from complex database schema design and implementation work.
An example of an application where versioning can deliver business value is Nautobot. Nautobot is an open source "Network Source of Truth and Network Automation Platform." The project is sponsored by Network to Code, a provider of network automation solutions. You can read more about Network to Code's motivations for integrating Nautobot and Dolt here.
This is the simpler case. Some applications used to managed configuration data benefit from robust versioning, and the ability to instantly rollback to historical versions. Or application owners may simply want a history for audit purpose. In this case the application simply sits on top of Dolt and periodically snaps a commit into the Dolt commit graph for later retrieval and analysis.