Roast my landing page for a key-value database service
http://kvdb.io
Hey all,
I'm curious what are the first things you think of when you visit https://kvdb.io - is the product description clear for the target audience? Do you feel like the terminal code samples above the fold help or detract from explaining the product?
Thanks!
Hi Amir,
My biggest question is why wouldn't I use Redis (Memcache, etc)? It's everywhere, super stable, super scalable, hosted on every major cloud provider and has an easy to use cli tool as well as libs for dozens of languages.
Andrew, I agree with you, it's bound to be the most common question to come up.
My thesis is that there is room for a service like KVdb for those that want more features than Redis and the like offer, but don't want to deploy a NoSQL document database. I plan on offering a Redis protocol-compatible interface to KVdb so developers can leverage existing Redis client libraries. Server-side scripting (currently Lua, JavaScript to come) is also supported, so you can build custom logic inside KVdb ("serverless" if you will): https://kvdb.io/docs/scripting
The biggest advantage I would say is that you don't have to deploy Redis or use a client library. KVdb is accessible from anywhere you can make an HTTP request.
The database space is very fragmented and typically people look for a specific database to solve a use case. I would put on the site what the best things your database is good for: is it for storing logs, serving very fast product information, etc.
For me, this is clear (and compelling!):
Then I look over to the right and see the curl commands. Looks simple. I wonder if there's some kind of management dashboard. I see the delete bucket command, and wonder about how access control works.
I then looked around for pricing. I'm the kind of person who hesitates to even go through the learning curve for a new dev tool if I can't see what the pricing is, because I get annoyed with lock-in. I clicked on the pro plan mentions but didn't see pricing.
So you've got my attention! It looks like something I'd try, especially now that I want to start new projects quickly. (I'm learning Svelte this week, for example.) But if I found your page based on some link somewhere, I'd have just closed the window when I couldn't see what future pricing commitment I'd be making.
Salim, thanks so much for your insightful reply!
It's buried in the docs at https://kvdb.io/docs/api/#buckets but you're right, I should briefly outline this on the landing page for those who are curious! I feel like there's a balance to be struck in not being excessively detailed on the landing page...
I intend to go with a freemium model, but I'm not quite sure about charging for the service yet since there isn't enough usage to determine what the right price point would b. But now that you mention it, I see how it could be a deterrent to even trying the service out in the first place.
Great points, I'm going to take them to heart and implement changes very soon :)
Hi Amir !
Product description is clear.
I'd add some white space to the left and right side in header to have same center - aligned structure as sections below.
Good luck with your project, Amir !
Thanks for the feedback Romarto, those are good points that my developer mind wouldn’t have ordinarily considered, I’ll make the changes :)
This comment was deleted 7 years ago