3 ms·
Show HN: K(v)aas. Key-Value as a Service. Simple API to Persist short-lived Data
Hey HN!
I built K(V)AAS last night, after having to deal with some programmable banking API that couldn't persist data across sessions.
I didn't want to create a new db or backend for such a simple task, but also couldn't find an existing service that simply accomplishes this.
I'm keen to hear what you all think! Current usage is entirely free. If there is a need, I'll build it out a bit more.
- ttymck 3y agoIs $key global across all accounts? Is it scoped based on your authentication? I didn't want to sign up, but was curious.
- FrikkieSnyman 3y agoIt's scoped based on API key. Keen to hear why you are hesitant to sign up?
- quickthrower2 3y agoYou need to say more about how auth works on the landing page. I see you have answered another commenter on this question. Also something like this needs a “docs.” subdomain. I like the idea, especially the REST interface with no package installs required. I had a similar idea myself coming from “what is the simplest possible firebase” point of view. I like the idea of using this from a backend. Then the lack of granular permissions will not matter as much as the backend will be the “bastion”. Your competition might include the KV offering from Vercel. I probably wouldn’t sign up as you are selling infra and I need to know you will be around, and you have a reliable service etc.
- FrikkieSnyman 3y agoThis is great feedback, thanks! I've updated the site to make the documentation available without having to be logged in - https://www.kvaas.cloud/documentation https://www.kvaas.cloud/documentation As far as reliability - I've not built my db, and K(V)AAS simply leverages other cloud services. So it should be as reliable as those! But if you ever run into something, you can reach me at frikkie@splirrit.com and I'll pick it up!