---
title: "Denys Zaichenko (@madsalttech) | Hashnode"
description: "A senior full-stack developer specialising in multi-tenant SaaS apps and AI agents. Read the latest articles by Denys Zaichenko on Hashnode."
url: "https://hashnode.com/@madsalttech"
---

@madsalttech

# Denys Zaichenko

@madsalttech · Lisbon, Portugal · Joined October 2026

A senior full-stack developer specialising in multi-tenant SaaS apps and AI agents.

### [A validation layer for AI invoice extraction, in Python](https://madsalt.hashnode.dev/a-validation-layer-for-ai-invoice-extraction-in-python?utm_source=hashnode&utm_medium=feed)

What to run after the model reads an invoice, in what order, and what each check caught in my test of 30 invoices.

6 min read · [madsalt.hashnode.dev](https://madsalt.hashnode.dev/a-validation-layer-for-ai-invoice-extraction-in-python?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/a-validation-layer-for-ai-invoice-extraction-in-python/6afb0a8d4c910ad7508227b7) [13h ago](https://hashnode.com/posts/a-validation-layer-for-ai-invoice-extraction-in-python/6afb0a8d4c910ad7508227b7)

### [Five Lovable security fixes, as before and after SQL](https://madsalt.hashnode.dev/five-lovable-security-fixes-as-before-and-after-sql?utm_source=hashnode&utm_medium=feed)

The diffs I apply most in Lovable and Supabase apps: policies, grants, views, roles and a NULL that skipped a check.

5 min read · [madsalt.hashnode.dev](https://madsalt.hashnode.dev/five-lovable-security-fixes-as-before-and-after-sql?utm_source=hashnode&utm_medium=feed)

[13h ago](https://hashnode.com/posts/five-lovable-security-fixes-as-before-and-after-sql/6afb0a3f4c910ad750812a1c)

### [Audit your Supabase project from the SQL editor](https://madsalt.hashnode.dev/audit-your-supabase-project-from-the-sql-editor?utm_source=hashnode&utm_medium=feed)

Five catalog queries that show what your public key can reach, and how to read each result.

5 min read · [madsalt.hashnode.dev](https://madsalt.hashnode.dev/audit-your-supabase-project-from-the-sql-editor?utm_source=hashnode&utm_medium=feed)

[13h ago](https://hashnode.com/posts/audit-your-supabase-project-from-the-sql-editor/6afb09e64c910ad75080203b)

### [Supabase anon key vs service role key: what each one opens](https://madsalt.hashnode.dev/supabase-anon-key-vs-service-role-key-what-each-one-opens?utm_source=hashnode&utm_medium=feed)

TL;DR. The anon key, now called the publishable key, is meant to be public. It maps to the anon or authenticated role, and your RLS policies decide what it sees. The service role key, now the secret k

6 min read · [madsalt.hashnode.dev](https://madsalt.hashnode.dev/supabase-anon-key-vs-service-role-key-what-each-one-opens?utm_source=hashnode&utm_medium=feed)

[Nov 2](https://hashnode.com/posts/supabase-anon-key-vs-service-role-key-what-each-one-opens/6ae865e4dee7dce8b2954752)

### [Supabase exposed schemas: what the list opens up](https://madsalt.hashnode.dev/supabase-exposed-schemas-what-the-list-opens-up?utm_source=hashnode&utm_medium=feed)

TL;DR. The Exposed schemas list in Supabase decides which schemas the Data API serves to anyone holding your public key. The default is public and graphql\_public. Every table, view and function in a s

5 min read · [madsalt.hashnode.dev](https://madsalt.hashnode.dev/supabase-exposed-schemas-what-the-list-opens-up?utm_source=hashnode&utm_medium=feed)

[Oct 26](https://hashnode.com/posts/supabase-exposed-schemas-what-the-list-opens-up/6adf556e5bb6fa9a24a4ea7f)
