I&#x27;m not aware of any services with the simple API you&#x27;re looking for (neat idea), but there are a lot of more complicated solutions.<p>What are the key&#x2F;value durability requirements? (OK to drop values now and then, or does it need to keep them until the end of time?). Need backups? Do values expire, or do you have to expire them manually? Since you can&#x27;t enumerate or search, how do you delete things? Allowed sizes of keys and values, between bytes and terabytes? How far should it scale?  Shared namespace, or namespace per user? Do you need a latency guarantee? How low? Are you gonna use it for something important and need an SLA on the availability of the service as a whole?<p>A couple of &quot;nearby&quot; points in the solution space:<p>Amazon S3 is a KV store where the keys look like filenames and the values look like files. High durability, good scaling, pretty high latency. You could also obviously paper a KV store on top of ElastiCache or DynamoDB, which are going to have different properties.<p>Going low-level and implementing your own in say, golang would probably be the most fun though :p<p>Hard to say if we could use a SAAS KV store at work without a lot more technical detail on the solution. I&#x27;m having a hard time thinking of an app where you&#x27;d want a KV store, but not need a database or NoSQL store which you could use instead.