Upgrading from Runops to Hoop.dev


Welcome to the upgrade guide from Runops to Hoop.dev. This migration brings a series of improvements to your experience. In this document, we detail how these enhancements introduce new functionalities and require some collaborative effort due to significant code restructurings and component rewriting.

Rebranding and Upgrade: Runops and Hoop.dev

We want to clarify that Runops and Hoop.dev are the same entity; we've only undergone a marketing rebrand. This transition from Runops to Hoop.dev is more than just a name change—it's a significant upgrade of the existing solution you've been using. Our commitment to improving your operational efficiency remains our top priority, and this upgrade is a testament to that commitment.

Benefits of Migrating to Hoop.dev

  • Users Directory Integration: Integrate your database access management with Active Directory, Google Workspaces, Okta, or any SSO. Grant and revoke access effortlessly from managed groups.
  • Faster and Better UX: Enjoy a completely redesigned UI and UX, crafted from the ground up. We've included the most requested features by our users, offering a more intuitive and efficient interface.
  • New Agent Infrastructure: The agent infrastructure has been rewritten to optimize our most significant use case: native access with database clients. This results in enhanced performance and reliability.
  • Next-gen Runbooks: Our advanced versioned automation surpasses ad-hoc executions. It brings reliability and consistency in operations, enriched with features like rich inputs, indexed session contents, and more, for smoother and more controlled operational tasks.

Step-by-step Guide

Step 1: Account Creation

The first step in migrating to Hoop.dev is creating a new account at hoop.dev. Contact our team in the chat inside the app to get your account created if you don’t already have one. Initially, this account will be without data. For substantial data transfers, our team can assist with internal migration. For smaller data sets, manual duplication of your resources within the tool is recommended. You'll find that the setup process is now much simpler than with Runops.

Step 2: Updating Agents

The next step is updating your agents. The Runops agents have evolved into what we're calling Hoop.dev agents. The application remains largely the same, but it will now require authentication tokens from your new Hoop.dev account. For increased security, Hoop.dev requires a token per agent. Runops agents are 1 token for all agents. These tokens are essential for updating your system with a new Docker image and environment variable. Once updated, the solution will be operational and functional.

Step 3: Testing Connections

After setting up, test the connections to ensure everything is functioning as expected. Users accessing the new address should be able to interact seamlessly, similar to their experience with Runops.

Step 4: User Transition and Monitoring

The final step involves releasing the new system to users. The change in their experience will be minimal, but the improvements in Hoop.dev are significant. Post-release, monitoring the system to ensure a smooth transition is important. The redesigned user interface in Hoop.dev is more intuitive, and users should naturally adapt to and benefit from the new features.

Support and Contact

For any questions or assistance during the migration process, feel free to directly contact the Runops/Hoop.dev team. We're here to ensure a smooth transition.

Parallel Operation and Migration Importance

We are providing an extended migration window to make this transition as smooth as possible. As of October 16, 2022, newly-created accounts no longer have access to Runops.
During the migration, your Runops and Hoop.dev instances will operate in parallel. This ensures no disruption to your current operations until your Hoop.dev instance is fully functional. Post-migration, Runops will be phased out. As we cease updates for the older version, it's crucial to complete this migration promptly. Please make plans to migrate to Hoop.dev prior to the EOL date of June 1st, 2024., with only critical updates being released until then. The new Hoop.dev solution is where all new features and updates are being delivered.