My landing page is live! Feedback?

Hey @daveagill!

Thanks so much for taking the time to review our landing page, and providing very thorough and useful feedback! As mentioned to others below, I would love to get your updated opinion on the next version incorporating everyone's feedback here, once it's ready - will ping when it's up.

Just to provide quick answers to some of your questions, in case anybody else runs into the same thing:

• This is a SaaS offering for now. We are considering a self-hosted option down the line.
• The pricing is still very much WIP, so we'll refine the tiers as we get user feedback during the beta. For now, a database cluster counts as a single "database" for the sake of pricing. We believe all production systems should have resiliency, and we therefore don't want to penalise customers for that in the pricing.
• As mentioned in one of the threads further below, we'll release documentation on the exact queries and permissions used by the connector once we open-source it. But as a quick answer, we currently require access to the statistics tables (e.g., pg_stat_user_tables, pg_database etc. for Postgres).
• No actual application data is sent to us, and we'd like to keep it that way for security/privacy reasons. If we do decide to capture it later for some very useful feature, we will make it opt-in. We only grab statistics on things like tables, columns, indexes etc., and for slow query monitoring, we only receive parameterised/anonymised queries.
• The platform is hosted in Europe, but we are considering offering multiple regions in future for data protection concerns. However, given that we don't receive any application data, we feel that this is not a pressing concern.
• We'll definitely look at adding a more prominent section on general security of the platform and connectors - it seems to be a recurring question in the comments here.

Will see how we can better bake all the above into the landing page and documentation.

Thanks again! :)

Hey @naskalator!

Thanks so much for taking the time to review our landing page, especially for going the extra mile and giving us a video walkthrough!

Some very useful feedback in there, which correlate very well with some of the other points of feedback here. I'm glad to see that we're already working on the majority of your feedback as part of our next iteration, which we're planning to launch this weekend.

As mentioned to others, I would love to get your thoughts on our next iteration - will ping here once it's live :)

Thanks again!

Thanks, @steffenbleher! Good suggestion - will give it some thought whilst we're busy with the next iteration.

Hey @Gav!

Thanks for taking the time to review our landing page and adding to the below feedback - some great additions to the list for our next iteration!

As mentioned to others below, I would love to get your feedback on our next revision assuming you have the time - will ping here when it’s ready :)

Thanks again!

Hey @TheMusician!

Thanks for taking the time to run through our landing page, and for your very kind feedback. I'm very glad to hear that this would have potentially solved some sleepless nights for you - it certainly would have done the same for us, which is why we were inspired to build DBSupervisor!

I would love to extend a beta invite to you once we onboard the next round, and get some deeper feedback given your previous experience. Will drop you a message as soon as we're ready to see if you're keen :)

Thanks again!

Hey @mirkonasato :)

Thanks for taking the time to review our landing page and giving us your feedback!

We've also intermittently seen the performance issues with the image carousel - will look into it and get it solved.

Good point regarding security - we do vaguely touch on this in the "How it works" page, but we can and should definitely focus on this a lot more. In most cases, customers will be using our (soon-to-be) open-source connector, which runs within your infrastructure/VPC and only reports a limited set of statistics to our API. This way, we never directly interact with your database, nor do we hold any of your credentials. We'll release documentation on the exact queries and permissions used by the connector once we open-source it, and customers can of course checkout the code and do their own due diligence if required.

You may have seen that we also do have the option of bypassing the connector and directly connecting to your database, but we're still questioning the popularity of this approach given security concerns like you've raised. We may choose to remove it and avoid the privacy/legal implications altogether.

I'd love to get your feedback on version 2 of the landing page, once we incorporate all the feedback - will ping here when it's ready.

Thanks again!

Hey @YosifG!

Thanks for the great feedback - some very useful points there!

Would love to get your input again for version 2 once it's out, assuming you're happy to give it another look - will ping here when it's ready :)

Thanks again!