All projects

Full stack / AI support portal

OpsDesk AI

An AI-powered IT and business support portal for small and medium-sized businesses. Employees submit and track tickets, search the knowledge base, and get troubleshooting help from an assistant that answers only from approved, published documentation, with source links.

React 19ViteTailwind CSS 4Node.js 24Express 5PostgreSQL 17Geminin8nPlaywrightDocker
Type
Full-stack web app
Roles
Employee, IT support, admin
Tests
125 API, 28 end-to-end
Data
Fictional demo company
OpsDesk AI administrator dashboard

Overview

A help desk where the AI is not allowed to guess.

Small teams rarely have an IT department, so the same questions get asked again and again. OpsDesk AI puts tickets, documentation, hardware records, and an AI assistant in one place, and keeps the assistant tied to what the company has actually written down.

Employees

Submit and track tickets, search help articles, and ask the assistant for troubleshooting steps.

IT support

Work the ticket queue, reply with public or internal notes, maintain documentation, and manage hardware.

Administrators

Manage users, review reports and audit trails, and control the AI and n8n automation settings.

Everyone

Role-specific dashboards and reports computed from SQL, with date filters and bar, line, and donut charts.

Grounded AI

The server decides what the model may cite.

The assistant is built so that a wrong answer is hard to produce and easy to spot.

  1. PostgreSQL full-text search retrieves only published knowledge base articles.
  2. The matching articles are sent to Google Gemini through a provider abstraction, with a mock provider for tests.
  3. The server, not the model, decides which sources are cited, and removes steps that have no supporting article.
  4. When the knowledge base has no answer, the assistant says so plainly instead of improvising.
  5. The assistant can draft a ticket from the chat. The employee reviews it before anything is submitted.

Security

Roles enforced in the API, not the UI.

01

Private by default

Private tickets return 404 to other employees, even when the id is guessed. Internal notes never reach employees.

02

Sessions and CSRF

Server-side, HTTP-only sessions with synchronizer-token CSRF protection and bcrypt password hashing.

03

Abuse limits

Rate limiting on sign-in and AI requests, plus Helmet security headers.

04

Append-only audit log

Database triggers stop audit records from being edited or deleted.

Automation

Notifications that cannot break the ticket system.

Ticket events go through a transactional outbox, so a ticket is saved whether or not n8n is reachable.

01Ticket event
Written in the same transaction
02Outbox worker
Retries with exponential backoff
03Signed webhook
HMAC signature, idempotent event id
04n8n
Verifies and routes the event
05Gmail
Notification email

An admin delivery monitor shows failed deliveries and offers a one-click retry.

Testing

Tested in the API, browser and model.

125 API testsNode test runner and Supertest, covering roles, validation, and edge cases.
28 end-to-end testsPlaywright, including a WCAG 2.1 AA accessibility scan with 0 violations.
11 live checksRun against the real Gemini API to confirm grounding behaviour.
4 widthsLayouts checked for overflow at 1440, 1024, 768, and 390 px.

Scope and limits

What this project is, and is not.

  • All data is fictional demo data for a made-up company. Demo accounts and passwords are for local development only.
  • Without a Gemini API key, the assistant says it is not configured and points to the knowledge base and ticket form instead.
  • Retrieval uses PostgreSQL full-text search over published articles, not vector embeddings.
  • The API refuses to start in production without secure cookies, and the demo seed refuses to run in production.

Screenshots

The app, captured from the repository.

Next projectEvalForge AI Reliability Platform