Lightning Jar - Web Studio

Technologies

Below is a list of some of our favorite and most-used technologies for building web applications for clients.

1. AI / LLM

Why this matters: Controversial, misunderstood, and overhyped though they may be, AI and LLMs are transforming industries and society. Used carefully and responsibly, they are still a valuable tool for innovation and progress. We design and deploy LLM-powered features with a focus on safety, performance, and maintainability, leveraging managed model providers and an SDK-first approach for rapid iteration. Preferred defaults: Vercel AI SDK + AI Gateway for multi-model orchestration; Anthropic and OpenAI as primary model providers.

Anthropic (Claude)

Model Provider

Provider of the Claude family of models, known for strong reasoning, long context windows, and helpfulness with a focus on safety. Excellent for analytical tasks, documentation-heavy workflows, complex tool use, and structured outputs. We choose Claude when we need high-quality reasoning, longer contexts, and nuanced instruction-following for chat, agents, and knowledge-heavy assistants.

Use Cases:

  • Knowledge-dense assistants and agents
  • Long-context analysis and summarization
  • Structured outputs for integrations

State-of-the-art language and multimodal models used for chat, content generation, extraction, and code-focused tasks. Broad ecosystem support, tools/function calling, and strong multimodal capabilities make it a versatile default. We reach for OpenAI when we need wide capability coverage, robust tooling, and predictable performance across chat, embeddings, and function/tool workflows.

Use Cases:

  • General-purpose chat and content creation
  • Embeddings and similarity for search/RAG
  • Code-focused assistants and refactoring

Vercel AI Gateway

AI Gateway / Observability

A managed gateway that unifies access to multiple model providers with a single endpoint, centralizing API keys, rate limiting, caching, and observability. It provides request analytics, cost controls, retry/backoff strategies, and prompt/version governance. We adopt Gateway to de-risk vendor lock-in, improve reliability at scale, and gain visibility into latency, token usage, and cost across providers and environments. Licensing notes: SaaS gateway; models remain provider-side. We can route traffic to alternative gateways or direct APIs to avoid lock-in.

Use Cases:

  • Centralized model access across vendors
  • Cost and latency management for production AI
  • Prompt/version governance and analytics

A TypeScript-first toolkit for building AI features into web apps with streaming UI, multi-provider support, and server/client utilities. It simplifies chat, tool-calling, RAG, and function invocation with first-class React/Svelte adapters and edge-friendly primitives. We use it to prototype quickly, support multiple model vendors without rewriting app logic, and ship reliable, streaming conversational UIs with minimal boilerplate.

Use Cases:

  • Conversational UIs with streaming responses
  • Multi-provider resilience without app rewrites
  • Tool calling and function execution from the UI

2. API & Integration

Why this matters: Clear, type-safe APIs prevent integration drift, reduce incidents, and make feature delivery predictable. We design APIs for clarity, performance, and safety—favoring type-safe schemas, real-time capabilities, and standards-based integrations. Preferred defaults: GraphQL for complex domains, tRPC for TS monorepos, Webhooks for eventing, Zod/Valibot for schemas.

GraphQL

API Protocol

Our preferred choice for complex domains, enabling strongly-typed schemas, precise data fetching, and powerful tooling like code generation and caching. We implement schema governance, persisted queries, and performance-aware resolvers to keep APIs fast and predictable.

Use Cases:

  • Complex product/content domains with many clients
  • Client-optimized queries and reduced over-fetching
  • Schema-driven development and codegen

NanoID

Identifier Generation (IDs, Tokens)

A tiny, fast library for generating cryptographically strong, URL-friendly unique IDs with customizable alphabets and lengths. We use NanoID for public-facing identifiers, idempotency keys, and correlation IDs where short, non-sequential, collision-resistant tokens improve UX and security compared to UUID v4.

