EcomStride

EcomStride is the public web presence and inbound-lead engine for an agency that manages Amazon marketplace accounts. Visitors move through a services catalogue, individual service pages, an about and credentials narrative, a testimonials wall and a consultation form. The site's single commercial job is to turn a cold visitor into a tracked inbound lead, then hand that lead to the operator through a private dashboard.

The data model is deliberately narrow. One persisted entity, the lead, is captured from the public form. Everything else the visitor reads, the fifteen service definitions, their long-form detail and eighty-one testimonials, lives as typed data in the repository rather than in the database, so the marketing pages render without a single database read and every content change ships through code review.

The public surface also carries a dedicated Amazon Selling Partner API data-access policy that maps each service to the specific API roles it relies on.

The same Supabase key serves the public form, which may insert a lead and read nothing, and, after authentication, the admin dashboard, which may read, update and delete. Rather than trusting the caller, every privileged path is written on the assumption that the database may silently refuse it: writes ask for their affected rows back, and an empty result is treated as a rejection, not a success.

Session continuity across React Server Components runs through the Supabase SSR cookie adapter, refreshed on each request by the proxy handler so that a server-rendered admin page and its client components share one authenticated identity. Keeping authorisation in the database rather than only in application code was the right call for a single-operator tool: the rules live in one place, and the database itself is the enforcement point.