[dfragnito]

Great question.

We have shut down our consulting business and are all in on SFSQL. We will not be offering a FOSS solution. Our plans are to provide SFSQL via a subscription based self hosted model. Delivered initially as a docker container.

SAAS offerings would be provided through infrastructure provider partners. We would prefer not to be the SAAS provider of SFSQL. We have other business models that we plan to deploy but we don't want to get ahead of ourselves.

[rmbyrro]

I don't mean to be negative, but just two cents of feedback:

I believe (could be wrong) many developers would be worried about using this.

Seems to me you're a small shop (?). AWS can get away with a proprietary DB API like DynamoDB's. They are big and can provide strong assurances.

Since SFSQL is just starting out, by a small shop, it would be a high risk to rely on it being a closed source, proprietary API.

Might be worth thinking about how you're going to address such concerns. Must have something really strong to support.

[dfragnito]

In a self hosted model developers would host SFSQL on their own infrastructure, which could be AWS, Google, Azure, DO, etc.. There is no reliance on us. Yes we are maintaining the API and underlying implementation. Software is a Service thus the subscription model.