Google Cloud and Firebase development company

We build apps on Google Cloud and Firebase: real-time back ends for mobile apps, sign-in, storage and notifications, Cloud Functions, App Engine and Cloud Run services, and Google APIs such as Maps and Solar. Our project records hold 40+ Google Cloud and Firebase projects, and you own the projects and the code we set up.

40+

Google Cloud and Firebase projects in our records

10+

Published case studies using Google Cloud

3

Clouds we build on: AWS, Azure, Google Cloud

20+

Years in business, since 2005

Counts come from our project records. A Google Cloud project is one whose recorded stack or work names Google Cloud or Firebase; the case-study count is the number of published case studies that use a Google Cloud or Firebase service. For the delivery side, see cloud DevOps.

What we build on Google Cloud

Examples from our own projects, described in general terms.

Firebase back ends

Real-time databases, chat and live location for mobile apps. See Silent Beacon and Afrimack.

Sign-in and notifications

Firebase Authentication, social sign-in and push notifications through Cloud Messaging. See Newsology and GoAquatix.

Maps and Google APIs

Maps, Places and Solar API data in web and mobile apps. See the MyAddressPin case study.

Cloud Functions, App Engine and Cloud Run

Back-end logic that runs on demand, APIs on App Engine and containers on Cloud Run. See Fitdigits on App Engine and RoofReveal on Cloud Run.

Data and storage

Firestore, Cloud SQL and Cloud Storage, with rules and backups set up properly. See the LearnDash storage offload to Cloud Storage.

Reviews and migrations

Security rules, access and costs reviewed, runtimes moved to supported versions, and integrations deployed on Google Cloud. See the Python 3 migration and the order sync service.

When Google Cloud is the right choice

Google Cloud and Firebase suit mobile-first products and apps built around Google services:

  • Mobile apps that need real-time data, sign-in and notifications quickly.
  • Products that use Maps, Places or other Google APIs heavily.
  • Small teams that want managed services instead of servers.

For a wider range of managed services, AWS may fit better; for Microsoft-centred systems, Azure with .NET.

A laptop connected to cloud storage

Technologies we use

What our Google Cloud projects are built with. Linked technologies open our page for them.

Frequently asked questions

What Google Cloud services do you work with?

Firebase (Realtime Database, Firestore, Authentication, Cloud Messaging, Cloud Functions), App Engine, Cloud Run, Cloud SQL, Cloud Storage and the Maps, Places and Solar APIs. Our records hold 40+ Google Cloud and Firebase projects.

App Engine or Cloud Run?

App Engine when an API already runs there or fits a managed runtime; Cloud Run when the service ships as a container and you want the same image everywhere. We have done both: an API migrated to Python 3 on App Engine and a reporting platform on Cloud Run.

Can you migrate our systems to Google Cloud?

Yes. We plan the move with you first, keep a rollback path, and have moved runtimes, integrations and media storage onto Google Cloud services.

Should we choose Google Cloud or AWS?

We build on both and have no stake in the answer. Google Cloud and Firebase fit mobile-first products and anything built around Google APIs; AWS offers a wider range of managed services; Azure fits Microsoft-centred organisations. The choice follows your existing systems, data and team, and we can compare them for your case. See our AWS and Azure pages.

How do I get a quote?

Use the form on this page or book a project call. Tell us what you need and we come back with questions and next steps.

How can we work together?

There are three ways, on the same terms:

  • Dedicated team, best for ongoing work: interview the developers, then they work on your project full or part time.
  • Fixed scope, best when requirements are clear: we agree the scope and the price up front, and deliver against it.
  • Time and material, best when the scope will change: you pay for the time used and can change priorities as the work goes on.

Whichever you choose, we sign an NDA before work starts, you own the code we write, and every change is reviewed in your repository.

Can I interview the developers before we start?

Yes. For a dedicated team you meet the developers in an online call and interview them before they join your project.

Building on Google Cloud or Firebase?

Tell us what you run today and what you need. We come back with questions, a suggested approach and an estimate.