The Nalu platform’s production database had grown beyond 2GB, and standard migration scripts kept timing out, breaking on schema mismatches, or hitting memory limits during transfer. A clean lift-and-shift was not an option because the application needed to maintain referential integrity across multiple linked entities during the cutover.
Hermosa is Nalu’s internal ML processing engine, and its client-server architecture needed to talk to the freshly migrated Cloud SQL instance without exposing the database to the public internet. The standard public endpoint approach would have created a serious security exposure, especially for a real estate platform handling proprietary pricing data.
Auth0 gave Nalu out-of-the-box APIs to manage user sessions and state, which kept the application code clean, added a recurring third-party cost, and an external dependency that the team wanted to remove. Firebase Authentication offered tighter integration with the rest of the Google Cloud stack, but did not provide the same automatic session-state management.
The Nalu Web App needed a UI for operators to start, stop, and monitor live ML processing jobs running on Hermosa. The default approach of polling the backend every few seconds would have hit API rate limits, increased server load, and given users laggy log feedback that made it hard to debug failing jobs.
Operators were spending significant time configuring each new project with the same baseline data: property templates, unit types, market segments, and pricing rule defaults. Manual setup was slowing down onboarding and creating data-entry errors that would later corrupt ML predictions.
The original Nalu Web App had hard-coded Firebase connector fields scattered across multiple components, which meant any schema change required edits in dozens of places and made the codebase fragile.
Years of Business
Experience
Happy
Customers
Countries with
Happy Customers
Agile enabled
employees