Comparisons / Supabase ecosystem
RowShield vs MakerKit: day-one scaffolding versus day-two drift
The short version
- MakerKit sells production-shaped starter kits for SaaS products, with Supabase among supported backends: authentication flows, organisations, billing and admin screens arriving pre-assembled with considered RLS. RowShield verifies that those policies, and everything added afterwards, still hold in production, continuously.
- Choose MakerKit when — you are launching a polished SaaS quickly and want authentication, organisations and billing assembled by people who have done it repeatedly.
- Choose RowShield when — your codebase has grown beyond the kit, and you want empirical proof that template-grade security survived your migrations, generators and contributors.
RowShield rules relevant here
Head to head: MakerKit vs RowShield
| Capability | MakerKit | RowShield | Edge |
|---|---|---|---|
| Deliverable | A licensed codebase you own, extend and operate as your product’s foundation. | A monitoring service observing your deployed policies, endpoints and configuration. | Parity |
| Temporal reach | Strongest at day zero, before accumulated change departs from shipped conventions. | Every day after launch, across every migration and contributor, indefinitely. | RowShield |
| Coverage scope | The kit’s modules as delivered; custom work inherits no standing guarantees. | Whole-database posture: policies, grants, function attributes, storage buckets, auth settings. | RowShield |
| Verification method | By construction: sound patterns whose preservation depends on future discipline. | Empirical: live policy evaluation plus anonymous probing of the PostgREST surface. | RowShield |
| Divergence handling | Silent by nature: convention erosion becomes visible only when something breaks. | Regressions flagged wherever they originate, including generator-written migrations. | RowShield |
| Launch velocity | Weeks saved assembling auth, billing and organisations; genuinely decisive early on. | None offered; RowShield accelerates nothing and claims no credit for building. | MakerKit |
| Shared intent | Reduces Supabase security mistakes by preventing them in the initial build. | Reduces the same mistakes by proving the database refuses improper access thereafter. | Parity |
Column claims about MakerKit are sourced below. Where the edge is theirs, the page says so — and the sections that follow explain why Supabase teams still pick RowShield.
What MakerKit does
A MakerKit licence buys a curated codebase: authentication flows, organisations and teams, subscription billing, administrative screens and accompanying interface components, arranged so a competent team can ship a credible product in weeks. Supabase kits arrive with row level security written for their multi-tenant structures.
That last point matters for this comparison: day-one authorisation in MakerKit is genuinely considered rather than improvised, and adopting it spares most teams the work of hand-rolling tenancy. The kit accelerates construction; it does not supervise what follows.
Where the scopes differ
MakerKit hands you correct code at a moment in time; RowShield verifies correctness across all the time that follows. The distinction matters because a starter’s security properties are hereditary only while descendants obey them.
Your first bespoke feature forks the inheritance; your first AI-assisted migration forks it further. RowShield reads the live policies on schedule, probes PostgREST as an anonymous caller, and reports any weakening with the offending statement quoted and a remedy proposed.
The probe deserves particular emphasis for starter users. A policy can read as correct in review and still behave wrongly at the PostgREST boundary, where role semantics, forced RLS and filtered results interact. Testing behaviour, not just text, is how a template’s promises are actually audited rather than assumed.
Why Supabase teams choose RowShield over MakerKit
Again, sequencing rather than rivalry, yet the reasoning favours monitoring as codebases mature. Construction-time quality cannot testify about production tonight, whereas continuous evaluation can.
Consider the ordinary paths by which a kit’s discipline erodes: an organisation feature added without mirroring the template’s policy structure, a billing webhook granted broader database access than it needs, a second developer who never read the original RLS conventions because they were busy shipping. None of these are visible in the starter’s changelog, and all of them are visible in the live catalog.
Its accumulated history doubles as audit evidence that least privilege held across every release you shipped. The starter prevents the first bug; RowShield catches the fortieth prompt, the contractor’s shortcut, the urgent patch that inverted a condition. Those late catches are the ones worth having.
Where MakerKit is the right choice
Building a SaaS from an empty repository is slower and riskier than starting from MakerKit’s assembled, tested patterns, particularly for teams without strong product-engineering depth. That advantage is real and stated plainly.
The pivot: the kit accelerates the beginning, while the middle and end of your product’s life belong to whatever verifies the system as it changes. Holding that office is RowShield’s entire purpose.
Using both
Buy the kit for velocity, then attach RowShield so its guarantees are policed beyond delivery. The starter’s policies enter monitoring on day one, and every deviation, deliberate or accidental, is surfaced while it is still cheap to reverse. Teams running this combination describe a settled feeling: the template got them to market quickly, and something competent watches afterwards.
Frequently asked
- Is RowShield affiliated with MakerKit?
- No. MakerKit is an independent commercial product and RowShield is built by Veristria. Their name and materials remain their property, and our characterisation rests on public information reviewed on 2026-08-23.
- Can MakerKit and RowShield be used together?
- They complement each other cleanly: the starter constructs, the monitor verifies. Connecting RowShield after adopting MakerKit takes minutes and subjects the kit’s policies, and everything you add afterwards, to continuous evaluation.
- MakerKit’s RLS is already solid; why monitor at all?
- Solid at purchase, and subject to every migration afterwards. Generated code, contractor work and urgent fixes introduce variance the starter cannot foresee, so monitoring exists to prove the original invariant still holds in production.
Check your project in about ten seconds
Paste a URL. No signup, no writes, nothing stored.
Run the free audit