Postgres guides and the Australian-owned SaaS blog
Practical guides for Australian founders and developers, building the backend, choosing the stack, and keeping your data Australian-owned under the Privacy Act.
Building on WattleDB right now? The developer guide covers connecting, generating a REST API from your schema, JWT auth with Row-Level Security, and migrations.
How to build a SaaS in Australia (2026): the Australian-owned stack
Every SaaS backend has the same six layers, database, auth, APIs, storage, email, backups. In Australia there's a seventh that decides which customers you can sell to. Here's how to build all of it, Australian-owned from day one.
Where your users' logins live: Auth0, Cognito, Firebase, Supabase Auth, Clerk and Kinde
Six sign-in providers compared on who owns them, where your users' records sit, which law reaches them and what they cost, for the security questionnaire your next customer sends.
Passwords and the Privacy Act: what APP 11 expects
Stored passwords are personal information. What APP 11 asks of them after the 2024 amendments, the reasonable steps NIST SP 800-63B points to, and when credential stuffing becomes a notifiable breach.
Moving off Supabase Auth today: keep your users, keep auth.uid()
Bring your users and your RLS policies across: export the bcrypt hashes, recreate auth.uid(), sign tokens yourself, and know what does not move (sessions, OAuth app settings, MFA factors, email templates).
Why your Postgres query is slow: reading EXPLAIN ANALYZE
Nearly every slow query gives itself away in its plan. The three numbers that matter, the loops trap that makes a "fast" node cost two seconds, and the five plan shapes behind most slowdowns, with the fix for each.
Postgres indexing: why your index isn't being used
You added the index and the query is still slow. Ten rules that cover most cases: composite column order, expression and partial indexes, the casts and wildcards that hide an index, and how to find the ones you don't need.
Schema migrations without downtime
The migration that takes your site down is rarely the slow one, it's the instant ALTER TABLE that waited behind a long query and queued every request behind it. Lock timeouts, NOT VALID constraints, batched backfills, expand-contract.
PostGIS for Australian data: GDA2020, MGA zones and distances
Australia moves about 7 cm a year, so it has two modern datums and a lot of location code that is a metre or two out. Geography columns in GDA2020, radius and nearest-first queries, GDA94 conversion, MGA2020 zones and suburb lookups.
Build an AI Q&A app with pgvector and Postgres (RAG guide)
A beginner tutorial. Store help articles in PostgreSQL, find the closest chunks with pgvector, and have a model on your own computer answer from them, with sources. Tested Python code included.
pgvector in Australia: keep embeddings in your own Postgres
Store and search AI embeddings next to the rows they describe: HNSW indexes, filtered search, row-level security, halfvec over 2,000 dimensions, measured storage per row, and hybrid search with keywords.
Full-text search in Postgres, without another service
Before you add a search cluster and a sync pipeline, check what the database already does: tsvector generated columns, GIN indexes, user-safe query parsing, ranking, snippets and fuzzy trigram matching, plus the honest limits.
JSONB in Postgres: when to use it, how to index it
Postgres will store your whole app in one JSONB column. That doesn't mean you should. Where JSONB wins, GIN vs expression indexes, promoting hot keys to generated columns, and the gotchas that bite six months in.
timestamptz vs timestamp: Postgres time zones done right
One column-type decision decides whether yesterday's total is correct, whether it's correct in Perth, and whether it stays correct after the first Sunday in October. What Postgres really stores, and the three rules that keep Australian data straight.
How data actually leaks, and the controls that stop it
2024 was Australia's worst year on record for reported breaches. The causes repeat: exposed surfaces, stolen credentials, over-broad access. What the OAIC numbers and the Optus and Medibank cases show, and the infrastructure controls that address each one.
Your database provider can read your users' PII
Most managed databases can read every row you store, because the provider holds the keys. Why "encryption at rest" doesn't change that, and how client-side encryption where you hold the key does.
How to search encrypted data without decrypting it
If a field is encrypted, how do you still find a user by email? Blind indexes. How keyed hashes let a database match encrypted values it can't read, what they leak, and the honest limits.
"Encryption at rest" won't stop a subpoena
At-rest encryption protects against a stolen disk, not against your provider, an insider, or a legal demand, because the provider still holds the key. What each layer of database encryption defends against.
Build a SaaS fast: from a Postgres schema to a live REST API
A fast path with WattleDB: a real Postgres schema, an auto-generated REST API and JWT + Row-Level Security for multi-tenant isolation, plus a straight answer on what you still bring yourself today.
How to migrate from Supabase to WattleDB
An honest step-by-step: dump and restore the database, carry your RLS, re-point the REST API, copy Storage, and handle Auth, Realtime and Edge Functions, which don't map one-to-one. What's clean, what takes effort, what has no equivalent yet.
How to migrate a PostgreSQL database between providers
Assess, provision, dump, restore, verify, cut over, the full step-by-step playbook for moving Postgres with minimal downtime, with the exact pg_dump / pg_restore commands. Provider-agnostic, Supabase included.
Multi-tenant SaaS with PostgreSQL Row-Level Security
The scariest bug in a multi-tenant app shows one tenant another's data. A worked example of enforcing isolation in the database with RLS and JWT claims, so a forgotten WHERE clause can't become a breach.
An instant REST API for your Postgres database
Enable the REST API and PostgREST turns your schema into a full HTTP interface, filtering, ordering, pagination, embedded relations and writes, all respecting Row-Level Security. Skip the CRUD layer.
Connection pooling in Postgres: why your app needs it
Connections are expensive and there's a hard limit, ignore it and a spike takes you down with "too many clients." What a transaction-mode pooler does, and which of the two connection strings to use where.
Connecting Prisma and Drizzle to WattleDB
WattleDB is standard Postgres, so your ORM works, once the right URL does the right job. The clean setup: pooled DATABASE_URL for the app, direct DIRECT_URL for migrations, TLS throughout.
Point-in-time recovery: getting your data back
A nightly backup answers "what did it look like last night?" PITR narrows the gap after a 4pm bad migration. How continuous WAL archiving works, what the console lets you pick, your recovery window, and why you restore to a new database.
Stop testing on real customer data: masked clones
Cloning production into staging quietly parks real customer PII where it was never meant to live. Masked clones are paused for now. This guide covers how they are meant to work: common contact fields anonymised by column name, with the mask reviewed against your own schema.
Data sovereignty: why it matters & the risks of ignoring it
A plain-English, global guide to the concept behind everything else here: what data sovereignty is, why it's become a board-level priority worldwide, and what an organisation really risks by neglecting it.
Privacy Act 2024 vs overseas cloud laws: the compliance catch-22
One set of rules pulls your data one way, the Privacy Act pulls it the other, and Australian businesses on US clouds get caught in the middle. The clean structural way out: an Australian-owned stack.
PostgreSQL vs Firestore for Australian apps
Relational or document? Predictable or per-operation pricing? Australian-owned or US-owned? A practical comparison for Australian teams choosing a database in 2026.
What "managed PostgreSQL" actually includes
More than a database you didn't have to install. Automated backups, point-in-time recovery, Row-Level Security, pooling and audit logs, and why they separate a hobby project from production.
Best database hosting in Australia (2026)
AWS RDS, Supabase, Neon, DigitalOcean, Firebase and WattleDB, six real options ranked for Australian teams on the axis global lists skip: who owns the company behind your data.
Firebase alternatives for Australia in 2026
Supabase, Appwrite, PocketBase, Nhost, WattleDB, ranked on the axis most lists skip: who owns the company, and whether an Australian business stands behind your data.
Australian-owned data in Australia: the Privacy Act 2024, in plain terms
Residency is geography; ownership is who's behind the platform. Why a US provider's Sydney region isn't an Australian company, and what the 2024 reforms mean for your data.
WattleDB vs Supabase: the Australian-owned alternative
Same developer experience, genuine Australian ownership. A full feature-by-feature comparison, plus an honest take on when to choose each.
Supabase in Australia: a Sydney region vs an Australian company
Supabase has a Sydney region, so you can keep data onshore. But a Sydney region is not the same as an Australian company. What running Supabase in Australia really means, and your options when you want an Australian-owned stack.
Australian-owned data in the cloud
The cloud made infrastructure borderless; Australian ownership puts a name and a place back on it. How to keep the cloud's convenience while knowing exactly who owns and runs the platform your data sits on.
Australian data retention compliance software: a buyer's guide
Retention is two duties at once, keep some records long enough, delete the rest on time. The obligations that set the clocks, the capabilities that enforce them, and why the data layer's Australian ownership matters.
Industries: Australian-ownership rules by sector
Health, childcare, construction, telco, education, legal, accounting, real estate, aged care, the specific regulations that make Australian ownership a requirement, not a preference.
Building something Australian-owned?
Start building on a wholly Australian-owned Backend-as-a-Service.
Get started →