Web / 5 technologies
Web interfaces people use every day.
Most of what we build has a web front end. Sometimes it is a marketing site that has to rank; sometimes it is a dashboard someone keeps open all day. Those jobs need different tools, so we pick per product and keep TypeScript throughout, which keeps the code readable for whoever works on it next.
Start a project
What we use
Web technologies we know well.
ReactInterfaces for dashboards, staff tools and customer portals that people use for hours at a time.Explore React ↗
Next.jsReact applications with server rendering, for products that need fast first loads and search visibility.Explore Next.js ↗
AstroContent sites and marketing pages that send HTML first and add JavaScript only where a page needs it.Explore Astro ↗
Tailwind CSSA utility-first CSS framework for building consistent interfaces quickly, straight from the markup.Explore Tailwind CSS ↗
TypeScriptTyped JavaScript across web, mobile and server code, so changes are checked before they ship.Explore TypeScript ↗
Why us
What we bring to web work.
React in our own products
The SoulCare care dashboard is a React web app we build and run, so we work with React in production, not only in demos.
TypeScript in a shipped product
SimRhythm is written in TypeScript, so the shape of every value is checked before the app reaches a device or browser.
This site is the proof
cirlume.co.uk is built with Astro and Tailwind CSS v4. You are looking at the result.
What you get
What a well-chosen stack gives you.
Pages that load quickly
Rendering on the server or at build time where it helps, so people see content before scripts finish.
One language end to end
TypeScript in the browser and on the server, with types shared between them.
Components you reuse
A shared set of interface parts, so new screens look and behave like the old ones.
Pages search engines can read
Server-rendered HTML for anything that needs to rank, not an empty shell filled in by JavaScript.
Where AI fits
AI in web work.
Answers inside your app
Add a search or question box that answers from your own documents, streams the reply into the page and shows its sources.
Knowledge assistants ↗Review screens for AI output
Interfaces where staff check, correct or reject what a model drafted before it is saved.
AI workflow automation ↗
Where it stops: The browser should never hold model keys or decide what a user may see. That stays on the server.
Choosing between them
Which one, and when.
Astro for sites people mostly read. Next.js when public pages and signed-in features share one product. A React single-page app for tools that live behind a login. TypeScript in every case, and Tailwind when a design system needs to stay consistent.
What’s changing
Shifts to plan for.
Dates that affect web technologies, checked against the official sources.
July 2026
TypeScript 7 ships
The compiler is now a native Go program, with full builds typically 8 to 12 times faster. Tools that used the old compiler API need checking before upgrading.
January 2026
Astro team joins Cloudflare
Cloudflare took on the Astro team. The framework stays MIT-licensed and can still be deployed to other hosts.
October 2025
Next.js 16 released
Caching became opt-in through Cache Components, Turbopack became the default bundler, and synchronous access to route params was removed, which affects upgrades.
Common questions
Web questions.
Do you build with WordPress?
Not as a rule. We use headless CMSs such as Sanity, Contentful and Storyblok, which give editors a familiar interface while the site itself stays fast.
Can you take over an existing React codebase?
Yes. We start by reviewing dependencies, build tooling and test coverage, then agree with you what to fix first.