Next® takes a major step into Docker, containers, and Kubernetes

As part of our commitment to our long term cloud-first strategy for Next® Digital Workplace we today take a major step forward.

When we run Next® as a Service we do so using traditional Virtual Servers in Microsoft Azure. With automated provisioning, we can spin up new customer instances in minutes, and deploy new servers automatically as the need arises. Everything is just fine. 

In order to become truly cloud-native, and deliver unlimited scalability with full 24/7 support for our users, we aim to move everything to Azure Kubernetes Services over time.  

Azure Kubernetes Services is the future platform for Next® as a Service 

Next® Transformation Engine

The Next® Transformation Engine - responsible for OCR, full-text extraction, PDF generation, and other data transformation in Next® - now becomes the first component ready to be delivered as a Docker image, deployed as a container, and ready to run in Kubernetes.  

All other components in the Next® technology stack will follow, and eventually the entire Next® Digital Workplace will run as cloud native application in Microsoft's data centers. 

For you as a customer, this means faster, easier, and even more reliable operations, as Next® will be able to automatically spin up new instances of it's components if something breaks down, or increased user activity requires more computing muscles.

For us this means easier operations with better scale of economics. Retaining 100% separation between customer's data, we get to share computing power among all customers and users.   


To the benefit of on premises customers too  

Far from everyone is ready to move to the cloud now. And amongst those who are, some prefer their own cloud - Amazon, IBM, Google, or something completely different. In reality, the vast majority of Next® customers run their Next® on their own servers, or on servers run by their hosting partner.

The containerization of Next® Transformation Engine brings many benefits to you too.

Previously, the Next® Transformation Engine required a Windows server to run. Now it's your choice if you prefer to deploy it on Windows or on Linux. 

At the same time, the protocol used by the transformation engine has has been optimized dramatically, securing you increased performance and improved reliability. Also the configuration has been streamlined and simplified.  

For the techie ones

When you upgrade to the containerized Next® Transformation Engine, we cannot detect the IP address of the engine. Previously the Transformation engine  was responsible for the connection, but now core Next® is in control. Until you setup this address, the Next® Transformation engine will not be able to process requests. 

Additional information

Please refer to the online product guide for additional information on this feature, once it is released.

Commercial terms and conditions

The new and enhanced Transformation Engine is available free of charge to anyone with a valid license, and an active service plan. 

Any consultancy needed will be invoiced. 

Using Next® in a high availability setup, requires a High Availability License. 


Despite our best efforts, we may be forced to change both content and expected delivery of future product updates without notice.



Next® takes a major step into Docker, containers, and Kubernetes


New feature


In planning 

Expected release:

December 2021

Affected products:

Next® Bank Statements
Next® Contracts
Next® Emails
Next® Enterprise Archive
Next® ExCustody
Next® Invoices
Next® Mailroom
Next® Processes





Responsible product manager:

Kim Hellum




Kim Hellum