You will get a secure Supabase backend with row-level security and tests
Project details
Most Supabase projects ship with RLS either switched off or written by guesswork. Both end the same way.
I write the database layer properly.
What I do:
• Schema design with constraints enforced in Postgres, not just in your UI
• Row-level security policies per table and per role, written to be readable later
• Multi-tenancy where one organisation can never see another's rows
• RPCs for the operations that shouldn't be a client-side query
• pgTAP tests proving each policy denies what it should — the suite is yours to keep
• Realtime, triggers and migrations set up so your team can keep moving
I run a multi-tenant POS platform on exactly this: every venue isolated by row-level security, realtime broadcast from the database, money stored as integer minor units, with a pgTAP suite in CI.
Tell me your tables and your roles, and I'll show you where the current policies leak before you order.
I write the database layer properly.
What I do:
• Schema design with constraints enforced in Postgres, not just in your UI
• Row-level security policies per table and per role, written to be readable later
• Multi-tenancy where one organisation can never see another's rows
• RPCs for the operations that shouldn't be a client-side query
• pgTAP tests proving each policy denies what it should — the suite is yours to keep
• Realtime, triggers and migrations set up so your team can keep moving
I run a multi-tenant POS platform on exactly this: every venue isolated by row-level security, realtime broadcast from the database, money stored as integer minor units, with a pgTAP suite in CI.
Tell me your tables and your roles, and I'll show you where the current policies leak before you order.
Programming Languages
JavaScript, TypeScriptCoding Expertise
Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$145
|
Standard
$395
|
Advanced
$795
|
|---|---|---|---|
| Delivery Time | 5 days | 14 days | 30 days |
Number of Revisions | 1 | 2 | 3 |
Design Customization | - | - | - |
Content Upload | - | - | - |
Responsive Design | - | - | - |
Source Code |
About Kenneth Johannes
Full-Stack Developer | Internal Ops Tools, React & React Native
Jakarta, Indonesia - 3:25 am local time
Recent work:
• Prevented Ocean Plastic — migrating an entire ocean-bound plastic supply chain off paper. Five distinct roles (field admin, office admin, production leader, lab staff, supplier), a full audit trail with identity, timestamp, GPS and field-level diffs on every entry, QC sampling, and traceability QR scanning for downstream processors.
• Warehouse Ops — picking and stock app for an Indonesian bike-parts seller on Shopee and TikTok. Shipping-label PDFs parse client-side into pick lists; stock is derived from an append-only ledger rather than edited in place, so no count can be silently changed.
• Solute — white-label POS platform for cafés and restaurants: QR self-ordering, register, kitchen display and queue TV in one real-time system, each venue on its own themed subdomain.
• TXE Express — operations PWA for a courier company, built end to end as sole developer.
I also ship consumer software — Cutling, a native iOS and macOS clipboard manager.
If you have a process running on paper or a spreadsheet that needs to become software people can trust, that's the work I do best.
Steps for completing your project
After purchasing the project, send requirements so Kenneth Johannes can start the project.
Delivery time starts when Kenneth Johannes receives requirements from you.
Kenneth Johannes works on your project following the steps below.
Revisions may occur after the delivery date.
Map your tables and roles
I write down who should be able to read and write each table, and show you where your current policies let the wrong rows through.
Write the policies and constraints
Row-level security per table and per role, constraints enforced in Postgres rather than only in your UI, and RPCs for anything that shouldn't be a client-side query.