Use Cases:

  • URL-safe, short IDs for public resources and links
  • Idempotency keys, request deduplication, and correlation IDs
  • Client-side identifier generation without central coordination

tRPC

Type-safe RPC

A great fit for full-stack TypeScript apps where end-to-end type safety and developer velocity are paramount. We choose tRPC when teams benefit from shared types without the overhead of an additional query language.

Use Cases:

  • Monorepos with shared types
  • Rapid prototyping of internal tools
  • Type-safe server/client contracts without GraphQL

Valibot

Schema Definition & Validation

A lean, fast schema library for parsing and validation with strong TypeScript inference. We use Valibot to validate inputs at the edge and server boundaries, ensuring trustworthy data pipelines.

Use Cases:

  • Lightweight schema validation in edge functions
  • Type-safe form and API input parsing
  • Bundle-size conscious validation

Webhooks

Event-driven Integration

We integrate and expose webhooks to connect systems and automate workflows across services. We focus on signature verification, retries with exponential backoff, idempotency keys, and audit logging for reliability.

Use Cases:

  • Real-time event notifications between services
  • Automated workflow triggers
  • Third-party integrations and sync

WebSockets

Real-time Transport

We make extensive use of WebSockets for low-latency, bidirectional communication—ideal for collaborative UIs, live dashboards, and streaming interactions. Our implementations emphasize backpressure, reconnection strategies, and secure auth handshakes.

Use Cases:

  • Real-time collaborative features
  • Live dashboards and notifications
  • Chat and messaging applications

Zod

Schema Definition & Validation

A popular, ergonomic schema validator with excellent DX and ecosystem integrations. We use Zod where broad community support and familiar patterns speed up delivery.

Use Cases:

  • TypeScript-first schema validation
  • API request/response type safety
  • Form validation with error messages

3. Auth & Security

Why this matters: Security is trust—modern auth and session practices protect users and keep compliance teams comfortable. Security is foundational. We standardize on modern auth, strong session management, and defense-in-depth controls to protect users and systems. Preferred defaults: BetterAuth for app auth, token-based sessions with rotation, 2FA (TOTP + WebAuthn), Arcjet for edge protection.

Arcjet

App Security

We use Arcjet to enhance security at the application edge—protecting against bots, abuse, credential stuffing, and anomalous traffic. Arcjet pairs well with serverless/edge stacks, adding risk-based controls and observability to critical endpoints.

Use Cases:

  • Bot protection and abuse prevention at the edge
  • Rate limiting and credential stuffing defense
  • Risk-based access controls for critical endpoints

BetterAuth

Authentication

Our preferred authentication solution for modern web apps—clean APIs, strong multi-tenant support, and integration-friendly flows. We insist on two-factor authentication (2FA) for client logins and design enrollment/recovery flows that balance security with usability.

Use Cases:

  • User authentication for modern web applications
  • Multi-tenant apps with SSO and social login
  • Secure session management with 2FA support

DOMPurify

Content Sanitization (XSS Protection)

A fast, well-audited library to sanitize HTML and SVG against XSS attacks in browsers and Node.js. We run DOMPurify at render time or on ingestion to neutralize scripts, event handlers, and dangerous URLs—paired with strict CSP and escaping for defense-in-depth.

Use Cases:

  • Sanitizing user-generated HTML/markdown output to prevent XSS
  • Rendering rich text safely in SPAs/SSR without trusting input
  • Enforcing allowlists for attributes, tags, and URL protocols

We favor token-based auth (short-lived access tokens with refresh rotation) for stateless scaling across serverless and edge environments. Our implementations emphasize secure storage, rotation, and scoping with least-privilege principles.

Use Cases:

  • Stateless authentication for serverless apps
  • Secure API access with refresh token rotation
  • Cross-service authentication in microservices

2FA is a requirement for client logins. We support TOTP apps, WebAuthn/passkeys, and backup codes for resilience. We design secure enrollment, device management, and recovery to minimize lockouts while maintaining strong posture.

