SW Business Solutions Platform

The SWBS Platform is the digital backbone of SW Business Solutions: a company platform built entirely in-house, made up of three closely interlocking applications in a Git submodule monorepo.

Architecture: the parent repository swbs-platform manages three independent sub-repositories as Git submodules: apps/api (NestJS backend), apps/website (public Next.js website) and apps/admin (Next.js admin dashboard). Each sub-repository is deployed and versioned independently, but they share a common API contract.

Backend (NestJS 11 + Fastify 5): the REST API is built on NestJS with Fastify as HTTP adapter for maximum performance. MongoDB 7 with Mongoose 8 as ODM, Redis 7 for session and API response caching, BullMQ for asynchronous job queues. All content — technologies, services, projects, blog posts, team, clients, industry solutions, case studies and locations — is managed through typed REST endpoints. OpenAPI/Swagger documentation is generated automatically from the NestJS decorators.

Public website (Next.js 15): an App Router website with React Server Components for maximum performance. Server-side rendering for dynamic content, static site generation with ISR for content pages. Bilingual (German/English) with next-intl and URL-based routing. Schema.org JSON-LD for Google rich snippets (Article, FAQPage, LocalBusiness, TechArticle). Server-side pagination with search and sorting for 200+ technologies.

Admin dashboard (Next.js 15): a complete CMS dashboard with TanStack Query for optimistic state management, shadcn/ui as the component library, and React Hook Form plus Zod for form validation. All 15+ content types are editable from the dashboard.

DevOps: continuous deployment via GitHub Actions — API and admin on Railway, website on Vercel. S3-compatible media management with CDN delivery.

The biggest technical challenge was keeping three independent repositories in sync while maintaining type safety across system boundaries. The API had to serve the public website (tuned for performance and SEO-friendly data structures), the admin dashboard (tuned for developer experience) and future mobile clients at the same time.

Further challenges: correct server-side rendering of dynamic content alongside static generation in Next.js 15; GDPR-compliant implementation including consent management and a privacy API; and a structured SEO setup with JSON-LD across every content type.

Unified TypeScript types at the API boundary via OpenAPI/Swagger specs that are binding for both the backend and the frontend clients. Strict contract-first development with DTO classes on the NestJS side and generated types on the frontend side.

For Next.js: a hybrid rendering strategy — RSC (React Server Components) for content pages, client components for interactive features such as search and filtering. The technologies page uses genuine server-side pagination through the API rather than loading everything on the client.

GDPR: a dedicated privacy controller with data export, deletion requests and consent management. All personal data (contact enquiries) is deleted automatically after six months.