Noodlesticks
Talk with us

Behind the chopsticks

What we do for nerds

The unglamorous, deeply satisfying stack we actually run — and the workflow that keeps clients from becoming tickets.

01 — Hosting

Servers that answer to a human, not a status page.

Static sites and app backends on Linode, usually behind nginx. TLS, sensible backups, systemd (or Docker when it earns its keep), and deploys that don’t require a PhD in YAML archaeology.

  • nginx reverse proxy + static roots
  • Let’s Encrypt / managed certs
  • Linode VMs + managed Postgres when forms need a real DB
  • You get someone who already knows the box when DNS gets spicy
Playful illustration of a server rack styled like chopsticks

02 — Sites

Hugo by default. React only when it pays rent.

Most marketing sites are content + polish. We ship them as Hugo static builds — fast, boring in the best way, and drop-dead simple to host on the same nginx story as everything else.

  • Hugo extended (your friends Forge & personal sites already live here)
  • Hand-rolled layouts when themes would fight the brand
  • CI-friendly hugo --minify → public/ → server
  • Next.js / app shells only if the product actually needs a client runtime
Illustration of a browser window with a chopstick cursor clicking a button

03 — Form Platform

POST goes in. Humans get notified. Postgres remembers.

Our multi-tenant form stack (working name: Form Platform) is FastAPI + PostgreSQL + SendGrid. Per-domain admin, roles, CSV export, spam defenses, file uploads when needed. Already running for real clients — churches, clinics, the works.

  • Forms on your domain (/f/contact, etc.)
  • Team notify + submitter auto-reply
  • Admin inbox with roles (admin / reviewer / read-only)
  • Dogfooded on this very site’s “Talk with us” form
Illustration of a form flying into a database mailbox

04 — Workflow

Scope → ship → stay. No “upgrade to Pro” boss fight.

We sell a relationship on purpose. That means fewer dashboards for you to abandon, and more “hey, can we add an open-house QR form by Friday?” energy. Billing portals can show up later; the loop looks like this:

  1. Talk — what you’re shipping, domain, timeline
  2. Shape — hosting, site, forms, or a sensible mix
  3. Stand up — nginx, Hugo, form-platform site + forms
  4. Hand off — admin logins, QR links, “how to change copy”
  5. Stay — tweaks, new forms, the weird DNS Tuesday
Illustration of a workflow looping back to a person at a laptop

Stack scrapbook

The short list, for the résumé skimmers.

Hugo nginx Linode FastAPI PostgreSQL SendGrid systemd / Docker GitHub Actions Cloudflare (when it helps)

Still reading? You’re our people. Talk with us — bring your domain drama and your favorite terminal font.

Talk with us