Excited to share some of the backend work I've been doing lately with Supabase! 🚀

Here's a look at what went into building a production-ready backend from scratch:

🗄️ Database Schema Design Designed a relational schema with multiple interconnected tables: profiles, notes, reminders, conflicts, and a dedicated user_keys table for encryption key management. Every table has proper foreign key relationships, timestamps, and nullable/non-nullable constraints enforced at the DB level.

🔒 Row Level Security (RLS) Every single table has RLS enabled with two policies: users can only access their own rows, and anonymous access is blocked entirely. No exceptions. Security is enforced at the database layer, not just the application layer.

🔑 Auth & Email Flows Set up Supabase Auth with email + OAuth support, including full PKCE flow for secure token exchange. Configured deep link redirects for email confirmation and password reset flows, all tested end to end.

⚡ Edge Functions Built and deployed multiple Supabase Edge Functions handling AI processing pipelines, including JWT validation at the top of every function before any processing begins. The OpenAI API key lives exclusively in Supabase secrets, never in the app or any config file.

🔄 Merge Pipeline Built a follow-up note merge pipeline as an Edge Function. New facts are appended to existing profiles, duplicates are detected and skipped, conflicts are logged, and resolved reminders are handled gracefully.

📦 Migrations All schema changes go through versioned migration files under source control. No manual dashboard changes. CI/CD triggers migrations automatically on merge to main.

🔐 Encryption Architecture Client-side AES-GCM encryption via CryptoKit. Plaintext never sits in the database. Encryption keys are stored in a dedicated RLS-scoped table, fetched after login, and held in memory only for the session duration.

Still a lot more to share about this project. Excited to talk about it publicly when it launches! 👀

Interesting work! Nice 🔥 Have there been any bottlenecks so far in testing?

Digital Concrete: Architecting a Structured SMTP Gateway for Equine Health

Equine health records are traditionally a black hole of lost paper and forgotten notes. In the field, data entry is a battle against the elements - mobile apps often fail here because they ignore the physical reality of a vet’s work. When I architected the ESQ Engine, I didn't build another complex interface for professionals to fight with. I built a Structured SMTP Gateway that turns the world’s most universal protocol - email -into a surgical data-entry tool.

My architectural philosophy for this project was "Zero-Friction Integrity." In a barn, a specialist won't tap through twenty screens to log a medical report. They want to type a quick email from their desktop or phone and be done. The ESQ Engine meets them exactly where they are, but it enforces a rigid, database-ready structure on the backend. It’s a passive hub that translates human intent into atomic records without the need for a UI.

At the core of the engine is Unique Horse Hashing. Every horse in the system is assigned a unique, private email address that acts as its personal data vault. But receiving mail is only the beginning; we needed a security layer that acts as a digital bouncer. To protect data privacy, I implemented SMTP-level Verification. The system performs a real-time handshake: if the sender’s email doesn't match a registered, verified professional in our database, the engine silently drops the connection. This ensures that every entry in a horse’s history is authenticated at the source.

Once authorized, the system transitions from security to precision. Using a high-performance parsing logic, the ESQ Engine scans the incoming text for specific patterns. It extracts the horse's name, the service performed, and the Soundness Score with surgical accuracy. This ensures that even though the input method is fluid and familiar (email), the output is absolute. The data is parsed, validated, and instantly mapped to the horse's unique identifier in the database—all without the professional ever seeing a spreadsheet or a login screen.

The lifecycle concludes with Automated Sync and Notification. The moment a record is committed, the engine triggers a cleanup routine: attachments like radiographs and CT scans are stripped, optimized, and filed into secure S3 storage. Simultaneously, a push notification is dispatched to the horse owner. This creates a real-time, verified medical history that is unhackable by human forgetfulness.

I specialize in taking fragmented, manual industries and building the underlying concrete that holds their data together. The ESQ Engine doesn't just store notes; it creates a trusted, chronological audit trail for the life of an animal. It’s a solution that proves the most sophisticated technology is often the one you can’t even see. If your infrastructure relies on users remembering to use a clunky app, you’re building on sand. I build on logic.

Visuals looking neat. Good work!