T.10 / Technology
Cloud
larch deploys and runs products on Google Cloud and Firebase. Hiki’s back end, web app and daily scraper run on Cloud Run, with Firebase for sign-in and push notifications, and the Bridddge desktop app keeps its accounts in Firebase.
Bring the idea. We’ll tell you how we’d build it and what it takes.
01 / Built with Google Cloud and Firebase
One product lives on Google Cloud end to end. The other is a desktop app that uses Firebase for its accounts.
Web platform / 2025
01
Cloud Run serves Hiki’s FastAPI back end and Next.js web app and runs the daily scraper. Cloud Build deploys on every push, and Firebase handles Google sign-in and push notifications.
Web platform / 2025
Next.js · FastAPI · MongoDB · Google Cloud
macOS app / 2025
02
The Bridddge desktop app signs users in with Firebase Auth and keeps each account’s subscription and usage in Firestore.
macOS app / 2025
Electron · React · SQLite · MCP
02 / Related service
Fast, resilient platforms that grow with your business, not against it.
What you get
Bridddge keeps each user’s subscription and usage in Firestore, one record per account.
Hiki’s web app, API, scraper and photo storage run in one Google Cloud project.
Cloud Build ships Hiki on every push to main, and Cloud Logging keeps the record in production.
03 / How we use Google Cloud and Firebase
Shipping is half the job. Hiki deploys on every push to main and runs with no servers to look after, and Bridddge’s accounts live in Firebase.
Hiki runs on Google Cloud in the EU region europe-west1. Cloud Run serves two services, the FastAPI back end and the Next.js web app, and runs the scraper as a Cloud Run job that Cloud Scheduler starts every morning to refresh the catalog from the bookstores. Each push to main triggers Cloud Build, which builds the containers, stores them in Artifact Registry and deploys the new version.
A global HTTPS load balancer with Cloud Armor sits in front of the site. Marketplace photos go straight from the browser into a private Cloud Storage bucket through signed upload links, resized first, so the back end never handles the files. Logs go to Cloud Logging.
Firebase Auth gives Hiki Google sign-in, on the web and in the Android app, and the back end verifies the sign-in token before it trusts a request. Firebase Cloud Messaging sends the push notifications, and the back end clears out tokens that no longer work.
Bridddge runs on the user’s Mac, but its accounts live in Firebase. The app signs users in with Firebase Auth and keeps each account’s subscription and usage in Firestore.
Cloud Run scales with traffic and back down again with no servers to manage, and Firebase brings sign-in and notifications without building them from scratch. This site, larch.ee, runs on Cloud Run too.
04 / Other technologies
Hiki’s FastAPI back end runs on Cloud Run, and its Android app signs in with Firebase. See what else we built with them.
T.04 / Back end
Hiki’s back end: FastAPI with async MongoDB, the aiohttp scrapers and the pipeline that enriches every title.
Built with it
T.09 / Mobile
Hiki for Android: a native Kotlin app with every screen in Jetpack Compose, on Google Play.
Built with it
11 technologies
Eleven technologies, each one running in a product we shipped.
Start / 30-minute call
No corporate theater. Just results.
Prefer email?
nicholas@larch.ee