What we actually work with

A typed layer over JavaScript that we use for Worker code, API handlers and browser code, so bad shapes fail at build time.

Schema-based checking of data at the edges of a system, so untrusted input is rejected before it reaches any business logic.

The component library we build most interfaces in, from a schema designer and a social timeline to client marketing sites.

The React framework we use when a site needs server rendering, static export or file-based routing rather than a bare client bundle.

A component framework we work in where a codebase already uses it, most often a Laravel application with a Vue front end.

Utility classes for styling interfaces, used on nearly every build so styles sit next to the markup, not in a parallel stylesheet.

A development server and build tool for browser apps, used where a single page app is the right answer and no server rendering is needed.

The layer that caches server data in the browser and holds UI state, using TanStack Query, SWR or Zustand depending on the build.

Unstyled component primitives and editors that give correct keyboard and screen reader behaviour, styled to fit the project.

JavaScript that runs in Cloudflare's network rather than on a server we keep alive; it hosts most of the APIs we ship.

A small HTTP router for edge runtimes; it does routing, middleware and typed request context in our Worker APIs.

A named single-threaded object with private storage; we use them for tenant routing, exact rate limits and WebSocket fan-out.

Work taken off the request path: message queues with retries and dead letter handling, plus jobs that run on a schedule.

Connections held open so a page updates without polling; Socket.IO carries the messaging layer in Starterflare.

A structured Node framework with modules and dependency injection; it holds the ten domain modules of the Starterflare backend.

PHP's standard application framework; the Consonas CRM codebase is Laravel 11 with a Vue front end on MySQL and Redis.

Server-side TypeScript run by Supabase on Deno; it holds the model calls and scheduled jobs behind 360nutri.

SQLite as a hosted database on Cloudflare, queried from a Worker over a binding instead of a connection pool.

The relational database we default to on conventional server builds, for data models with real constraints and joins.

MySQL is the relational database under our PHP and Laravel work, run where the framework and the hosting already assume it.

An in-memory store for cache, sessions, queues and rate limits on builds that run on conventional servers.

Cloudflare KV, an eventually consistent key-value store we use for sessions, caches and lookups read on every request.

Buckets for files: R2, Amazon S3 and Cloudflare Images, holding uploads, media and raw inbound data across most of our builds.

Drizzle and Prisma: typed query building and migration tooling, so the schema, the SQL and the TypeScript types stay in step.

Hosted Postgres with an API over the tables, plus auth, file storage and Deno functions, used where the database can be the backend.

OpenSearch for full-text search and NATS JetStream for event streams, in backends that have outgrown plain database queries.

Inference bindings on the edge runtime, used for embeddings, moderation, classification and short text generation.

Hosted frontier models called over HTTP from server code, used for image understanding and generated content.

An index of embeddings queried by similarity, used for semantic search and recommendation over stored records.

Payments and subscription billing, used for checkout, plan tiers, the customer portal and webhook-driven entitlements.

Transactional email over an API, used for verification links, password resets, magic links and digests.

Unit tests, browser end-to-end tests and linting in CI, sized to what a given build can actually break.

Error reporting, tracing and metrics, used to find out what production is doing when nobody is watching it.

Static and Node hosting on CDN platforms, Vercel, Netlify and nginx, used where a site does not need its own runtime.

Container orchestration for services that must run continuously, used where a stack has stateful components behind it.