DitaBase is a company. Dit is an open source technology. DitaBase is developing dit at the same time as attempting to profit from it. Think of this as though a company were building git at the same time as GitHub.com
The dit file type and all essential tools will always be open source. DitaBase itself will make other tools and services that will not be open source, like freemium features on the website and freemium editors with more features. DitaBase will also host a marketplace for dit classes, where open and closed source code can be found and used in dits, either for free or for validation as a service.
Dit can be made to work with any format, even totally custom formats. By breaking down a format into objects, anything can be described. If it can be written down in binary, then scripts can be written that work with it's functionality.
This does not mean all formats are supported out of the box, or that DitaBase will support all of them.
But it does mean the following:
We realize the irony of any new format inherently making the problem worse, but dit is not trying to make a format that covers everyone's use cases. That is probably impossible.
Dit is not a format, it is a container. It's trying to be a bridge between other formats, and that means it relies on them heavily. You can't write data in dit format, only wrap data in a dit. For example, you can imagine how you might list some data in JSON vs XML. There is no such format for DitaBase, only a blank payload which is your responsibility to fill with a format.
Maybe format X will turn out to be better than Y. To dit, it doesn't matter. It only wants to make sure that switching between X and Y is as easy as possible. The only competing standard that dit introduces is whether to use a container like this or not. And at the moment, dit is the only one.