Our tech stack in 2022


Reading about our tech stack from one year ago gives me confidence for the future. Most of the languages and frameworks are still the same as twelve months ago. I think it is good we are not switching technology that often. It means we can maintain everything for a long time and get a lot of experience in our day-to-day tools.

Of course, we also have to keep an eye on the new stuff in web development and make some innovation happen at visuellverstehen. Therefore we try out new things in real-life projects from time to time. For example, I am happy there is Meilisearch now in our tech stack of 2022.

As always, I recommend not rushing into the last NewShinyFramework™.


  1. This will not cover every technology in all of our projects, because individual projects do need individual solutions. But it will cover all the basics.

  2. Legacy projects might use outdated technologies and those will not be part of this. Of course, we always try to update legacy projects.

  3. It is not easy to categorize every technology. Therefore the categorization might not always be 100 % correct.

  4. Not every one of us is working with all of the technologies mentioned below. Our team is organized into smaller sub-teams, which then focus on different projects.

Our tech stack

Core products

What people call »Backend«

  • Extbase
  • Laravel
  • Laravel Nova
  • Meilisearch
  • MySQL
  • PHP
  • PHPUnit
  • Statamic
  • TYPO3

What people call »Frontend«

  • Alpine.js
  • Antlers
  • BEM
  • Babel
  • Blade
  • CSS
  • Fluid
  • HTML
  • JavaScript
  • Laravel Livewire
  • Sass
  • Tailwind CSS
  • Vue.js
  • gulp.js
  • npm
  • webpack

What people call »DevOps«

  • Docker
  • Docker Compose
  • Git
  • GitHub
  • GitHub Actions
  • GitLab
  • GitLab CI
  • Hetzner Cloud
  • Laravel Forge
  • Mittwald

Honorable mentions

Three things are worth a special mention.

  1. Although Shopware 6 is a well-crafted software, we decided against it. We want to focus on individual digital products using Laravel and Vue.js plus content management using Statamic and TYPO3. We will still maintain running client projects and support our Shopware plugins though.

  2. One of our clients asked for Alpine.js in combination with Laravel Livewire. It turns out those work well together. Let us see if we want to use it more often in the future.

  3. We are using Meilisearch for advanced search technologies more and more. It is a simple alternative to Solr and Elasticsearch written in Rust. It works smoothly with Laravel and Statamic. We also developed a TYPO3 extension for Meilisearch.

Happy coding

I am curious how this will change in the next twelve months. Well, we will find out. See you next year. Happy coding.

Julia Lange

Access Current Entry in Custom Validation Rule

Sometimes, when writing a custom validation rule for a Statamic project, I find myself in a position...

Discover full article


Create an entry approval workflow with Statamic Revisions

When managing entries in your Statamic application that gather external data, such as from APIs, you...

Discover full article

Yamen Hadla

Effortless Language Redirection - TYPO3 Extension

Introduction Hello fellow TYPO3 enthusiasts! I had the pleasure of cooperating with my...

Discover full article
View all articles