A one-week audit of Firestore, rules, functions and billing, top fix shipped: one payment of $997. Then hire me by the week.
varstatt.com/discovery
tenderpilot.ai
contentpal.app
fidder.app
A data model built for 100 users meets 10,000. Five problems come up.
Money first. Your team keeps shipping while I read.
Reads, writes and deletes by collection, invocations, storage and egress
Indexes, read paths, listeners, rule coverage, sign-in flows
What I found, what each finding costs, what to fix first
Ranked findings, each with its fix. These four I have already paid for.
Teams with a Firebase web app and no one who owns it.
Right For
Better Elsewhere
A simple, predictable and transparent process that eliminates development headaches.
Pay once; a task board opens, and you add me to the Firebase project, billing and repo.
Work starts the next working day. Everything stays in your accounts.
After the report you rank the fixes; if you keep me on, I take one at a time.
Every change goes up for your review. I revise until you're satisfied.
You approve finished work. I move to the next fix, then to features.
You report issues anytime; I handle them first.





The audit week. Then stop, or hire me by the week.
— 1-week delivery
A Firebase audit with its top fix, then by the week if you want.
Usually reads, not traffic: whole-collection listeners, rules that look up other documents, polling. On my own app, fixing those took the Firestore bill from about $12 to under $1 a month.
Partly: budget alerts only warn, and Firestore has no spend cap. The report lists the limits your app needs.
A security rules review asks one question: can a signed-in stranger read or write what they shouldn't? Rules usually fail three ways: left open from setup, a sign-in-only check, or a collection added later.
Not on its own: Firebase web keys are public by design. An OpenAI or Gemini key in the browser is, so those calls move behind Cloud Functions.
Sometimes: Postgres fits heavily relational data better. More often the data model changes and the platform stays.
Yes, by the week: fixes, then features on Firestore, Auth, Cloud Functions and Hosting, on my default stack.
I revise the report until you're satisfied. Kept on by the week, cancel anytime with no penalty.
Fill in the project form with what moved: the bill, a Google rules email or a slow screen. I reply the next working day.
Jurij understand the core problem, insists on building the right experiences for the customers.

Kunal Modi
Founder @ SOAPNoteAI
Working with Jurij is an absolute joy, consistently exceeds expectations.

Janis Ozolins
Content Creator
Consistently delivered quality code in great time, very hard working & precise.

Bartosz Poźniak
CEO @ MyCointainer
The kind of engineer that every company on the planet would be lucky to have.

Hosam Mazawi
COO @ LemonUnit
Firebase Audit fits product teams best: CTOs and tech leads who need a senior on one part of the product.
“The upgrade keeps losing to features”: small pull requests, no big-bang rewrite.
“Backend work waits on a hire”: endpoints, integrations, an API being retired.
“Nobody here has shipped an LLM feature”: a prototype on your data first.
“Our workflows have no owner”: new flows, code where nodes stop, monitoring.
“An old app still has users and no owner”: kept current and safe.
Firebase Audit
“The bill keeps rising, or nobody trusts the rules”: the bill tied to its code, every rule reviewed.
“Releases are slow and scary”: planning to monitoring, fixes ranked.
“Every feature takes longer than the last”: why, what to fix first, whether a rewrite pays.
Not on a product team? See what Varstatt offers you.
Sole proprietorship headquartered in Rzeszów, Poland. VAT ID: PL8133854722.