Back to Triage – Bug & Feature Tracker

Next.js App

A One-time purchase plan for Triage – Bug & Feature Tracker.

$29
One-time purchase

What's included

The complete Triage app: Next.js 16 source with sign-in, members and roles, projects and issues, the landing page and its artwork, demo mode, the SQLite schema, 37 tests, a Dockerfile, README, SETUP guide and licence.

Trust report

v1.0.0
One-click deploy
Updated < 30d
Last tested
Pending
Human review
Pending
Install estimate
15 min
Support SLA
Not set
Refund rate
Not enough data
Install success
Not enough data
Deploy targets
docker
vps
fly-io
railway
render
Compatibility
react
19
next.js
16
node.js
>=22.13
typescript
5.9
$29
One-time

✓ Instant download

✓ Full source code

✓ Documentation included

Deploy

Tech Stack

Language
Framework
Tool

Why Next.js App for Triage – Bug & Feature Tracker

Framework advantages, typical use cases in this domain, and how this plan compares to the alternatives.

Triage, the Next.js App

How it is built

Triage is a single Next.js 16 App Router project. Server Components read the database directly and Server Actions validate input and write it; there is no separate API, client-side data fetching or browser storage. The data layer uses Node.js's built-in node:sqlite module in WAL mode with a busy timeout and foreign keys on. All SQL is parameterised, sort orders come from an allow-list, and related writes run in one transaction. The schema (projects, issues, comments, activity, users, sessions) is created and upgraded on start, so an existing database moves forward without a migration step.

Sign-in, sessions and roles

Authentication is written in the project with node:crypto, not an auth library. Passwords are stored as self-describing scrypt hashes with a per-user salt and are compared in constant time; an unknown email is checked against a decoy hash so it takes as long as a wrong password. A session is 32 random bytes in an httpOnly, SameSite=Lax cookie that lasts 30 days (Secure in production, or COOKIE_SECURE=false for plain-HTTP self-hosting); only its SHA-256 hash is stored, and expired sessions are deleted. A small proxy.ts sends signed-out visitors to the sign-in page, while the real check, requireUser() or requireAdmin(), runs in the protected layout, at the top of every protected page and as the first statement of every Server Action. A static test walks every "use server" export and fails if one is unguarded; only sign-in and first-run setup are exempt. The next parameter after sign-in accepts same-site paths only. Failed sign-ins are limited to 10 per IP and email in 15 minutes.

The first visit opens /setup, which creates the first admin inside a write transaction and refuses once any user exists. Admins add members with an initial password, change roles and remove members; Triage refuses to remove you or the last admin. Changing your password signs out your other sessions.

Demo mode

DEMO_MODE=true seeds a fictional team (six projects, forty issues, comments and history), adds an admin and a member account shown on the sign-in page with one-click buttons, shows a "data resets every hour" banner and wipes and reseeds everything every DEMO_RESET_MINUTES (default 60) and on start. The demo accounts' passwords and roles can't be changed and they can't be removed, so the next visitor can always sign in. This is how the public demo at triage.mvp.sale runs.

Running and deploying it

You need Node.js 22.13 or later and pnpm 10. pnpm dev starts an empty workspace; pnpm dev:demo starts the demo. The Dockerfile builds a standalone production image that runs as a non-root user, keeps the database at /app/data/triage.db on a volume and has a health check on /api/health. Serve it behind HTTPS so the session cookie stays Secure, and make sure your proxy sets X-Forwarded-For so the sign-in throttle sees real addresses. SETUP.md covers environment variables, backups of the SQLite file, rebranding, tests and troubleshooting.

Limits to know about

There is no email at all, so no invitations or password-reset links: admins hand out initial passwords. If the only admin forgets their password, SETUP.md shows how to clear the accounts from the command line and run setup again; projects and issues are kept. There are no attachments, integrations or real-time updates, one workspace per install, and the sign-in throttle lives in the server's memory, so it resets on restart and is per process.