Yes, those commands write the variables to a file, though you could also make a system call instead from within your app if you didn't want them in a file or en

Yes, those commands write the variables to a file, though you could also make a system call instead from within your app if you didn't want them in a file or environment variables. The language SDKs (including ruby) wrap the envkey-source binary, which is where all the decryption and verification logic lives: https://docs-v2.envkey.com/docs/envkey-source https://docs-v2.envkey.com/docs/envkey-source There is an -m/--mem-cache flag that you can pass to envkey-source that makes it work just as you're describing. It keeps the variables in RAM and listens for updates, keeping them all up-to-date.