Use Cases:

  • Enhanced account security for user logins
  • TOTP and WebAuthn/passkey support
  • Secure backup code and recovery flows

4. Backend & Runtime

Why this matters: Choosing the right runtime and hosting improves reliability, security, and developer velocity from day one. We choose runtimes and hosting that balance security, developer experience, and performance. Our defaults favor fast iteration locally and reliability in production, with growing adoption of secure-by-default platforms. Preferred defaults: Bun for local dev, Node.js for production, Vercel for hosting and edge.

Bun

Runtime (Development)

Our preferred development runtime for its fast install, test, and dev server performance. Bun streamlines local DX with speedy tooling and modern APIs. We use Bun to accelerate feedback loops during development while keeping parity with production targets.

Use Cases:

  • Fast local development with instant installs
  • Running scripts and dev servers with minimal latency
  • Prototyping and tooling scripts

Deno

Runtime (Security-focused)

An increasingly important part of our stack due to secure-by-default permissions, native TypeScript support, and web-standard APIs. We consider Deno for apps where sandboxing, permission scoping, and edge deployment are priorities.

Use Cases:

  • Secure scripts with granular permissions
  • Edge functions and serverless deployments
  • TypeScript-first CLI tools and utilities

Docker

Containers & Dev Environments

Standard container tooling for packaging apps and dependencies into immutable images, ensuring consistent behavior across dev, CI, and production. We use Docker for local service orchestration (Compose), hermetic builds, and CI pipelines; images can be deployed to managed platforms or orchestrators when serverless isn’t a fit.

Use Cases:

  • Reproducible local environments and parity with CI/production
  • Containerized services and dependencies for development (DBs, queues, caches)
  • Portable deployment artifacts for servers, Kubernetes, and CI pipelines

Node.js

Runtime (Production)

Our preferred production runtime thanks to its maturity, ecosystem depth, and predictable operational model across serverless and containerized workloads. We optimize Node for cold starts, streaming responses, and observability in modern hosting environments.

Use Cases:

  • Production server-side applications
  • API servers and microservices
  • Build tools and CLI applications

Vercel

Hosting & Edge

We frequently host on Vercel for its excellent developer experience, preview environments, instant rollbacks, built-in firewall capabilities, and Edge Runtime. Vercel’s serverless and edge primitives pair well with our frameworks (SvelteKit, Vue/Nuxt, Astro) for globally fast delivery.

Use Cases:

  • Preview deployments for every pull request
  • Edge functions and serverless APIs
  • Global CDN delivery with instant rollbacks

5. Content Management / PIM

Why this matters: Centralizing content and product data shortens time-to-publish, lowers error rates, and keeps every channel consistent. Platforms that centralize product data, digital assets, and content, enabling omnichannel delivery, governance, and a single source of truth across websites, apps, and commerce. Preferred defaults: Pimcore for data-heavy catalogs; Sanity for bespoke editorial workflows; Hygraph for GraphQL-first federation.

Hygraph

Headless CMS (GraphQL-first)

A GraphQL-native, headless content platform designed for federating content across sources and delivering it to any frontend. Hygraph excels at structured content modeling, schema stitching via Remote Sources, and performant queries with granular permissions. We use Hygraph when teams want a modern editorial UI, strong GraphQL ergonomics, and easy integration with other services through content federation—ideal for omnichannel content and multi-site setups.

Use Cases:

  • GraphQL-first content delivery across web/app surfaces
  • Content federation from multiple backends
  • Multi-site and white-label content models

LJX

Lightning Jar Custom CMS

LJX is our own custom CMS solution, designed to allow content editors to edit text in place. It provides a seamless editing experience, enabling users to make changes directly on the page without the need for separate editing tools.

Use Cases:

  • Bespoke editorial CMS with real-time collaboration
  • Rich block content (Portable Text) at scale
  • Multi-environment governance and review flows

