FormKin

Every new public-facing form required developer involvement — configuring the kintone connection, building the HTML, handling the submit logic, and deploying the page. Non-technical users had no way to create forms independently, which created a constant backlog of small requests that should never have needed engineering attention.

The product had to keep kintone API tokens server-side at all times — the public form page needed to work without exposing credentials to the browser. Multi-tenancy also meant each user's forms had to be strictly isolated at the database level, not just the application layer.

• kintone API tokens must never reach the client, even for form rendering
• Form field structure is generated dynamically from the live kintone schema
• Public form access must work without requiring respondents to create accounts
• RLS policies enforce per-user data isolation regardless of application-layer bugs

The architecture separated the admin surface (where users configure forms) from the public surface (where respondents fill them out). Form metadata and API tokens live in Supabase behind RLS. The public form page fetches field schema server-side, renders via a FormRenderer component, and submits back through a server API route — the kintone token never touches the client.

• Server-side kintone field fetch auto-generates the FormRenderer at request time
• Token-based public URL — /f/[access_token] — no respondent login required
• Submit handled by a server API route; kintone token stays server-side throughout
• Plan gating enforced at form creation time, verified against Supabase user_plans

Magic link OTP was chosen deliberately over password auth. The product is used by operators who log in occasionally to manage forms — not daily active users who memorize passwords. Passwordless auth removed a whole class of support requests and kept the session model simple.

• Supabase Auth handles the OTP flow with no custom token logic required
• One-time links reduce the support surface and eliminate credential reset flows
• Session management is compatible with Next.js App Router server component patterns

Non-technical users can now create, test, and publish forms without writing code or filing a ticket. The form-to-kintone pipeline is deterministic — kintone field config drives form generation, and submission routes back to the connected app automatically. The developer dependency for routine form creation is gone.