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
I build typed, performant web applications end-to-end: schema, server logic, and the design system they ship on. Recent builds are below, along with how to start one.
Two primary ways to work together. Each is priced and scoped in writing before we start; no surprise hourly line items.
End-to-end delivery of production web systems, from schema to ship. Typed, performant, and accessible by default.
Move off macOS or Windows onto a tuned Fedora workstation: dotfiles, dev tooling, and daily drivers configured.
Self-hosted, observed, and running now — shown as evidence, not a diagram. This is the operational spine the work ships on.
Forgejo with a self-hosted Actions runner. Every pull request runs a design-system gate before it can merge.
n8n orchestrates lead intake, enrichment, and outreach — the same pipeline this site posts into.
Coolify builds container images and rolls production over behind Traefik — zero-downtime, on merge.
Uptime Kuma watches every service and records health continuously.
Tailscale gives private, keyless access to every host and service — nothing extra exposed to the public internet.
Traefik terminates TLS and routes every Braxsys subdomain automatically.
Ten years shipping production web systems across fintech, infrastructure, and tooling. I take work end-to-end: 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.
Outline the problem, the constraints, and the timeline. The tighter the brief, the faster the reply.