Can a prompt replace Knack?

Build a standalone customer or member portal app with its own end-user login, distinct from this catalogue's Caspio entry, which is about embedding widgets into an existing site rather than being its own app. Use Next.js/TypeScript with Postgres and a simple email/password or magic-link auth system. Define tables where each record has an owner field linking to the logged-in user's account. Build list and detail views that automatically filter to records the logged-in user owns — a customer sees only their own orders, a member sees only their own submissions — with a separate admin role that sees everything unfiltered. Support a basic self-service signup flow so end users can create their own accounts rather than being provisioned manually. Add a simple public-facing landing page for the portal, distinct from the authenticated app. Do not build a visual page-layout builder, a large library of pre-built portal templates, or complex multi-level organizational permission hierarchies beyond the owner/admin split — those are out of scope; this is a working two-role portal, not a fully general permission engine. Requires hosting and a database; no external API key needed.