Building · KroweUT Austin '26

Product-minded engineer.
I ship things that work.

CS student and founder building Krowe — a secure portal that makes it safe for small businesses to hire a builder and ship internal systems. Seven projects shipped end-to-end. Looking for a team where craft and speed both matter.

Featured deployment

live

Krowe

krowehub.com · co-founder/CEO

A secure portal that makes it safe to hire a fast, low-cost builder — scope, pay, and ship internal systems in one workspace, with the risk contained and the work verified.

Next.jsReactTypeScriptSupabaseTailwind

users

10k

impressions

1.2s

load time

Patel Gaines Internal System

In-House Developer — Internal Tools

Internal operations platform for the property-tax consulting firm where I work — runs the outreach pipeline, referral tracking, and performance reporting the team works out of day to day, with multi-stage funnel tracking and exportable analytics. The Next.js app is hosted on AWS compute and served through a CloudFront CDN.

Next.jsTypeScriptSupabaseAWSTailwind

modules

daily

usage

clients

JarvisOS

Solo Developer

An agentic OS for AI-assisted work: a Next.js command center paired with a Fastify daemon that watches live Claude Code sessions and streams their transcripts in real time, browses the installed skill library, maps an Obsidian vault as an explorable wikilink graph, and turns finished sessions into AI recaps — triggered by editor hooks, reviewed in-app, and written back to the vault's daily notes.

Next.jsReactTypeScriptFastifyOpenAITailwind

services

<200ms

hook latency

SSE

streaming

Krowe

Active

A secure portal that makes it safe to hire a fast, low-cost builder — scope, pay, and ship internal systems in one workspace, with the risk contained and the work verified.

Tech stack

Next.jsReactTypeScriptSupabaseTailwind

Screenshots

View Live View Production

Case study

Architecture

Next.js PortalSupabase Auth

Supabase AuthPostgres + RLS

Next.js PortalServer Actions

Server ActionsOpenAI gpt-4o

Key Decisions

The portal is the product

Operators scope, pay, and ship inside one secure workspace — the portal powers the whole engagement, not just discovery

The moat is the secure portal

Isolated workspaces, in-portal data custody, and audit logs make it safe to hire a cheap, unproven AI-native builder

Open builder pool — verify, don't gatekeep

Verified profiles plus a ship-likelihood score let operators judge; trust comes from transparency and containment, not screening

Postmortem

What went wrong

First positioning leaned on a scrapped AI 'pain → scope' intake engine as the differentiator — it wasn't defensible

What improved

Refocused on the secure portal as the product and the moat — the thing that makes it safe to hire an unproven builder; structured intake survives only as a table-stakes brief

Metrics & Results

users

10k

impressions

1.2s

load Time

By the numbers

shipped

hackathons

languages

3.8

gpa

Stack

TypeScriptPythonReactNext.jsNodePostgresSupabaseAWS

Dev Tools

Claude CodeCodexGitGitHubFigmaVercelObsidianSlack

Product-minded engineer.I ship things that work.

Krowe

Architecture

Key Decisions

Postmortem

Metrics & Results

Product-minded engineer.
I ship things that work.