Scalable services
Services split to scale on their own, as on our AWS platform.
Cloud
Google Cloud development services with AWS and Azure proof behind them
We have no published Google Cloud build. We have shipped three builds on AWS and three on Azure, and we say plainly what carries across and what does not.
0Published builds on Google Cloud
22 Aug 2024Cloud Functions became Cloud Run functions
3Published builds on AWS
3Published builds on Azure
What we build
What we would take on with Google Cloud
Cloud Functions upgrades
1st gen functions moved to Cloud Run functions.
Delivery pipelines
Daily CI/CD deployments on a Kanban workflow.
Teams in your account
Engineers working inside accounts you own.
Architecture
Where Google Cloud would sit
Google Cloud in the slot our AWS build fills
Users
Angular web appFront end
Services
.NET microservicesScalable architecture
Cloud
Google CloudWhere it would sit
AWS KinesisCrypto platform
Delivery
Daily CI/CDKanban workflow
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Serverless
Cloud Functions is now Cloud Run functions
The August 2024 rename
Before 22 Aug 2024
Cloud Functions
- A separate event-driven product
- 1st gen needs an upgrade for full Cloud Run features
Now
Cloud Run functions
- Built on the unified Cloud Run platform
- APIs, gcloud functions commands and Terraform modules keep working
Source: Google Cloud blog, Cloud Functions is now Cloud Run functions, 22 August 2024.
Builds
The closest builds we can show you
Fintech, Hong Kong
Cryptocurrency marketing platform
Microservices and AWS Kinesis built for 30,000+ concurrent users, first phase live in one month.
30,000+Concurrent users the platform had to support
Construction safety testing, United Kingdom
Hydrajaws Limited
Azure, Azure DevOps and Azure AD B2C under a Xamarin, .NET and Angular app.
500%Surge in potential clients
Fit check
When Google Cloud is the right call
Pick Google Cloud when
- Your team and data already sit on Google Cloud
- You run functions that need the Cloud Run features
- You want a second cloud beside AWS or Azure
Look elsewhere when
- You need a published Google Cloud build to inspect, which we do not have
- Your team runs Microsoft 365 and .NET, where we shipped Azure
- Traffic arrives in spikes on AWS Kinesis, where we have proof
Explore
Same job, other tools
Pairs with
Where we used it
Stack
What Google Cloud usually sits beside
AWS
Azure
Kubernetes
Terraform
Docker.NETFAQs
What buyers ask first
What happened to Google Cloud Functions?
On 22 August 2024 Google renamed it Cloud Run functions, built on the unified Cloud Run platform. The existing APIs, gcloud functions commands and Terraform modules keep working.
Do you have a published Google Cloud build?
No. We say so on the first call and show the nearest work, which is three builds on AWS and three on Azure.
Should we pick Google Cloud, AWS or Azure?
The choice follows where your team, data and licences already are. We have published builds on AWS and Azure, and none on Google Cloud.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us what runs on Google Cloud today
Thirty minutes on your projects, your services and your team. No sales pitch.