HProxy

We style our whole website with Tailwind CSS, currently version 4. Writing the classes right in the components keeps each page's look in one place, and the build only ships the classes we actually use, so our CSS stays small. What works less well: long class lists make some components hard to read, so we pull repeated patterns into small shared components.

We publish our REST API in a public Postman workspace. Importing our OpenAPI file created a collection with every endpoint in a few minutes, and customers can fork it, put their own API key into a variable and try a call before they write any code. What works less well: an imported collection is a snapshot, so when our API changes we have to import the file again, and the free plan's limits for sharing inside a team are tight.

We use Google Analytics 4 on our site to see where visitors come from and which pages they read, and we pull those numbers through its API into our own reports instead of clicking through the interface. The realtime view is handy right after a launch to see whether traffic arrives. What works less well: GA4 runs behind our own server logs, so on a busy day we trust the logs first, and the interface takes a while to learn.

We track our keyword positions in a Semrush Position Tracking project and get an email when rankings decline, which helps us notice early when a page slips. Setting up the project took a few minutes and the reports are easy to read. What we like less: the full suite is expensive if you only need one or two features, and position tracking only covers the keywords you add yourself, so new topics need manual updates.

We use the free Ahrefs Webmaster Tools for our sites. The site audit emails us when something new turns up, for example a page that no internal link points to, which is easy to miss otherwise. We also check Ahrefs' Domain Rating through their free API before we list our product on a directory, so we can skip low-value sites and pay only where it is worth it. What we miss: most of the backlink data sits behind the paid plans, and those are expensive for a small team, so we stay on the free tools.

We use Stripe for card payments on our site, where customers top up a balance from $10. The API was easy to connect to our own backend, every payment shows up in the dashboard right away, and payouts reach our bank account reliably. The fees are noticeable on many small top-ups, and we still run our own fraud checks on top of Stripe's, but for card payments it has been dependable for us.