The CMS will have to rely on some database at some point. This is where the actual money-maker comes in: we'll make this package free to implement and open source, but we'll offer a headless CMS package independently, to compete with Storyblok.
On the client-side, however, the idea is to write your components just one time and have them automatically generate the UI in your CMS, which will be self-hosted even though the content itself will not be. This will give us a unique advantage over Storyblok by maintaining the philosophy of separating the content from the implementation, yet bringing the code definitions on both sides closer together to reduce correlating effort in multiple places.
The CMS will have to rely on some database at some point. This is where the actual money-maker comes in: we'll make this package free to implement and open source, but we'll offer a headless CMS package independently, to compete with Storyblok.
On the client-side, however, the idea is to write your components just one time and have them automatically generate the UI in your CMS, which will be self-hosted even though the content itself will not be. This will give us a unique advantage over Storyblok by maintaining the philosophy of separating the content from the implementation, yet bringing the code definitions on both sides closer together to reduce correlating effort in multiple places.