Web application development

A web app is SaaS, an internal tool, a dashboard, a B2B portal. Not a brochure site with CMS, but an interactive product users work in daily.

What's included

• Architecture and data model.
• UI kit and design system.
• Auth (password, OAuth, 2FA, SSO).
• Roles and permissions.
• Multi-tenancy if needed.
• API (REST or GraphQL) with docs.
• PWA mode for mobile.
• CI/CD pipeline.
• Monitoring (Sentry, metrics), alerts.

Use cases

• SaaS — multi-tenant, billing, self-service signup.
• Internal tool — single-tenant, deployed on client infra.
• B2B portal — for customers or partners on top of your business.
• Dashboard — real-time data visualization.

Technical stack

• Frontend — React 18 + TypeScript or Vue 3 + TypeScript. Next.js / Nuxt 3 for SSR, Vite for SPA.
• State — TanStack Query for server data, Zustand/Pinia for UI state.
• UI kit — shadcn/ui, Radix, or custom design system. Tailwind CSS as foundation.
• Backend — Node.js (NestJS / Fastify) or PHP 8.2 (Symfony). REST + OpenAPI spec.
• Database — PostgreSQL 16+ as primary. Read replica for analytics at scale.
• Cache — Redis for sessions, query cache, queues.
• Search — PostgreSQL FTS, Meilisearch or Elasticsearch — picked for volume.
• Realtime — WebSocket (Socket.io / native ws) or SSE. Depends on direction of communication.
• Auth — JWT + refresh token rotation, OAuth2 (Google, GitHub, MS), SAML SSO for enterprise.
• Permissions — RBAC via CASL or custom. Multi-tenancy support.
• Files — S3 (AWS / regional). Pre-signed URLs for secure uploads.
• Queues — BullMQ / RabbitMQ for background jobs, broadcasts, syncs.
• PWA — service worker with cache-first for static, stale-while-revalidate for HTML, offline fallback.
• Deploy — Docker + Compose / Kubernetes for scale. CI/CD via GitHub Actions.
• Monitoring — Sentry, OpenTelemetry, Prometheus + Grafana, structured logs in Loki.