Use this link if are still using Runops: https://use.runops.io

We are starting a new phase. Runops was born to bring more autonomy to developers.

We do that by transparently baking security and compliance into tools devs use to perform sensitive operations. So, instead of revoking access to keep systems safe, admins should feel comfortable granting more access because of the strong guard-rails created by Runops.

We launched the product and it skyrocketed.

We kept integrating Runops to existing tools aiming to integrate into developers workflows As we kept adding features, users kept growing,

But something didn't feel right.

Product grew too complex. Due to the high number of features, new users had a hard time understanding and getting started. The integration to existing tools was working fine, but not great. Some users needed a better experience.

So we decided to make a risky move.

Instead of trying to integrate with existing tools, we would re-implemente them in a better way.

So we shifted focus to refactoring the whole product. We spent multiple months without working on new features.

Existing users were happy with the current solution. But we wanted to bring it to the next level.

It paid off, and today we are launching hoop.dev!

A simple and secure connection between developers and the cloud shouldn't be a static straight line, it should be a continuous flowing hoop.

FAQ

How can I get started with hoop.dev?

Head over to our Quickstarts

Is Runops going to continue working?

Yes. hoop.dev is a revamped version of Runops. Most features were migrated. Runops will continue to operate normally and we'll be in contact with our customers to align migration strategy. It should be straightforward as we'll do most of the things in the backend.

What should I do if I use Runops today?

Nothing. We'll reach out to align next steps. hoop.dev is a reorganization of Runops features in a simpler interface and simplified concepts.