Inspired by Alex’s 2019 Tech Stack for Bootstrappers post, I decided to write about Statictastic tech stack in details.
Statictastic is a tool created to help teams to publish and manage static sites. It handles hosting, custom domain, CMS, Contact Forms, CDN, SSL certificates, etc.
Check this short video below if you want to have a better idea about the features and how Statictastic works:
Whenever someone is accessing www.statictastic.com they are accessing the product marketing website. The main goal of this website is to be fast and to include all the content that customers need to know about the product.
I’m eating my own dog food here. It’s a static site generated using Hugo and fully managed by Statictastic.
Statictastic had the need to deal with concurrency since the beginning. For this reason, finding a language that offers such support was a “must have” feature.
Elixir was my choice to build Statictastic. Although I have been using the language for a few years, I keep getting impressed by its simplicity and powerfulness. In combination with the Phoenix framework, both the development and now the maintenance have been productive.
Customers trust Statictastic to serve their websites. That means that Statictastic is responsible for their brand and there’s no space for messing up.
AWS was my choice to host and manage the application infrastructure. All the building blocks (DNS, load balancer, CDN, Auto Scaling, Database, Events, Emails) are managed by AWS, which make things easy to maintain and extremely resilient.
The main application uses PostgreSQL as its main database. PostgreSQL is a battle-tested database engine and offers all the features needed by Statictastic up to now. As mentioned above, Statictastic PostgreSQL is managed by AWS (RDS).
Statictastic send emails in two specific cases: Account activity and Contact form submission.
AWS SES is the tool responsible for sending transactional emails. It’s quite simple and integrated with all the other AWS tools.
Here I just stuck to the basic: G-Suite. It handles all the contact and support emails at the moment.
Although AWS has its own tool to manage logs, I decided to go with Timber to manage Statictastic logs.
Timber is a new kind of cloud-based logging system designed for applications and developers. Spend less time debugging and more time shipping.
The tool is quite simple and has some neat features.
I decided to use Sentry to get visibility about the errors. I have been using it for some time and it has never disappointed me.
Open-source error tracking that helps developers monitor and fix crashes in real time. Iterate continuously. Boost efficiency. Improve user experience.
Currently Statictastic includes a single video in the “How It Works” section, but I have plans on adding more videos, covering features in details.
I’m using Wistia to manage and host videos. It makes things simple and also gives nice insights about the video plays and user behaviours.
I’m a big fan of real-time chats. I think they are a nice way to get in contact and to get quick answers.
Statictastic integrated Drift, which enables all the visitors to quickly chat with me in case they have any questions about Statictastic or related topic.
I was developing Statictastic by myself, so although I needed something to organise and prioritise things, I didn’t need anything fancy. I’m using Trello to organise everything, from development to content creation.
Well, that’s it. I tried to cover all the tools and services currently being used to build and run Statictastic. If you have any questions or want to know more about a specific topic, feel free to get in touch.
Hi, I'm Elvio. I’m an independent software developer consultant based in Berlin, Germany. I’ve spent the last 10+ years working in a wide range of software projects, from internal web dashboards to real-time applications used by millions of people.More about me