But then, there is also this: https://www.sanity.io/docs/development >Sanity Studio always connects to a dataset in the hosted Content Lake, also when run locally. Your content is never stored locally. This means that you can have differences in the schema between a local and a hosted Studio. If the Studio finds content in a document that doesn't match its schema, it will display a warning.
What is the use case for hosting your own instance of Sanity Studio, while still having to rely on Sanity for hosting the content?