How we build: the stack behind our sites and web apps
You get the stack that fits the job:
- most new sites run on Astro with a headless CMS on Cloudflare;
- web apps run on Laravel with React, or on Next.js with Payload and Postgres;
- WordPress on Bricks is there for teams that want traditional hosting.
Every technology below has a live project behind it. Once paid in full, the site, the code and every account are yours.
Astro and a headless CMS on Cloudflare: most new sites
Your pages are served from Cloudflare’s cache, close to your buyer. You have no WordPress plugins to patch, and your team edits content in a simple CMS: EmDash or Payload, chosen for the task.
- uwindi.com. This site runs on Astro and EmDash on Cloudflare Workers.
- TesovTech. A content platform for a tech review creator. In October 2026 it moved from WordPress to Astro and EmDash. The pages got faster and the design more premium, and the creator now edits content in a simpler editor.
Cloudflare Workers, R2 and Resend: forms, files and email
Your request form runs on Cloudflare Workers:
- Turnstile keeps out spam;
- attached files go to private R2 storage and reach you as signed links;
- notifications go out through Resend;
- the lead lands in your CRM, if you have one.
The form on this site, Neatko and TesovTech.
Web apps: Laravel with React, or Next.js with Payload and Postgres
Your web app gets one of two stacks, chosen by its requirements, scale and long-term maintenance.
- Laravel fits apps like warehouse management and self-storage, with React for the interface where the app needs it.
- Next.js with Payload and Postgres suits platforms with user accounts, catalogs and payments. It runs on Railway behind Cloudflare.
Examples:
- MLP. A warehouse management web app, 21M+ sq ft managed.
- Ambar. A self-storage web app with full WMS integration.
WordPress on Bricks: for teams that want traditional hosting
The site is custom-built, with no theme and no Elementor. It runs on the hosting you choose and is edited in the WordPress you know. More: custom WordPress development.
- Neatko. An embroidery studio’s brand, site and SEO.
- Talent Compass. A recruiting firm’s site and landing pages.
How your stack is chosen
Four questions decide it:
- Who edits the site, and how often?
- Does it need accounts, payments or a catalog?
- What does it connect to: the CRM, the ERP, ads?
- Where do you want it hosted?
The answers pick the stack, and you see the reasoning in the proposal.
