Skip to content

MyTechSupport.com

MyTechSupport.com is a website that connects people who have tech problems with people who can fix them. Clients post a job or a “bounty” (like a reward for solving a problem), and freelance tech support specialists from around the world pick up the work and get paid. It is part Upwork, part StackOverflow, built specifically for tech support. This is a real app with user accounts, real money, and live messaging — not a brochure site.

Yours. Your own platform.

https://mytechsupport.com

ThingDetail
FrameworkNext.js 16.0.10
React19.2.1
UI componentsRadix UI, Tailwind CSS
DatabaseSupabase (PostgreSQL) with 91+ migrations
PaymentsStripe Connect
EmailResend
HostingVercel
Scheduled jobsVercel Cron (notifications queue, email digests, daily stats, profile nudges, security, onboarding, job review, engagement reports)
  • Repo: ~/apps/mytechsupport/
  • Dev server: cd ~/apps/mytechsupport && npm run dev (port 3000 default)
  • Dev port (if using pop-it-open): 3200
  • Build number: 798 (as of last Explore pass)
  • Latest commit: 2026-03-31
  1. cd ~/apps/mytechsupport
  2. Edit pages and components in src/
  3. npm run dev to preview
  4. Bump the build number in TWO places (this is a gotcha specific to this repo):
    • src/lib/build-info.ts
    • src/components/layout/Footer.tsx
    • The build.txt file is the canonical source, but these two files also need to match.
  5. Commit with message format Build X: summary
  6. git push — Vercel auto-deploys
  • User roles: client, specialist, admin, super_admin
  • Job marketplace: private paid jobs between clients and specialists
  • Bounty board: public bounties anyone can claim
  • Real-time messaging between users
  • Stripe Connect payouts to specialists
  • Admin dashboard for managing users, jobs, disputes
  • Cron jobs running every day for digests, stats, security checks
  • Two-file build number bump. Easy to forget one of the two files. Consider automating this in a pre-commit hook.
  • The critical deployment rules are in OUR_SHARED_UNDERSTANDING.md, not in CLAUDE.md. Read that file before you make any deployment changes.
  • 91+ migrations. Supabase migration history is long. When adding a new migration, always test on a local or staging DB before pushing.
  • This is a real app with real users and real money. Treat deploys with more caution than the marketing sites — a bug here can cost money or break a payout.
  • Supabase URL + anon key — in Vercel environment variables, referenced in .env.local for dev.
  • Stripe secret + webhook signing secret — in Vercel environment variables.
  • Resend API key — in Vercel environment variables.
  • Full list — in shared-secrets.env on Google Drive.
  • GSC Audit (capabilities/gsc-audit) — include in the weekly health check, this is one of the highest-leverage sites for SEO fixes.
  • Send a Gmail (capabilities/send-gmail) — transactional emails technically go through Resend, but digest emails can use the Gmail capability if needed.