Take a look under the hood

Summary – Technical foundation of Messengerturn. A quick overview.

This is gonna be a little bit technical. You should read on, if you are interested in the software stack of Messengerturn.

Photo of a man wearing a VR headset in a workshop

Photo by Eddie Kopp on Unsplash

From low level to frontend –

Database: mongoDB Atlas

A mongodb cluster, replica set with 3 nodes. You definitely do not want to operate a database server on your own. I’m happy to buy instead of build that.

Infrastructure: Linode VPS

Virtual private server with Ubuntu. Nothing special. Location of all the data is Germany.

Webserver: nginx

Plain reverse proxy and SSL termination for the node.js process. Zero downtime deployments via PM2. Automatic SSL certificates with certbot and lets encrypt.

JS framework: Next.js

Next is running on top of an express server. There is a small REST-like part of the API to handle user-centric actions and the Telegram webhook. But most of the app is build on top of GraphQL.

All pages are server side rendered for that extra fast paint.

Frontend framework: UIkit

The CSS is based on top of UIkit.


Hosted on netlify and built with gatsby.js. It works offline and sets 0 (zero) cookies πŸ‘Œ


I chose that specific stack just because I know it the best. It really does not matter which technology you use, especially your customers don’t care. So choose one that you know the most about. Time to release should be minimized!

Thanks for reading this short overview. If you have any more questions: Find me on Twitter.

About the author

A blog about the evolution of Messengerturn. Announcing new features or explaining why things are done this or that way. If you like to know more, you can visit www.messengerturn.com.