Our users and peers often ask us what language and tools we use and why. Here are our answers.
As part of our selection process, we focus on (1) robustness and (2) engineering speed. This means that once we’ve identified a few suitable tools, we aim to make our decision quickly to get back to building asap.
Our engineering stack is a living organism, so it will keep evolving, but here is what we use at the moment:
Porter is a YC company as well. The team is genuinely nice, super reactive and precise. But that’s not why we chose them: they were recommended by one of our advisors, who led big data infrastructure projects for incumbent banks and telecom companies in Europe. So we chose them on the spot.
A solid alternative is Qovery, their team is brilliant too. The team only ran into their product once we had already implemented Porter, but it’s a great product as well!
We started with NordVPN. It’s a great VPN, but we only needed an internal VPN. Tailscale does exactly that, and it’s really ‘zero-config’. Tailscale will link to your domain name, so that every team member can easily connect to it. It makes onboarding new team members easier and allows us to save a lot of time on the configuration.
We looked at GitBook, Theneo and GitHub pages. We wanted to have both the product documentation and API reference in the same place, while having enough flexibility on the presentation and design. We view our documentation as a part of our product so it needs to reflect the UX and brand we’re building.
We’re very happy with Docusaurus! The only thing to be aware of is that it’s a self-hosted solution, so it requires some configuration.