What the builds are made with
This is the most technical group on the site, and the one an owner has the least reason to read. It is the raw material: the programming languages the builds are written in and the tools that turn code into a website you can actually click on. There is no job here that maps to your week the way the others do. It is here for one reason. When someone asks what a build is actually made of, or a developer on your side wants to check the work is standard and not some black box, the honest answer is on this page rather than hidden. The short version: these are ordinary, widely used tools, chosen because they are dependable, not because they are clever.
TypeScript
The main language most of the builds are written in. It is a stricter, safer version of JavaScript, the language of the web, and its strictness catches whole classes of mistakes before the code ever runs. For you that means fewer of the silly bugs that make software feel flaky.
Node.js
The engine that runs that code on a server rather than in a browser. It is what the automations and the behind-the-scenes half of a website actually run on. Widely used and well understood, which is what you want holding up the parts nobody sees.
Python
A widely used programming language, especially common for data and AI work.
Next.js
The framework the websites and web apps are built with. It is what turns the underlying code into fast, search-friendly pages a visitor can actually use, and it is a common home for a website helper like "Answer the questions you get asked all day". This site runs on it too.
React
The standard toolkit for building the interactive parts of a website: the buttons, forms and chat windows people click and type into. It sits under Next.js and is what makes an interface respond rather than just sit there. Almost anything a customer touches on a build is put together with it.
Astro
A framework built for content-heavy sites that need to load fast, such as blogs and marketing pages.
Tailwind CSS
A styling system for laying out and dressing an interface quickly and consistently. It is how the look of a build gets put together without a tangle of one-off styles, which keeps things tidy and quick to change. Invisible as a name, but you are looking at its work on most modern sites.
shadcn/ui
A set of ready-made, good-looking interface pieces, such as buttons, menus and dialogs, that can be dropped into a build and adjusted to fit. It saves rebuilding the ordinary parts of an interface from nothing, so the effort goes into the parts that are actually yours. It is assembled on top of the building blocks below.
Radix
The accessible, low-level building blocks that sit under interface pieces like the ones above: the plumbing that makes a menu open correctly and work with a keyboard and a screen reader. It is a quiet quality choice, and it is what makes an interface usable for everyone, not just the mouse-and-good-eyesight majority.
Framer Motion
A tool for adding smooth, considered animation to a web interface, the gentle movement that makes something feel finished rather than abrupt.
Three.js
A tool for drawing 3D graphics in a web page, the kind of moving, dimensional visuals you cannot make with ordinary web styling.
React Email
A way of building the emails a system sends using the same pieces as a website, so a reminder or confirmation looks clean and holds together in every inbox. It is what keeps the automatic emails from a build, the ones going out in your name, from arriving looking broken. It works alongside the sending service in the integrations.