// BRAXSYS WEB · AI · INFRASTRUCTURE

Web & AI systems, drawn to spec.

Fixed-scope websites and internal tools, engineered end-to-end and shipped in weeks — one systems engineer who owns the whole stack, from data model to design system.

STATUS // AVAILABLE Q2 FIXED-SCOPE · SCOPED IN WRITING
TITLE BLOCK
Project
BRAXSYS
Discipline
Web · AI · Infra
Drawn by
James Grant
Response
≤ 48h · Mon–Thu
SPEC-REV 4.7 SHEET 01
[ 02 ] // SERVICES

Engagement models — scoped, typed, shipped.

Two primary ways to work together. Each is priced and scoped up-front; no hourly surprise line items.

// PRIMARY
[ 01 ] ACTIVE

Custom Web & Application Development

End-to-end delivery of production web systems — from schema to ship. Typed, performant, and accessible by default.

  • SvelteKit / Next.js, TypeScript, Postgres
  • Server-driven, containerized deploys
  • Design systems, not one-off pages
  • Auth, webhooks, and integrations — wired correctly
// SECONDARY
[ 02 ] ADD-ON

Fedora Migration & Hardening

Move off macOS or Windows onto a Fedora workstation that boots fast, runs cool, recovers from mistakes, and locks down its network — set up in one hardening pass refined on my own daily-driver hardware.

  • One-pass hardening — firewall, automatic security + system updates, codecs — so the machine maintains itself
  • OS-wide undo: automatic snapshots with boot-menu rollback (a bad update is a two-minute fix, not a reinstall)
  • Hardware that just works — Secure-Boot-signed NVIDIA, Wi-Fi/firmware, and battery, thermal & deep-sleep tuning
  • Hardened networking — app-level firewall, VPN kill-switch, and secure remote-access mesh, no leaks
  • A desktop shaped for real work — tiling layouts, per-app workspaces, a printed quick-reference, and a support window
[ 03 ] // INFRASTRUCTURE

The stack behind the studio.

Self-hosted, observed, and running now — shown as evidence, not a diagram. This is the operational spine the work ships on.

// Operator-gated · credentials required
[ 01 ] Source & CI
Operational

Self-hosted Git + CI/CD

Forgejo with a self-hosted Actions runner. Every pull request runs a design-system gate before it can merge.

  • Forgejo
  • Actions
  • Docker
Operator-gated
[ 02 ] Automation
Operational

Workflow Automation

n8n orchestrates lead intake, enrichment, and outreach — the same pipeline this site posts into.

  • n8n
  • Webhooks
  • Postgres
Operator-gated
[ 03 ] Delivery
Operational

Deploy Platform

Coolify builds container images and rolls production over behind Traefik — zero-downtime, on merge.

  • Coolify
  • Docker
  • Traefik
// Private · internal
[ 04 ] Observability
Operational

Uptime & Monitoring

Uptime Kuma watches every service and records health continuously.

  • Uptime Kuma
// Private · internal
[ 05 ] Network
Internal

Zero-trust Mesh

Tailscale gives private, keyless access to every host and service — nothing extra exposed to the public internet.

  • Tailscale
  • WireGuard
// Private · internal
[ 06 ] Edge
Internal

Reverse Proxy + TLS

Traefik terminates TLS and routes every Braxsys subdomain automatically.

  • Traefik
  • Let's Encrypt
// Private · internal
[ 04 ] // ABOUT

Engineer first. Designer when it ships the work.

Seven years shipping production software across web, mobile, and internal tooling. I take work end-to-end — the kind that needs someone equally comfortable in a database schema, a TypeScript generic, and a visual hierarchy.

Preference for typed languages, trunk-based workflows, and observability wired in before launch. I think in diagrams and ship in small increments.

// PHILOSOPHY — "The code is the spec. Everything else is notes."

// PROFICIENCIES

Frontend

  • SvelteKit
  • Next.js
  • React
  • TypeScript
  • TailwindCSS

Mobile

  • Flutter
  • Dart
  • SQLite

Backend & Data

  • Node.js
  • Postgres
  • Drizzle
  • better-auth
  • Sanity

AI & Automation

  • Claude API
  • n8n
  • PowerShell

Platform

  • Docker
  • Coolify
  • Vercel
  • Forgejo Actions
  • Tailscale

Practice

  • Automated testing
  • Trunk-based dev
  • Accessibility (WCAG AA)
  • Observability
[ 05 ] // CONTACT

Start a project.

Outline the problem, the constraints, and the timeline. The tighter the brief, the faster the reply.

// RESPONSE SLA
≤ 48h · Mon–Thu
// ENGAGEMENT MINIMUM
2 weeks · scoped in writing
// LEAD-REQ
// ENCRYPTED IN-TRANSIT / NEVER SHARED