Typical DevOps handles code deploys in a single direction: from Dev to PROD, from lower environments to higher environments, and for this there are many well known solutions like Jenkins, Terraform, Octopus. But in the opposite direction the situation is not so good.

Yes, in many companies there are home-grown processes to copy databases from higher environments to the lower ones (with hiding/removing sensitive data) to reproduce problems, found on PROD. However, in complex scenarios an access to PROD is needed to find the root cause. Developers need at least logs. And in the Enterprise world it's all depend on the level of ~~paranoya~~ how sensitie the information is.

Thi is what we suggest, the project is to create a safe access method to the higher environments, combining easy friendly interface and interactivity with the full audit of all operations and controlled manner of what users can do and what they can't. The project is called Bell -Action at a distance, and a bearded guy on the logo is John Steward Bell, you know him if you had ever heard about the Quantum Entanglement.

Reverse DevOps, an invitation to project «Bell»