Storm Infrastructure Changes

During April and May we will perform a number of changes to our environment, primarily to give us better traceability, scalability and security for the Storm services.

The change does not require any immediate changes from an integration perspective, however, it’s possible that temporary disruptions will occur in the stage environment while we’re testing the rollout.

The primary change is the introduction of a new load balancing mechanism, and implementing that we will streamline the naming of our services. The current naming including any * address is deprecated and will be removed by Jan 31st 2021

Rollout plan

This is the rollout plan as of April 25th 2020, this plan will be adjusted if problems arises for customers and partners.

Load balancer introduction

Stage environment: Week 18-20

Production environment: May

New API endpoints available

Stage environment: Week 19-22

Production environment: Week 23-26

Legacy endpoint redirect

Legacy endpoints will return a 301 Moved Permanently redirect response. Since there are a vast variety of client libraries, it’s important that tests are performed, by clients and partners, to validate their chosen HTTP Client Library supports this. It also means that this activity might be postponed/prolonged if problems arises. To be able to handle the situation where clients are required to update the client libraries, this activity needs to be possible to roll back and to handle this, we need to have a fairly aggressive schedule.

Stage environment: 2020-07-01

Production environment: 2020-09-01


The naming of the API and Admin endpoints are fully backward compatible until Jan 31st 2021 (but will redirect to new endpoints,  see above).

Lab environment – *

The current Stage environment will be renamed to the Lab environment in preparation for the introduction of a new QA environment. The future purpose of the Lab environment is to be the internal system test environment for Storm, but accessible for external parties to be able to early test joint development efforts. The QA environment is planned for Q3 2020 (and will be named *



  • StormAPI:
  • Connect:
  • Admin:
  • Query:
  • Message:
  • Custom Integrations:

QA environment – *

Future QA environment, planned release during Q3. More information will be shared after summer.

Production environment *


  • StormAPI: ( will continue to work)
  • Connect:
  • Admin:
  • Query:
  • Message:
  • Custom Integrations: