Oracle Backend with Firebase APIs

Mandeep Gupta  ·  Oracle Database  ·  AppDev

Oracle just gave mobile and web developers a Firebase-shaped on-ramp straight into Oracle AI Database — and it’s a bigger deal than it sounds.

If you’ve built apps on Firebase, you know the appeal: collections and documents instead of DBA-managed schemas, a client SDK that handles auth and sync for you, and security rules you write once instead of an API layer you maintain forever. Oracle has now packaged that same developer experience on top of its own database, under the name Oracle Backend for Firebase (nicknamed “Fusabase”).

Runs on infrastructure you already have

This isn’t a hosted service bolted onto Oracle from the outside — anywhere you’re already running Oracle REST Data Services (ORDS), this runs too: OCI, AWS, Azure, GCP, on-prem, or Cloud@Customer. No separate control plane, no new data plane to secure, no additional vendor relationship to manage.

Your DBA’s controls don’t disappear

Because collections live as real tables inside Oracle AI Database, VPD policies, TDE, auditing, partitioning, and Data Guard all still apply underneath the app-developer-facing security rules. It’s two layers of governance on the same data — not a replacement for the controls your DBA team already trusts.

Vector search sits next to your business data

With native vector storage in Oracle AI Database, similarity search and your relational data can be joined in a single query, governed by a single set of security rules. That’s a meaningfully simpler path to RAG and semantic search features than standing up a dedicated vector store alongside everything else.

import { doc, setDoc } from "fusabase/oracledb";

// create or update a document in a collection
await setDoc(doc(db, "employees", "E1042"), {
  displayName: "Sample Employee",
  department: "Fusion HCM",
  status: "Active"
});

An answer for stolen client configs

Firebase-style client configs are public by design — anyone can extract them from a deployed app. App Trust adds an attestation layer (reCAPTCHA, hCaptcha, Turnstile) so a request has to prove it came from your actual app, not a script or a clone, before it ever touches the database.

SDKs that feel familiar on day one

Native SDKs ship for iOS, Android, JavaScript, and Flutter, deliberately shaped to feel familiar if you’ve written Firebase code before — the concepts (documents, queries, auth state listeners, storage references) map over directly, even though the backend underneath is Oracle.

It’s generally available now as part of ORDS 26.1.1, with hands-on LiveLabs workshops for iOS, Android, and web if you want to try building something on it directly.

Category: Configuration | Fusion HCM