Frequently asked questions

WattleDB is Australia's first sovereign Backend-as-a-Service (BaaS) — one platform giving you managed PostgreSQL, auto-generated REST and GraphQL APIs, authentication, S3-compatible object storage and transactional email. It's built by RR Sols Pty Ltd, a 100% Australian-owned company, and runs entirely on Australian-owned infrastructure in Sydney and Melbourne, so your data is beyond the reach of the US CLOUD Act.

A Backend-as-a-Service provides the common backend components every application needs — database, authentication, APIs, file storage and email — as a managed, pre-integrated service, so developers build applications without provisioning and operating that infrastructure themselves. Firebase and Supabase are well-known examples; WattleDB is the Australian sovereign equivalent. See How to build a SaaS in Australia for the full stack.

WattleDB is built and operated by RR Sols Pty Ltd, an Australian-owned and operated company with no foreign parent entity. Support and administration are handled onshore under Australian law.

WattleDB is preparing for launch and currently accepting registrations via the waitlist. Join the waitlist to be notified when access opens and to help shape the platform.

Yes. Sovereignty is determined by corporate ownership, not server location. WattleDB is owned by RR Sols Pty Ltd, an Australian company with no foreign parent, and runs on Australian-owned infrastructure in Sydney and Melbourne with backups kept cross-state within Australia. Because there's no US or other foreign entity in the chain, there's no CLOUD Act exposure to disclose. Read the full explainer: Data sovereignty in Australia.

All data is stored in Australia. Primary infrastructure is in Sydney and backups are held cross-state in Melbourne, both within Australian-owned data-centre facilities — so a single-city incident cannot take out both your primary and your backups. No data leaves Australia.

Yes — those regulated sectors are exactly who WattleDB is built for. It keeps data onshore under Australian jurisdiction, is architected for IRAP assessment at the PROTECTED level, and removes the cross-border transfer risk that comes with US-owned providers. That helps meet Privacy Act obligations and sector-specific requirements. See Industries for the rules by sector.

No. An Australian region gives you data residency (geography), not sovereignty (jurisdiction). If the provider is US-incorporated, the US CLOUD Act can compel it to produce your data regardless of region. Genuine sovereignty requires an Australian-owned provider with no foreign entity able to be compelled.

PostgreSQL, the world's most advanced open-source relational database. Each tenant gets a managed Postgres database with kernel-enforced CPU, memory and storage limits, connection pooling, Row-Level Security for multi-tenant isolation, automated backups and point-in-time recovery.

WattleDB uses simple, flat AUD pricing with unmetered bandwidth on paid tiers, so there are no surprise egress bills. There's a free tier to start building, and paid tiers scale up in resources as your application grows. All prices are quoted ex-GST. Current tiers are shown when you create a database in the console.

A masked clone is a one-click copy of your production database with all personally identifiable information — names, emails, phone numbers, addresses — automatically replaced by realistic fake data. Your team tests against production-shaped data without exposing real customer PII in staging, a practical way to meet privacy obligations. It's a WattleDB feature that Supabase and Firebase don't offer.

No. Unlike usage-based platforms that meter egress bandwidth (which can produce bill shock), WattleDB uses flat AUD tier pricing with unmetered bandwidth. You pick a tier and know the price.

Similar developer experience — managed database, auth, APIs and storage — but 100% Australian-owned with no foreign parent. Supabase Inc. is US-incorporated and Firebase is a Google (US) product, so both carry US CLOUD Act exposure even with an Australian region. WattleDB has no US entity to compel, and uses flat AUD pricing instead of usage-based egress. Compare in detail: WattleDB vs Supabase and Firebase alternatives for Australia.

Yes. WattleDB is built on the same open-source core as Supabase — PostgreSQL, PostgREST and GoTrue — and ships Supabase-compatible client libraries, so most Supabase projects migrate by changing a few environment variables rather than rewriting application code.

Yes. Migrating from Firebase involves moving from Firestore's NoSQL model to PostgreSQL. That's more involved than a Supabase move, but it also frees you from NoSQL lock-in and unpredictable scaling costs, and gives you the full power of SQL, relations and Row-Level Security.