mirrord

nput, configuration, and state from the cloud. While mirrord can be used in a lot of ways, our ideal use case is for it to be used for concurrent work on a shared, mature development or staging environment. Instead of maintaining multiple environments, each with its own state, maintenance, and cloud costs, organizations can now leverage a single well-maintained production-like environment for use by multiple developers or teams. mirrord is written in Rust, and the technology behind it is quite interesting (and we actually wrote some blog posts about it, see in our company blog [1]): - mirrord injects itself into the executed process, hooking most of the libc APIs, then decides what to run locally and what to run remotely - This lets us run only a specific process in the context of the remote environment, unlike similar solutions which use VPN or edit system files - In order to hook functions, it uses the fantastic Frida framework As for our business model, we plan to launch a managed service to complement the open-source offering of mirrord. The service is intended to help you manage the use of the product in a team/enterprise context. We would love your feedback, and would appreciate your support by: - Trying out mirrord [2]! - Joining our Backend Engineers Discord community [3] - Telling your friends - Contributing to our codebase or opening issues [4] Let me know what you think! [1] https://metalbear.co/blog/ [2] https://mirrord.dev/docs/overview/quick-start/ [3] https://discord.gg/pSKEdmNZcK [4] https://github.com/metalbear-co/mirrord