Simplify testing

Easily spin up multiple copies of your existing Hypernode environment, and start testing. Done? Deploy your changes and easily terminate your Brancher node again.

Try Hypernode Brancher

Use Brancher to your own advantage

Improve your tests

Increase the quality of testing for new functionalities or performing upgrades.

tap to show more

Pay per minute

Pay only for what you use and avoid unnecessarily high costs.

tap to show more

Integrate in CI/CD

Make Brancher part of your deployment process and make sure you always have low-threshold testing.

tap to show more

Involve your customer

Involve customers in the testing process to increase the quality of deployments.

tap to show more

Prevent errors

Avoid mistakes by testing well in advance.

tap to show more

Test individual features

Test new functionalities faster by temporarily spinning up new environments.

tap to show more

How to use Brancher

Unlock the possibilities

  • Combine Deploy and Brancher. Launch a Brancher node, deploy your feature branch with Deploy, conduct thorough testing, and automatically remove the Brancher if all tests are successful.

  • Hypernode CLI. To simplify the use of Hypernode Brancher, we have incorporated a user-friendly interface into the Hypernode CLI. This interface can be accessed using 'hypernode-systemctl brancher'.

  • Hypernode API. Brancher is fully integrated with our API, allowing you to automate creation or deletion of temporary Hypernodes using API tokens. Use your favorite deployment/automation tool, like Github and Bitbucket.

  • Control Panel. Create or terminate Brancher nodes with just one click. In your Control Panel account you can also find all information on total time used, amount spent on Brancher nodes, and previously used Brancher nodes.

Use case: MySQL update

Because you cannot downgrade MySQL version, it’s crucial to test properly before updating. On a development Hypernode it can be done only once and can deviate from your production node. This is where Hypernode Brancher comes in, by creating a copy of your production Hypernode it provides an identical state for testing and you have as many attempts as you need.

 

Want to know more?

Use case: MySQL update

Because you cannot downgrade MySQL version, it’s crucial to test properly before updating. On a development Hypernode it can be done only once and can deviate from your production node. This is where Hypernode Brancher comes in, by creating a copy of your production Hypernode it provides an identical state for testing and you have as many attempts as you need.

 

Want to know more?

Use case: Acceptance server per pull request

It’s common to have a separate acceptance server for each pull request, allowing colleagues or customers to test changes before merging them into the main branch. This can be achieved by creating a separate Github Actions workflow that creates a new Brancher node based on the current pull request and leaves a comment with the Brancher node URL on the pull request. This simplifies testing in a real environment.

Use case: Acceptance server per pull request

It’s common to have a separate acceptance server for each pull request, allowing colleagues or customers to test changes before merging them into the main branch. This can be achieved by creating a separate Github Actions workflow that creates a new Brancher node based on the current pull request and leaves a comment with the Brancher node URL on the pull request. This simplifies testing in a real environment.

Use case: updating PHP

Dedicated Servers are generally delivered within an hour. The delivery time depends on the type of dedicated server you want to purchase. For a specific delivery time of one of our products, we advise you to contact our specialists. Get a hold on one of our specialists with the button below!

Use case: updating PHP

Dedicated Servers are generally delivered within an hour. The delivery time depends on the type of dedicated server you want to purchase. For a specific delivery time of one of our products, we advise you to contact our specialists. Get a hold on one of our specialists with the button below!

Essential for your workflow

Quickly set up a test environment based on your production or development Hypernode using Brancher. This allows for safe testing of new releases without affecting your production environment.

The environment is configured with the same settings as your other environments, and you can choose to import your database or not.

Use Brancher for testing PHP/MySQL/Varnish versions, database migrations, application updates, and other changes to your webshop.

Essential for your workflow

Quickly set up a test environment based on your production or development Hypernode using Brancher. This allows for safe testing of new releases without affecting your production environment.

The environment is configured with the same settings as your other environments, and you can choose to import your database or not.

Use Brancher for testing PHP/MySQL/Varnish versions, database migrations, application updates, and other changes to your webshop.

Pay per minute

Hypernode Brancher differs from a development node in its pricing model. The amount of time spent on a Brancher is tracked and calculated at a rate of 0.01 per minute per Brancher. Once the Brancher is deleted, an overview of the minutes spent is sent to you.

You can view both active and past Brancher runs, and at the end of the month, an invoice line is added to your Hypernode invoice for the total minutes spent in Hypernode Brancher.

Pay per minute

Hypernode Brancher differs from a development node in its pricing model. The amount of time spent on a Brancher is tracked and calculated at a rate of 0.01 per minute per Brancher. Once the Brancher is deleted, an overview of the minutes spent is sent to you.

You can view both active and past Brancher runs, and at the end of the month, an invoice line is added to your Hypernode invoice for the total minutes spent in Hypernode Brancher.

Curious about Brancher? Let us know!

Frequently asked questions
What is the difference between a Brancher node and a development Hypernode?

A development node is perfect for developing one webshop at a time, running all the single tests you can think of, and giving the customer (the shop owner) access during development. A Brancher node is perfect for testing multiple branches simultaneously without needing to buy multiple dev nodes for at least a month, integration and automation tests without a lingering state at your development node and also giving the customer (shop-owner) access during development.

love Brancher! I might use it as my sole production environment!

Of course, you can do this and nobody is stopping you. But there won’t be backups. Also, the settings you change in the control panel won’t be reflected as well on these nodes. If your use case is production, you need a normal Hypernode. Want advice? We can help.

Do you anonymize the Magento database copied to Brancher with Masquerade?

You can test your software with personal data from your production database if you throw it away when you’re done. But if you still like to anonymize, we do install software like Masquerade on Hypernode by default so you can make this part of your deployment strategy.

I will have to import my anonymised database anyway, so i don't need my database copied to a Brancher at all. Is that also possible?

Yes, this is possible. Simply select “don’t copy the database” when you start a Brancher node.

Why am I being charged without being able to use my Brancher node?

Brancher nodes are designed and conceived with the idea of running short tests. This could, for instance, be testing out a new version of PHP or MySQL. But also, for example, to run a temporary release on a separate brancher node in combination with Deployments. For example, we also use this when we make changes to our support documentation. The change is temporarily run on a Brancher node. The fact that the timer starts running immediately is indeed intended. We also pay directly for the space reserved with the Cloud Provider.