Runtimes
Artifakt provides you with several runtimes you can use to power your applications.

What is a Runtime?

At Artifakt, runtimes are responsible for running your applications. When you select a runtime, we configure everything that must be running on the platform for applications to execute. Also, we use containerisation which involves bundling an application together with all of its related dependencies, libraries, and configurations files required for it to run.

Officially supported Runtimes

Artifakt maintains a collection of officially supported runtimes. Our runtimes are open-source and available on GitHub.
If you have a change that would be useful to the developers community, we encourage you to submit a pull request.
Runtime
Version
Documentation
Stage
End of Support
Akeneo
5.0
GA
30 Sep 2022
Angular
12
GA
-
Drupal
9.2
GA
-
Golang
1.16
GA
-
Java
8
GA
31 Mar 2022
Magento
2.4
GA
Sep 2022
Node.js
14
Maintenance
Apr 30 2023
​
16
GA
30 Apr 2024
PHP
8.0
GA
26 Nov 2022
​
7.4
Maintenance
28 Nov 2021
Python
3.9
GA
05 Oct 2025
Ruby
2.7
GA
-
Sylius
1.10
GA
Jan 17, 2023
​
1.11
GA
Jun 17, 2023
Symfony
4.4
GA
Nov 1st, 2023
​
5.4
GA
Nov 1st, 2025
VueJs
3
GA
-
Wordpress
5.7
Maintenance
-

Default sizing by Runtimes

By default, all created environment in Artifakt are configured with this default sizing:
  • 2GB RAM for the application instance including 50GB system disk.
  • 25GB persistent storage disk to store your assets.
If you are building a scalable platform, we also add by default a MySQL services (1GB RAM including 25GB storage disk) for the following runtimes:
  • Drupal
  • Symfony
  • Wordpress
There are exceptions for these specific & complex runtimes:
Text
Starter Platform Sizing
Scalable Platform Sizing
Akeneo
  • Application: 8GB RAM
Akeneo is not available on scalable platforms
Magento
  • Application: 8GB RAM
  • Application: 8GB RAM
  • Background Worker: 8GB RAM including 50GB disk.
  • MySQL 8: 8GB RAM including 50GB disk.
  • Elasticsearch 7: 4GB RAM including 50GB disk.
  • Redis 6: 4GB RAM

Custom runtime & Dockerfiles

If you have your own Dockerfile that you wish to deploy with, you must select the option β€˜Custom Runtime’ when creating your project. This will put your project and environment into a custom mode and not use Artifakt’s default GIT templates.
Custom Runtime

Shared responsibilites

Please note that Artifakt is only responsible for the original runtime provided. In case an issue arises, we will try to reproduce it using the Artifakt-provided image.
  • You will be responsible for any Docker Image you are providing if you use the dedicated "Custom Runtime" option.
  • If using the Artifakt runtime as a baseline, you will be responsible for all of your modifications unless they've been done by Artifakt Professional Services.
  • In any case, Artifakt support team will try to find the root cause of your issue and a proper solution. If the issue comes from your modifications, you might be charged for the service at regular Professional Service rate.
For more infomations please consult Shared Responsibility Model.
If you need assistance to write your Dockerfile, please contact our Sales team.
In case an officially supported runtime has been deprecated, you will also become responsible to upgrade to a supported version or transition to "custom runtime" mode.
If you still decide to keep the same version, please contact our Customer Support team.