Marketing site + product app
Next.js App Router on Vercel for marketing, separate Supabase-backed app for the product. Shared design system, separate deploy targets, single domain via Vercel rewrites.
§
§ · location · sf web dev
Web development, San Francisco.
Next.js, React, and full-stack engineering for SF brands where the site is the product. SOC 2-ready, HIPAA-aware, and integrated with the SF infrastructure stack: Stripe, Vercel, Supabase, MUX, Clerk.
§ 01 · sf web dev context
SF builds on its own infrastructure.
When you take an SF web development engagement, you inherit a stack the city built. Next.js on Vercel, Supabase for Postgres-backed accounts, Stripe for everything billing, MUX for video, Clerk when Supabase Auth doesn't fit. Other markets ask "should we use this?"; SF asks "why aren't we already?". Engagements lean integration-heavy with measurable infra performance budgets.
§ 02 · sf stack patterns
Four recurring stacks we ship in SF.
Headless commerce + content
Hydrogen on Oxygen for product + cart, Sanity or Contentful for editorial, custom Postgres for accounts and entitlements. The integration layer is the work.
Multi-party Stripe Connect
Marketplaces, creator-tools, and B2B SaaS launching consumer wings. Stripe Connect for multi-party billing, Shopify or custom Postgres for catalog, complex webhook orchestration.
Compliance-first health / fintech
SOC 2 Type II, HIPAA-eligible Supabase, audit log infrastructure, encrypted-at-rest custom data layers, pen-test-ready architecture documented from week one.
§ 03 · web developer near me in san francisco
Looking for a web developer near you in SF?
Our SF engineering team serves brands across San Francisco, the East Bay, and down the Peninsula. Discovery happens on-site in SOMA, the Mission, FiDi, or Palo Alto. Pacific Time coverage Mon–Fri 9–6 with 48-hour war-room support for major launches. Past SF engagements covered fintech compliance, health-tech HIPAA infrastructure, hardware-DTC site relaunches, and creator-tools commerce flows.
§ 04 · questions
Five answers.
Why Next.js for SF web dev specifically?
Vercel is headquartered in SF, and most SF brands' technical leadership is one or two hops from a Next.js core contributor. Choosing the framework that the local engineering culture already uses cuts hiring friction, reduces onboarding cost, and removes the "why this stack" conversation from the first meeting.
Do you handle SOC 2 / HIPAA / PCI engineering?
SOC 2 Type II readiness for the engineering side — audit logs, encrypted-at-rest data, secure CI/CD, pen-test scope. HIPAA-eligible Supabase configurations. PCI-DSS scope reduction via Stripe Elements + Connect. Compliance certification itself is your auditor's call; we ship the engineering they ask for.
What does an SF engineering retainer cover?
Monthly engineering bucket priced by hours, with rollover rules and a quarterly in-person review in SF. Typical scope: feature work, refactors, third-party integration changes, security patches, performance budget enforcement.
Are you on-site in SF?
Pacific Time coverage with quarterly in-person reviews in SF and at-launch on-site for major releases. Day-to-day engineering runs remote with same-PT working hours, weekly Friday demos, and Slack response within the working day.
How long is a typical SF Next.js build?
12–18 weeks for a marketing site + lightweight app, 18–24 for a full-stack product with custom data layer, 20+ for compliance-heavy health or fintech where audit-readiness work runs in parallel with feature work.
§ 05 · scope the sf engineering
Stack-fluent. Compliance-aware.
related