Engineering
Deep dives on architecture, performance, integrations, and the decisions that make software dependable in daily work.
If sending the email is the only thing your form does, then an unset API key deletes the submission and shows the visitor an error. Separate capture from notification and the failure costs a notification instead of a lead.
If the limiter runs before validation, a visitor's own typos spend their allowance and their next correct submission is silently discarded. The order of honeypot, validation and limit decides who pays.
Read entryA camelCase column breaks every insert with PGRST204. Supabase's new API keys are not JWTs and belong in the apikey header. Neither mistake has to surface in your app.
Read entryMotion and visual polish can earn attention, but conversion depends on clarity, useful hierarchy, fast performance, and an obvious next step.
Read entryBuilt by LOJIK
We built these for ourselves first. What we build for you is shaped around your business.
Things we build
Maestro development preview · synthetic session data