We've been building an access gateway for the past few years. The first version was built in Clojure, and we rewrote it in Golang. But that's a whole other story.
The gateway has a new type of architecture that allows packet manipulation (one of the reasons for Golang), which basically means you can programmatically change contents of connections in real-time.
Therefore it enables a whole set of problems to be consolidated at the access gateway layer, like data access policies (DLP), review of critical operations before they run (Change Management), automate repeat operations (Runbooks) and more. And this is how we monetize the solution.
Because of that we're open-sourcing the core of the gateway under MIT license. And we're including enterprise features from other gateways and some unique and new options enabled by our architecture.
Our vision for the project is to do what nginx did for HTTP to the protocols we interact with infrastructure.
It is early days and there's lots to do on the documentation side and making it easier to get started. We're working on these, but I'm super excited to share it with you.
We've been building an access gateway for the past few years. The first version was built in Clojure, and we rewrote it in Golang. But that's a whole other story.
The gateway has a new type of architecture that allows packet manipulation (one of the reasons for Golang), which basically means you can programmatically change contents of connections in real-time.
Therefore it enables a whole set of problems to be consolidated at the access gateway layer, like data access policies (DLP), review of critical operations before they run (Change Management), automate repeat operations (Runbooks) and more. And this is how we monetize the solution.
Because of that we're open-sourcing the core of the gateway under MIT license. And we're including enterprise features from other gateways and some unique and new options enabled by our architecture.
Our vision for the project is to do what nginx did for HTTP to the protocols we interact with infrastructure.
It is early days and there's lots to do on the documentation side and making it easier to get started. We're working on these, but I'm super excited to share it with you.
Would love to hear any feedback, comments, critics, anything: https://github.com/hoophq/hoop