For delivery projects, we prefer to use the same tech stack over and over again, as it makes life easier for developers. These tech stacks evolve of course, but generally using the same things across multiple projects makes it very easy for us to jump from project to project, and keeps things less surprising.
Projects tend to fall into into three main categories.
There are traditional websites where SEO is a major concern.
When we build websites, we build them so that the client can use the headless cms as a website builder and publish new pages themselves, utilizing the design system/building blocks we create during the project.
The websites we deliver generally consist of a Headless CMS, usually Storyblok. Styling is usually TailwindCSS. Commonly we stick to NextJS + Vercel, but also offer Astro with Cloudflare as an option.
We offer two different stacks for these currently.
Marketing Websites Good practices
Cookies, GTM & Consent Management
These are Web Applications with no SEO concerns, they usually require Login and have CRUD functionality.
We’ve done a lot with **BlitzJS** which is a framework on top of NextJS with Prisma/Postgresql and a “zero-api” layer - but have moved onward to T3-stack due to the dying community around Blitz.
We’ve used Render.com a lot for hosting, but tend towards Digital Ocean currently because it’s pricing is more lenient.
We do all our mobile apps with React Native. If the particular mobile app is a bad fit for React Native, then the project is likely a bad fit for us.