Sitevision is going Containerized
We’ve been working towards modernizing how Sitevision is run, and now we’re taking the next step. For developers, this changes how you access and run Sitevision on your machine. For customers running Sitevision on-prem, infrastructure to support the new container-based setup is required. In Sitevision Cloud, we handle the transition entirely.
Published: 2026-04-10
With the April release, we’re shipping a release candidate for containerized Sitevision. At this stage, all planned functionality is in place, but we need real-world validation before we can call it ready for production.
We’re aiming to release a production ready version in autumn 2026. By spring 2027, the previous way of accessing and installing Sitevision will be phased out.
We are currently in the migration phase. Once the transition is complete in Sitevision Cloud and on-prem environments, we can fully focus on the opportunities containerized deployment enables, such as improved performance, security, and scalability.
What this means for customers:
- This change affects all customers running Sitevision on their own infrastructure, they will need to handle the transition.
- We’re seeing different paths forward: some are preparing for containerized deployment, while others are choosing to invest their time in moving to Sitevision Cloud.
- Either way, it’s important to get started early to avoid getting stuck on the final version of the legacy installation.
Help us keep our customers informed so they can be well prepared and avoid last-minute rushes.
What this means for developers and partners:
- If you’re running Sitevision environments on your machine, you’re also affected and will need to adapt to the new container-based setup.
- Once the traditional way of downloading and installing Sitevision is phased out, local development will shift to running Sitevision in a container-based environment.
Local development going forward
Going forward, local development will be based on containers. Sitevision will be distributed as a container image, which you can run locally using a tool like Docker Desktop.
Sitevision/Cassandra Example single node setup
This setup is to be used for a local installation of Sitevision, for example, on a development machine using Docker Desktop with Docker Compose.
Prerequisites
Before you move on to our step by step guide make sure you fullfill these requirements. Make sure you:
- Have an account on My pages External link.. This is where you generate your Arty credentials External link. to download our images. You’ll use the Arty account to log in via your container platform.
- Have Docker desktop installed.
- Always have Docker desktop started before starting up your local Sitevision development environment.
- Are familiar with some basic Docker/Docker compose commands.
For more information on Docker Desktop and compose, we refer to official Docker documentation External link.
You’re free to choose your own container runtime and setup. While this guide uses Docker Desktop, alternatives such as Podman may also work. The provided Compose file can be used as a starting point.
Step-by-Step (Docker)
1. Log in to https://arty.sitevision-cloud.se with stored login credentials using the command below.
2. Save compose.yaml (compose.yaml) yaml, 3.2 kB.
3. Run the following commands to create volumes. These are used to persist data in your local sitevision environmet.
4. Run the following command to download specified Sitevision and Cassandra releases and start your environment. This must be run in the same directory as the saved compose.yaml file.
Your local sitevision environment is now up and running. Happy coding!