Platform environments

The first thing you should know is that we’re a software product. That means that we are constantly developing updates, improving existing features and possibly fixing bugs. In order for us to keep a continuous service, while still experimenting and releasing out new stuff, we have created different environments: Production, Testing, Staging, Prodtest, etc…

It’s important to understand this difference, because as a customer you may have encountered an environment that looks and/or feels a bit different than your own. This means that you came into contact with another environment than the production environment. 

Our sales people have access to a testing environment (, in order for them to display new features that may not have been tested thoroughly enough to pass to the production environment. 

Sometimes, during implementation, we need to set up a separate platform (not production) in order to test a few things and make sure we can nail the configuration. 


The two customer-facing environments are the production and the testing environment.

Production environmentTesting environment
Your 'real' platformUsed for testing
Has all our fully released functionalityHas the newest features that are still in development
Includes your total populationLimited to a testing audience
Not used for trying out thingsUsed to try out new configurations/workflows
SupportNo support

Production environment

The production environment is the environment all our customers use. It has all the features that have been thoroughly reviewed and tested by our QA and engineering teams. The functionality on this environment needs to be reliable. Functionality that's still under development or isn't fully up to our quality standard yet won't be available here.

As a rule of thumb: The production environment will always be our latest, validated and reviewed code which is shared by all of our customers..

Testing environments 

Now, in order for us to have a stable production environment we need to do a lot of testing and this requires a separate environment. This can either be a testing environment (, staging environment, etc… The goal here is to be able to try out newly developed features, see if our solution to bugs in the production environment actually works and generally play around without hindering the production environment, a.k.a. our customers...

To give you an example: If we are working on a new feature, we will first open this in one of our testing environments. This allows QA and test users to start using the feature, review it and possibly change a few things. This process makes sure that once you, as a customer, get access to this new feature everything is working and you can start using it as well. 


It’s important to realize what platform in which environment you are looking at, and realize that this may or may not be a production environment. 

The production environment will always have the as a URL, while others will be slightly different, eg. for production testing.