Technology Stack

The real technologies NexaStack Technologies builds with, organised by category — including what is deliberately not used, and what is planned but not yet installed, stated plainly rather than implied.

Frontend

The interface layer — server-rendered pages and typed components.

• Next.js
• React
• TypeScript

Backend

The application server handling requests, routing and business logic.

• Node.js
• Express.js

Database

Where content, enquiries and quotations are stored.

• MongoDB Atlas
• Mongoose

Authentication

How admin sessions are verified and kept secure.

• JWT
• bcrypt
• HTTP-only Cookies

UI and Styling

The design system's building blocks — utility styling, accessible primitives and type.

• Tailwind CSS
• Radix UI
• Geist Sans
• Geist Mono

Development Tools

The tooling that keeps the codebase consistent and versioned.

• ESLint
• Prettier
• pnpm
• Git & GitHub

Forms and Validation

Form schemas are written once in Zod — installed and real, shared between the web app and the API so client and server validate against the exact same rules. React Hook Form and @hookform/resolvers are the intended client-side form layer per the project's architecture, but neither package is installed in this codebase yet.

• Zod

State Management

No global state library — deliberately. Public pages read data with native fetch in Server Components; filters, pagination and search live in the URL via search params, kept shareable and back-button correct. TanStack Query is the intended layer for admin-side caching and mutations, but it isn't installed yet. Redux, Zustand, Jotai and MobX were evaluated and explicitly ruled out (root CLAUDE.md section 5) — URL state and, eventually, TanStack Query cover the real need without one.

• Native fetch
• URL Search Params

Testing

No test runner, test files or accessibility-testing tool are installed in this repository yet — testing here is genuinely unconfigured today, not partially built. The intended practice, once in place, covers unit tests for schemas and service-layer logic, integration tests for auth, contact and quotation endpoints, an end-to-end smoke test of the contact and quotation flows, and axe-core accessibility checks on key pages (root CLAUDE.md section 20).

Nothing installed yet in this category — see the description above for what’s intended.

Deployment Platforms

Where the site, API, database and media actually run.

• Vercel
• Render
• MongoDB Atlas
• Cloudinary