My landing page is live! Feedback?
Hey, fellow Indie Hackers! 👋
@jasonrussell and I have been working on DBSupervisor for the last few months and would appreciate your honest feedback on our landing page: https://dbsupervisor.com
We have over 15 years of software engineering experience between us, mostly having worked in small to medium-sized startups. We were constantly hit with scaling pains as usage grew, particularly within the database layer. These problems would silently grow until users started complaining about slow performance, and we would typically have to spend expensive startup hours debugging them from scratch.
In a startup, it’s hard to prioritise setting up actionable monitoring of your database health - you typically need to keep all your focus on building and scaling your product. Whilst many existing infrastructure analytics platforms capture raw database metrics, these often require lengthy setup, and are difficult to digest and formulate actionable fixes from.
That’s why we decided to build DBSupervisor, a drop-in solution to proactively monitor and address database-related problems within your application. The setup is super simple, and we make some intelligent, opinionated, and actionable suggestions on how to keep your database and product running smoothly.
Please check out our landing page, and drop us your feedback below 😎
Thanks!
It's a nice clean looking website and makes a good first impression.
While I don't love the MaterialUI theme for a website personally (fine for the product itself though) as a b2b offering it wouldn't really detract.
I would say ditch the image carousel. Those images were very slow to load anyway. Instead put those product images where the SVG images are. I want to see what these features look like in your product, I don't need to see a lady standing next to a lighthouse 😉
Also suggest to put a signup / request-beta-access button either in the header bar or on the signin page.
I actually wasn't sure if it was just for SQL database or which ones were supported, I control-F searched for "SQL" but found nothing. I eventually found it in the FAQ at the bottom of the homepage but there was no mention of this in the how-it-works and felt that it could even be in the hero section of your homepage. I.e. don't just say "database", say "SQL databases".
Other questions I had that took a bit "too long" to find the answers for or I did not see answered at all:
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:
pg_stat_user_tables,pg_databaseetc. for Postgres).Will see how we can better bake all the above into the landing page and documentation.
Thanks again! :)
https://www.loom.com/share/8ae64b8cfed748eb856a05238338e0a7 I hope you find this useful!! @allistercsmith
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!
Happy it was useful! For sure, just tag me again once the next iteration is out!!
If you have a few minutes to share, I'd also appreciate some feedback on ours haha. We just revamped our site at (still undergoing) at https://upgraded.dev/version-test
looks great! I'd give your sections a bit more space to breathe. Will make them stand out more
Thanks, @steffenbleher! Good suggestion - will give it some thought whilst we're busy with the next iteration.
I like the site, it's got a nice clean design and it's easy to follow. The service is a great idea, and it's a bargain compared to some DBA services I've worked with before.
A couple of suggestions I don't think have been mentioned yet:
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!
Sounds good.
I love the idea. Coming from a technical role in a startup, we had exactly the problem you described: we had postgres as one of our databases, set it up, set monitoring up and thought we are good. Hower, being a startup, our DBA was not an expert for postgres and he overlooked critical warning signs in the db raw monitoring data. Having opinionated suggestions and alerts is critical.
There are some open source solutions out there (like pghero), but your solution seems much much better looking and easier to use and has much more hints as it seems.
So I'm going to bookmark your tool for my next startup.
It was mentioned before: connecting to the database from a cloud service is a no go. You mentioned your open source agent, which runs on the infrastructure: great idea and a must.
If you don't have this agent yet, a tiny bit to gain trust is providing your users a single static IP of your client, so that they at least can whitelist your ip. It's only a tiny piece, however shows that you thought about it.
Good luck with your journey. I'm happy to follow your journey, as this has huge potential. And would have solved a lot of sleepless nights for me, in the past.
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, yes I am happy to assist (and if my new startup goes beyond validation also pay ;-) )
The landing page looks pretty clear to me, well done!
The images in the carousel under "All you need to know about your database" were pretty slow to load; there was like a 2-3 seconds delay before displaying each one of them. I see they're dynamically generated by Next.js, so it might just be that I was the first to request them after a new version was deployed or something.
I think the main concern I would have as a potential user is: what about security? If it works by letting your service connect to my database and have full access to it that's a pretty important consideration, so it may be worth covering it.
(Along with privacy, that is a legal requirement in some parts of the world.)
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!
That sounds great!
Some of my first impressions:
CTA should be a unique colour to ensure it stands out. it blends in with the page right now.
The "Request Beta Access" flow takes too long. It's like 6-7 questions, and a bunch of clicking. Also, I wouldn't really feel comfortable sharing things such as my monthly revenue with a random form- this is informatin you should get out of a call
Make it easy for me to sign up- an email field + "sign up for beta" CTA is enough.
I would love to see some formal data about how DB problems can affect my business- e.g. "Every year, businesses lose over 1B dollars from database problems.".
I understand you can't really do a case study right now, but I would do one and slap it on the landing page as soon as possible. If you can get a user to say "Using DBSupervisor, I analysed expensive queries and saved 200 dollars a month" it'd be sick.
Hope this helps :D
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!
No worries, would be happy to have a look :D