Pimcore

Digital Experience Platform (PIM, DAM, CMS, CDP, Commerce)

An open-source, enterprise-grade platform that unifies Product Information Management (PIM), Digital Asset Management (DAM), headless CMS, and customer data capabilities in one stack. Pimcore shines when you need a single source of truth for complex catalogs, omnichannel content, and assets—powering consistent experiences across web, mobile, marketplaces, and POS. We choose Pimcore for data-heavy builds, multi-language catalogs, and intricate data modeling with strict governance. Its API-first approach pairs well with modern frontends (e.g., SvelteKit, Vue/Nuxt, Astro) and enables scalable, composable architectures without locking you into a single frontend or commerce engine. Licensing notes: GPLv3 with commercial license available; self-hosting supported for data residency and compliance.

Use Cases:

  • Multi-language, multi-catalog product data with governance
  • Omnichannel content and asset syndication
  • Complex data models with approvals and workflows

Sanity

Headless CMS

A highly customizable, schema-driven content platform with the Sanity Studio, real-time collaboration, and a powerful GROQ query language. Sanity’s Portable Text and content graph features enable flexible, structured content at scale. We choose Sanity when editorial workflows, real-time collaboration, and deep customization are priorities—especially for bespoke content models, multi-environment governance, and performant headless delivery. Licensing notes: SaaS with exportable content and APIs; bring-your-own CDN for assets if required.

Use Cases:

  • Bespoke editorial CMS with real-time collaboration
  • Rich block content (Portable Text) at scale
  • Multi-environment governance and review flows

6. Core Web Foundations

Why this matters: Strong platform fundamentals (HTML, CSS, JS/TS) make apps faster, more accessible, and significantly easier to maintain. We ground every build in platform-native best practices: type-safe JavaScript, accessible HTML, and modern CSS. This foundation enables maintainable codebases, reliable refactors, and fast, inclusive user experiences. Preferred defaults: TypeScript strict mode; UnoCSS or Tailwind; semantic HTML with ARIA and WCAG 2.2 targets.

We leverage CSS Grid, Flexbox, custom properties, container queries, and cascade layers to build resilient layouts that adapt across devices. Our CSS approach centers performance, accessibility, and maintainability—minimizing specificity wars and dead code.

Use Cases:

  • Responsive layouts with Grid and Flexbox
  • Component-scoped styles with custom properties
  • Adaptive designs using container queries

HTML

Markup

Semantic HTML is non-negotiable for accessibility, SEO, and performance. We prioritize ARIA correctness, keyboard navigability, and progressive enhancement. We follow best practices for metadata, link relations, preloading, and structured data to improve discoverability and UX.

Use Cases:

  • Accessible, semantic page structure
  • SEO-optimized markup with structured data
  • Progressive enhancement foundations

Modern JavaScript features—modules, async/await, generators—paired with build tooling deliver lean bundles and clear, maintainable code. We emphasize performance practices like code-splitting, tree-shaking, and lazy-loading to optimize Core Web Vitals.

Use Cases:

  • Modern async/await patterns for data fetching
  • Tree-shakeable ES modules for smaller bundles
  • Clean, maintainable application logic

Tailwind CSS

CSS Framework

Our close second for utility-first styling. Tailwind enables consistent design systems, rapid iteration, and predictable theming with excellent tooling and ecosystem support. We pair Tailwind with component-driven UIs and design tokens for scalable, reusable patterns.

Use Cases:

  • Rapid UI prototyping with utility classes
  • Design system implementation with tokens
  • Consistent styling across component libraries

TypeScript

Language

We default to TypeScript with strict mode wherever possible to enforce robust types, safer refactors, and reliable API contracts across services and clients. Our approach includes strict null checks, noImplicitAny, and type-safe schemas to reduce runtime errors and improve long-term maintainability.

Use Cases:

  • Safer refactors and shared contracts across services
  • API client generation and schema-driven development
  • Large codebases requiring maintainability

UnoCSS

CSS Framework

Our preferred atomic CSS engine for on-demand utilities, instant compile, and flexible presets. UnoCSS keeps CSS minimal and maintainable while supporting design tokens and variants. We use it to balance developer velocity with runtime performance, avoiding unused styles and heavy bundles.

Use Cases:

  • On-demand atomic CSS generation
  • Custom utility shortcuts and presets
  • Minimal CSS bundles with tree-shaking

7. Databases & Storage

Why this matters: A reliable data layer is the backbone of performance, data integrity, and scale—without heavy ops overhead. Reliable data layers underpin fast, scalable web apps. We select managed, developer-friendly databases and storage that pair well with serverless/edge architectures, reduce ops overhead, and provide clear scaling paths. Preferred defaults: PlanetScale for MySQL workloads; Turso for edge-first SQLite; Upstash for Redis/queues; Vercel Blob for simple storage.

DigitalOcean Spaces

Object Storage (S3-compatible)

Scalable, S3-compatible object storage with a global CDN option and predictable pricing. Fits well when you need portable storage outside a specific hosting platform. We reach for Spaces for asset storage, backups, and static media distribution with familiar S3 tooling and lifecycle management.

Use Cases:

  • Asset storage decoupled from hosting provider
  • Static site asset delivery with CDN
  • Backups and lifecycle-managed archives

Drizzle ORM

Database ORM

Drizzle ORM is a TypeScript ORM for PostgreSQL, SQLite, MySQL, and CockroachDB

Use Cases:

  • Type-safe database queries
  • Automatic migrations
  • Support for multiple databases

PlanetScale

Serverless MySQL (Vitess)

MySQL-compatible database built on Vitess, offering non-blocking schema changes, horizontal scaling, and branch-based workflows for safe migrations. We use PlanetScale for production-grade relational workloads that need MySQL semantics, strong reliability, and developer-friendly branching. Licensing notes: Managed MySQL (Vitess). Data export and branching facilitate migration when needed.

Use Cases:

  • Production relational workloads on MySQL
  • Zero-downtime schema changes and branching
  • Horizontally scalable multi-tenant apps

Sharp

Media Processing (Images)

A high-performance Node.js image processing library powered by libvips—faster and more memory-efficient than ImageMagick/GD for common operations. We use Sharp to generate responsive variants, optimize to modern formats (WebP/AVIF), strip metadata, and enforce size constraints in upload pipelines and edge/serverless functions.

Use Cases:

  • Server-side image resizing, cropping, and format conversion
  • Automatic optimization to WebP/AVIF with quality/size trade-offs
  • Generating thumbnails and responsive image variants on upload or on-demand

Turso (SQLite)

Distributed SQLite (Edge DB)

A distributed, edge-optimized SQLite database built on libSQL with global replicas for low-latency reads and serverless-friendly connections. We choose Turso for edge-first apps, multi-region reads, and lightweight relational workloads that benefit from SQLite ergonomics with cloud scale.

Use Cases:

  • Edge-first apps needing global read performance
  • Lightweight relational data with serverless
  • Caches and feature storage near the user

Upstash

Serverless Data Services (Redis, Kafka, QStash, Vector)

Pay-per-request, serverless data platform offering Redis, Kafka, QStash (HTTP-based queues), and vector storage with global latency optimization. We adopt Upstash for event streams, caching, queues, and lightweight vector/RAG needs in serverless and edge environments with minimal cold start overhead.

Use Cases:

  • Serverless Redis caching and rate limiting
  • QStash background jobs and event pipelines
  • Lightweight vector storage for RAG

Vercel Blob Storage

Object Storage (Edge-integrated)

Simple, durable blob/object storage tightly integrated with Vercel projects and Edge Middleware. Great for uploads, public/private files, and serving media with minimal configuration. We use it for straightforward file storage in Vercel-hosted apps, leveraging built-in upload APIs, signed URLs, and region-aware performance.

