Skip to main content

Firebase app hardening before and after production launch

Firebase makes it easy to start with open rules and a client talking directly to the database. Before real users arrive, those defaults need to become explicit rules, verified clients and a backend that cannot be abused or run up an unexpected bill.

ISO 9001 & ISO/IEC 27001Certified quality and information securitySince 2014, made in GermanyDiese Seite auf Deutsch

From test mode to production-grade Firebase

Many Firebase projects begin in test mode, where Firestore or Storage rules allow broad access for a limited time. When that period ends, apps break, and the quick fix is often a rule that allows everything indefinitely. Combined with a client that writes directly to Firestore, this means any user can read or overwrite data outside their own scope.

Hardening a Firebase app means checking rules, client verification, server code and project settings together. Our AI Code Engineers at neooutput do this for apps built by hand, with FlutterFlow or with AI tools such as Claude Code and Codex. OnlineAppCreator can continue with feature development and operations once the foundation is secure.

Firebase pitfalls to avoid

  • Firebase web API keys are not secret, but they should still be restricted in the Google Cloud console to the APIs and app identifiers you actually use.
  • A service account JSON file for the Admin SDK must never be bundled into an app or frontend. If it was ever committed, revoke that key and issue a new one.
  • Rules like allowing any signed-in user to write a document let users change fields such as role or credit balance. Validate individual fields and keep privileged fields server-side.
  • Firebase Dynamic Links has been discontinued, so older apps that rely on it for invitations or password reset links need a migration to Universal Links and Android App Links.
  • Check Auth settings such as authorised domains, email enumeration protection and which sign-in providers are actually enabled before launch.

What hardening covers

Rules written and unit tested

We rewrite Firestore, Realtime Database and Storage rules around your data model and test them with the Firebase Emulator Suite. Tests run in CI so regressions are caught before deployment.

Only your apps can call the backend

App Check with Play Integrity, App Attest and reCAPTCHA Enterprise makes it harder for scripts to use your Firebase resources. We roll it out in monitoring mode first to avoid locking out real users.

Server logic in the right place

Prices, roles, counters and anything users must not control are moved into Cloud Functions with proper auth checks. The client then requests actions instead of writing trusted fields.

Costs under control

Budget alerts, query reviews and listener cleanup prevent a single faulty loop or scraper from generating a large bill. We also check indexes for queries that will grow.

How we harden your Firebase app

  1. Project review

    We inspect rules, Auth settings, Functions, API key restrictions and IAM roles in the linked Google Cloud project.

  2. Threat walkthrough

    For each collection we ask who may read and write which fields, and test it with real and malicious requests.

  3. Implement and test

    New rules, App Check and server-side logic are deployed to a staging project, tested against app builds and then promoted.

  4. Monitor

    We set up alerts for rule denials, App Check failures and spend, so you notice problems before users do.

Matching products

neooutput

Agentic coding workshops and AI services. Hands-on agentic coding workshops for teams on Claude Code, OpenAI Codex and Cursor, remote or on-site, in English or German. Plus AI Code Engineers on demand who deploy, secure and scale AI-built apps.

Explore neooutput workshops

OnlineAppCreator Custom Development

Idea to operating product, built by AI Code Engineers. We take ideas to operating digital products: discovery, AI-native engineering by our AI Code Engineers, launch, SLAs and scale. B2B and public sector, from an ISO 9001 and ISO 27001 certified team in Germany.

See how we build products

Frequently asked questions

Is App Check enough to protect our data?

No. App Check makes abuse harder by verifying the calling app, but a legitimate app can still be misused by its own user. Security Rules and server-side checks remain the main protection.

Can you harden a FlutterFlow project?

Yes. FlutterFlow uses a standard Firebase project, so rules, Functions and settings are reviewed the same way. We coordinate rule changes with the queries FlutterFlow generates so screens keep working.

Will users notice the hardening?

Ideally not. We test new rules against current app versions, and App Check enforcement starts only when monitoring shows that legitimate traffic passes.

Do you support migrating away from Firebase?

If there is a clear reason, such as data residency requirements or cost, we can plan a migration to another backend. In many cases hardening the existing project is the better first step.

Let's talk about your project.

15 minutes with an AI Code Engineer, free and without obligation. Or call our team around the clock.