Scorpiion

Good point, there are of course different levels.

I was thinking of a fully private deployed within the customers cloud account connected to the software provider via Private Service Connect or PrivateLink and then either only available inside the customers private network or only via their own firewall. The point being that it's not publicly exposed.

I'm curious what people think of BYOC (bring your own cloud) as an option offering to customers or buying it as a customer. Looking at Northflanks website they list it as an offering, I presume those customers are not affected by the breach.

What are your opinion on the concept? Growing trend that should be encouraged or a mistake for most startups? Would you choose one provider over the other because of it assuming price was about the same?

I get that this is often a super expensive "call us" option today, but in theory it doesn't have to be, so for the sake of discussion let's assume it can be delivered at a reasonable cost for the provider at reasonable price for the customer.

If people from Northflanks is reading this, I'm sorry for the incident and I hope you recover as soon as possible.

Looks like a nice service, it also sounds like something the SaaS companies who's pricing information you are showing would not like.

I'm curious how you look at that? Are there any legal risks for end users to share this type of information via your site? I'm thinking if the SaaS providers have some legal statements about not sharing prices (similar to how certain database providers don't allow sharing of database benchmarks).

Thanks for writing this one Simon, I read it some time ago and I just wanted to say thanks and recommend it to folks browsing the comments, it's really good!

Thanks a lot for sharing bob1029, nice explanation and justifications, much appreciated!

Hi bob1029, very interesting to hear about your experiences and point of view. Easy to forget the impact of how easy it's to sell an end product/service based on your selection of database (it does not always matter of course). I have thought about this as well, no one (?) will question if your app/service uses postgres but if you say sqlite I assume there will be some more questions.

Would you mind sharing some numbers of what you consider an "aggressive RPO", and what RPO number sqlite+litestream can still handle? Of course, it will depend on the use case, but if you would do a rough estimate. I think it could be helpful for a lot of readers.

I'm not an iPhone user myself, but recently run into the fact that SwiftKey has been deprecated on iPhone when helping a friend.

Does anyone here know the details of why SwiftKey was depreciated? Did iOS change their APIs or permissions somehow or what was the reason?

I'm curious, what does "connector hell" mean in this context from a practical point of view?

Interesting and glad to hear, I think it makes a lot of sense in this case!

Very interesting, tempted to apply to the company as this sounds very promising and fun to work on...

I'm curious about the business side of things, to give some context, some open source models that startups use today are:

1. The "open core" model, Gitlab being a good example. They try to split features that are open or closed/enterprise depending on the buyer.

2. The AGPL model, Mongodb used to do this, today a popular example is Grafana and their collection of products.

3. The Apache + cloud backend model, the core being standalone working with Apache license while building a value added managed service. I think this is what Synadia is doing with NATS.

4. The "source available" model, not really open source, but worth mentioning as it's very popular recently. Examples Mongodb, Elastic, Cochroachdb and TimescaleDB. This is often combined with open source such that some parts are open source, others source available.

With this as a reference Nikita, how would you explain how Neon thinks in regards to licensing and eventually building a healthy business? It's obvious a managed database service is the money maker, but how do you think around compeditors taking the project and building managed services without or with minimal code contributions? I'm sure you guys have thought a lot about this, would be interesting to hear some thoughts and reasoning for or against different options.

(Note: This is not meant to be an extensive explanation of these business models just a high level overview. If I have miscategorized some company above feel free to correct me in a comment.)

FYI this is from 2018.

I thought it was something released recently but saw on Github that it's from 2018.