Use Cases:

  • User uploads and media libraries
  • Public/private file delivery with signed URLs
  • Edge-aligned assets for low-latency access

8. Frontend Frameworks

Why this matters: The right framework reduces complexity and improves Core Web Vitals, which translates directly into better UX and SEO outcomes. Frontend frameworks are essential for building interactive and dynamic user interfaces. They provide a structured approach to organizing code, managing state, and handling user interactions. Preferred defaults: SvelteKit for app-first builds; Astro for content-heavy sites; Nuxt when teams prefer Vue.

Astro

Frontend Framework

A modern web framework focused on delivering zero-JS by default to the browser, Astro excels at content-rich sites with outstanding performance and supports Island Architecture so you can hydrate only what you need. Its seamless integration with React, Vue, Svelte, and others plus first-class MDX/content tooling make it a great fit for fast marketing sites, blogs, and documentation.

Use Cases:

  • Blogs, docs, and marketing sites with best-in-class performance
  • Multi-framework islands (React/Vue/Svelte components)
  • Content-heavy pages with minimal client JS

Svelte / SvelteKit

Frontend Framework

Our favorite open-source JavaScript framework at present, SvelteKit is the backbone of most of our new and upcoming projects. SvelteKit is the rare framework that truly reduces complexity and unpredictability rather than adding more limitations, complexity, or unnecessary boilerplate.

Use Cases:

  • High-performance apps and sites with SSR/SSG and streaming
  • Product dashboards and internal tools
  • Greenfield builds prioritizing low complexity and fast iteration

Vue / Nuxt

Frontend Framework

A progressive, approachable framework for building rich interfaces, with a gentle learning curve and excellent developer experience. Nuxt adds first-class routing, server rendering, API routes, and file-based conventions—ideal for content-driven sites, SSR/SSG, and hybrid apps. We reach for Vue/Nuxt when teams value clear component patterns, robust ecosystem support, and strong performance with minimal configuration.

Use Cases:

  • Content-led marketing sites with editorial workflows
  • Multi-site, SSR/SSG, and hybrid apps
  • Teams standardized on Vue

9. Monitoring & Testing

Why this matters: Observability and tests catch regressions early, reduce MTTR, and enable confident, frequent releases. We ship with confidence by instrumenting apps end-to-end: unit and integration tests, accessibility checks, and production observability. Our approach emphasizes fast feedback loops, clear failure signals, and actionable telemetry. Preferred defaults: Sentry for errors/perf, Playwright for E2E, Vitest or Bun Test for unit, OpenTelemetry for tracing, Lighthouse CI for budgets.

axe-core

Accessibility Testing

Automated accessibility checks integrated into unit/E2E tests and CI to catch common WCAG issues early. We combine automated checks with manual screen reader and keyboard testing for comprehensive coverage.

Use Cases:

  • Automated WCAG accessibility testing in CI pipelines
  • Integration with unit and E2E test suites
  • Early detection of accessibility regressions

Biome

Static Analysis & Formatting

All-in-one formatter, linter, and code actions replacement for ESLint/Prettier with native TypeScript support and very fast performance. We enforce strict TypeScript rules, import/order hygiene, and consistent formatting via Biome in CI for healthy, maintainable codebases.

Use Cases:

  • Fast code formatting and linting in CI
  • Enforcing consistent code style across teams
  • Replacing ESLint and Prettier with a single tool

Bun Test

Unit Testing (Runtime-native)

Bun’s built-in test runner delivers extremely fast execution, snapshots, and watch mode—great for local DX and monorepos. We use Bun test where projects already target Bun for dev to get near-instant feedback loops.

Use Cases:

  • Fast unit testing for Bun-based projects
  • Watch mode for rapid test-driven development
  • Snapshot testing and assertions

