Huh, that is a very interesting problem to have. It's certainly not the scale or complexity or security or reliability requirements that make storing your data

Huh, that is a very interesting problem to have. It's certainly not the scale or complexity or security or reliability requirements that make storing your data difficult -- it's the choice of hosting technology! That sounds dismissive but I don't mean it that way. I'm sure you've chosen wisely. I just find the problem intriguing because I don't know of any obvious solution and it's not one of the common problems people have with persistence. I'm trying to think of what sort of stateful servers you might be using anyway that you can piggyback for this. Some ideas: - SSH to any Unix box really - Email - Web-based pastebin service with an API - Regular Twitter tweets - Something stored on whatever you are using to conduct the deployment - An image uploaded to imgur where the image data are the string you need - DNS records - Any web service where you have a user profile editable through an API you could use one of the profile fields to store the string The list is getting more stupid as I go so I should probably stop there. But if you have written the service such that you can reject a deployment unless you're sure it worked, you are technically free to use quite stupid ways to store the data because worst case the deployment just fails and the old code chugs on.