Case study: building hedraup.com with eweb
A multi-page vi/en SaaS site with a signed-in app, admin RBAC and an API, from template to production in one evening.
Visit hedraup.comOne evening
from cloning the template (21:30, 10 Oct 2026) to production on hedraup.com
0 FAIL · 0 WARN
qa-crawl on production: 28 pages, 874 links, 288 anchors (11 Oct 2026)
4 hosts
site, www, admin, api — one Next.js app, HTTPS, vi/en
sin1
functions moved next to Supabase Singapore after eweb flagged the region
The problem
Hedra Up needed a marketing site, Google sign-in, an app to compose posts for many social networks, an admin and an API. One person, no wish to design from scratch.
What eweb did
8-question brief → eweb-setup picked the Velora template (MIT) for a saas site → clone and adapt: vi/en i18n, route table, single proxy file, Supabase migrations with RLS, admin and API. The agent did the rest from ADAPT_TODO.md.
QA before shipping
next build as a gate, qa-crawl on the Vercel URL: broken links, anchors, placeholders, lang attribute, 320px horizontal scroll. Production on 11 Oct 2026: 28 pages, 874 links, 288 anchors, 0 FAIL, 0 WARN.
Post-build
JSON-LD, cookie-free Vercel Analytics, consent banner for GA4, CSP/HSTS, Supabase Advisor with 0 errors, IndexNow. eweb also flagged functions running in iad1 while the DB was in Singapore; moving to sin1 made the app much faster.
Real screenshots