We recommend feature flags and gradual rollouts to mitigate risk and enable safe experimentation. Tools like LaunchDarkly or Unleash pair with observability to quickly roll back or dial traffic.

Use Cases:

  • Gradual rollouts and A/B testing
  • Quick rollback of problematic features
  • Environment-specific feature configuration

Lighthouse CI

Performance & Accessibility Audits

Automated audits for Core Web Vitals, accessibility, SEO, and best practices in CI with historical tracking and budgets. We set performance budgets and fail builds when regressions exceed thresholds.

Use Cases:

  • Performance budget enforcement in CI
  • Tracking Core Web Vitals over time
  • Automated accessibility and SEO audits

OpenTelemetry

Tracing & Metrics Standard

Vendor-neutral tracing, metrics, and logging instrumentation to unify observability across services and runtimes. We emit spans from serverless and edge functions to correlate logs, errors, and performance throughout a request.

Use Cases:

  • Distributed tracing across services
  • Unified metrics and logging collection
  • Vendor-agnostic observability instrumentation

Plausible

Analytics

Plausible is a lightweight web analytics tool that provides insights into website traffic and user behavior.

Use Cases:

  • Privacy-friendly website analytics
  • GDPR-compliant traffic monitoring
  • Lightweight alternative to Google Analytics

Playwright

End-to-End (E2E) Testing

Reliable cross-browser E2E tests with powerful auto-waiting, tracing, and test isolation. Works well in CI with parallelization and flakes control. We use Playwright for user-journey and regression tests, plus accessibility assertions and visual comparisons when needed.

Use Cases:

  • Cross-browser end-to-end testing
  • Visual regression testing with screenshots
  • Automated user journey validation

Polypane

Browser for Dev, A11y, and Responsive Testing

A developer-focused browser for multi-view responsive design, accessibility audits, and performance insights—all side by side. We use Polypane to validate layouts across breakpoints simultaneously, run a11y checks, visualize landmarks/headings, and preview meta/OG cards efficiently.

Use Cases:

  • Simultaneous responsive design testing
  • Accessibility audits and landmark visualization
  • Performance profiling and meta tag preview

We validate API inputs/outputs and webhook payloads with schema libraries (e.g., Zod, Valibot) to stop bad data at boundaries. Schemas double as client contracts and improve testability. See “API & Integration → Schema Definition & Validation” for our defaults.

Use Cases:

  • API input/output validation at boundaries
  • Type-safe webhook payload parsing
  • Form data validation with detailed errors

Sentry Performance + Profiling

APM & Frontend Performance

Transaction tracing, N+1 detection, slow endpoint surfacing, and frontend interaction-to-backend correlation. We use sampling strategies to control costs while preserving actionable signal.

Use Cases:

  • Identifying slow database queries and N+1s
  • Frontend interaction-to-backend correlation
  • Performance regression detection

Sentry

Error Monitoring & Performance

Real-time error tracking, performance monitoring, and release health with source maps and stack traces across frontend, backend, and edge. We use Sentry for alerts, session replay, and tracing to quickly diagnose issues and correlate them to releases and commits.

Use Cases:

  • Real-time error tracking and alerting
  • Release health monitoring with stack traces
  • Session replay for debugging user issues

UptimeRobot

Uptime Monitoring

UptimeRobot is a free uptime monitoring service that checks your website or service every minute and alerts you if it goes down.

Use Cases:

  • Website and API uptime monitoring
  • Instant downtime alerts via email/SMS
  • Status page generation for users

Vitest

Unit & Integration Testing

A fast, Vite-native test runner with first-class TypeScript and ESM support. Ideal for component/unit tests and server logic with speedy watch mode. We pair Vitest with Testing Library for DOM tests and use coverage thresholds to protect critical paths.

Use Cases:

  • Fast unit and integration testing
  • Component testing with DOM simulation
  • Watch mode with instant feedback