So you can do local first with the `dolt_clone()`, `dolt_remote()`,`dolt_fetch()`, `dolt_pull()`, and `dolt_push()` procedures: https://docs.dolthub.com/sql-re

So you can do local first with the `dolt_clone()`, `dolt_remote()`,`dolt_fetch()`, `dolt_pull()`, and `dolt_push()` procedures: https://docs.dolthub.com/sql-reference/version-control/dolt-sql-procedures https://docs.dolthub.com/sql-reference/version-control/dolt-... as well as the `dolt_remotes` system table: https://docs.dolthub.com/sql-reference/version-control/dolt-system-tables#dolt_remotes https://docs.dolthub.com/sql-reference/version-control/dolt-... We have a ton of remote options: https://docs.dolthub.com/sql-reference/version-control/remotes https://docs.dolthub.com/sql-reference/version-control/remot... Right now, DoltHub (https://www.dolthub.com/ https://www.dolthub.com/) will still work as a remote but all the SQL there will be the MySQL version. Over time the Doltgres storage format may become more bespoke and we'll have to figure out how DoltHub will work.