Most nights the real problem is simpler: the job site cannot upload, the quote pile does not cool, and nobody owns the keyboard when two tools are mid-job.
We already published the three field notes. This is the companion that names the stack.
Layer 0 starts at the curb — can the site still talk?
The pipe
On a water job, cell bars lie. Fiber is dead. The moisture map still has to leave the truck.
Starlink on a water job is not a partnership post. It is layer 0: a clear-sky dish, a 65–100 W brick, and a boring SSID so photos, Xactimate, and after-hours voice still move when the street does not.
No pipe → no honest traffic. Voice agents and CRM cards do not invent bandwidth.
Clipboard math beats a prettier quote card.
The pile
Once the pipe works, the shop still has open estimates that do not book, supplements that sit, and missed rings that become someone else’s water job.
The leftover pile borrows the math that cools a trapped ion. Count n (open quotes), A− (book or honest kill), A+ (new noise). Plot the leftover on Mondays. If it does not fall, follow-up is theater or miss rate is the heat.
AI that only writes a prettier card is a thermometer. AI that texts back in a minute and closes the row is a kick.
Two seats. One measurement owner.
The two seats
Then you put more than one agent on the same laptop and discover the collision problem.
Cursor checked in on Grok Desktop mid-job is the Cosync rule in the open: seats with jobs, not two models arguing in one thread. One seat keeps the PowerShell. The other reads the board, closes orphan twins, and does not steal the keyboard.
Human Gate still owns OAuth, live Publish, and paid spend. Seats replace waiting and context loss — not the owner.
Weather hits. The floor still has to run.
One floor
Read as three posts, they look like tech, physics, and tooling.
Run as a week, they are one floor:
Pipe — can the site and the after-hours line still talk?
Pile — are open quotes shrinking on purpose?
Seats — who owns the keyboard, and who only Cosyncs?
Skip the pipe and your “AI dispatcher” is a voicemail with better grammar. Skip the pile math and your lead gen is blue-detune (more noise, same booked jobs). Skip the seat rule and two tools fight over the same Chrome window while the work order twins drift.
Steal this without buying our tools
You do not need our stack names.
Write one Owner column and one Done-when line on every live card.
Put a truck kit on the hook for dead-fiber jobs (or admit you will not upload tonight).
Run the four-week leftover sheet before you buy another map-pack click.
Practice the check-in: are they stuck, or are they fine — and do I have a capability they lack? If they are fine, leave the keyboard alone.
That is restoration + AI ops without a slide deck.
What this is not
Not a Starlink / SpaceX / Tesla / xAI partnership.
Not “fully autonomous.” Publish and pay stay human.
Not Tacoma / Everett / Mason local news. Field notes stay method-first.
Not a new SKU. The front door on Tygart Media is still the kit you can copy and hang yourself.
Logic Apps vs Cloud Workflows: No-Code Automation Across Two Clouds
Every content operation runs on small invisible chains of “when this happens, do that.” Publish an article → notify a channel → write a row to the ledger. None of it is hard, but you don’t want to babysit a script for it — you want a managed orchestrator that fires on an event, calls a few services, and logs the result, for free. Azure and Google each have one, and they take opposite philosophies to the same job.
We wire the same publish → notify → log automation on both Azure Logic Apps and Google Cloud Workflows, on the free tiers, and compare. Short answer: Logic Apps wins when the work is gluing SaaS services together — its connector library and visual designer are unmatched, with a free grant of 4,000 built-in actions/month. Cloud Workflows wins when the work is lightweight, code-first orchestration inside GCP — its 5,000 internal + 2,000 external steps/month free tier pairs cleanly with Eventarc and Pub/Sub. One is a no-code SaaS glue gun; the other is a YAML orchestration engine.
This is the breakdown from the running lab on tygart.media — connector ecosystems, visual designer vs YAML, triggers, and free ceilings.
The free-tier ceilings
Free-tier ceilings for Logic Apps vs Cloud Workflows.
How we do it
Azure
Google Cloud
Verdict
Free grant/month
4,000 built-in actions
5,000 internal + 2,000 external steps
Comparable, units differ
Billing model
Per-action (Consumption)
Per-step (internal vs external)
Different mental models
What counts
Each connector/built-in action
Each workflow step executed
Tie at our volume
Fit for a glue chain
Generous
Generous
Tie
Our actual bill
$0
$0
Tie where it counts
Both free grants comfortably cover a real automation cadence. A publish → notify → log chain is three or four actions/steps per run; at a few publishes a day, neither 4,000 actions nor 7,000 steps comes close to binding. The units differ — Azure counts actions, Workflows splits internal vs external steps (external = calls out to other services, which are scarcer) — but for our workload both run free.
Connectors vs code-first
Connectors vs code-first automation.
This is the real fork in the road, and it decides the choice.
How we do it
Azure
Google Cloud
Verdict
Connector library
Hundreds (SaaS + Microsoft + 3rd-party)
HTTP + GCP services, no big SaaS catalog
Logic Apps, decisively
Authoring model
Visual designer (drag-and-drop)
YAML (code-first)
Logic Apps for no-code
SaaS glue (Slack, email, etc.)
Native connectors, prebuilt auth
Roll your own via HTTP
Logic Apps
GCP-native orchestration
Possible via HTTP
First-class
Cloud Workflows
Versioning / review in git
Exportable, but designer-first
YAML lives in git naturally
Cloud Workflows
Logic Apps’ superpower is its connector library — hundreds of prebuilt, pre-authenticated connectors for Slack, Office, Salesforce, Twitter/X, databases, and most SaaS you’d name. Wiring “post to Slack when an article publishes” is point-and-click, with the OAuth handled for you. Cloud Workflows takes the opposite stance: it’s code-first YAML with no big SaaS catalog — you orchestrate GCP services and arbitrary HTTP endpoints, building any integration you need by hand. That’s less convenient for SaaS glue but cleaner for engineers who want their orchestration in git, reviewed like code.
Triggers and event sources
How we do it
Azure
Google Cloud
Verdict
Native triggers
Many (HTTP, schedule, connector events)
HTTP + Eventarc/Pub/Sub
Logic Apps on built-in variety
Event-driven on cloud events
Via Event Grid
Via Eventarc (first-class)
Cloud Workflows for GCP events
Schedule / cron
Built-in recurrence
Cloud Scheduler
Tie
SaaS event triggers
Connector-based, prebuilt
Roll your own
Logic Apps
Pub/Sub-style fan-out
Event Grid
Pub/Sub (native pairing)
Cloud Workflows in GCP
Logic Apps can be triggered by connector events directly — “when a new email arrives,” “when a row is added” — which keeps SaaS-driven automations entirely no-code. Cloud Workflows leans on Eventarc and Pub/Sub for event sources, which is the idiomatic, powerful path if your events originate in GCP. Each is strongest for events native to its own cloud.
What surprised us
What surprised us across two clouds.
Logic Apps’ connector library is the whole ballgame for SaaS glue. Pre-authenticated connectors turned a “write a small integration” task into a five-minute drag-and-drop. Nothing on the GCP side matches that catalog.
Cloud Workflows’ YAML-in-git is quietly the better engineering experience. When the orchestration lives in the repo and gets code-reviewed, it stops being a clickable black box. We liked that more than expected.
The free grants are both ample. We worried about per-action metering and never came near either ceiling at a realistic publishing cadence.
External steps are the scarce currency on GCP. Workflows’ 2,000 external steps (calls out to other services) is the limit to watch, not the 5,000 internal steps.
The takeaway
Pick Azure Logic Apps if your automation is mostly gluing SaaS services together — Slack, email, CRMs, Microsoft 365 — and you want a visual, no-code designer with hundreds of pre-authenticated connectors. It’s the fastest path from “I wish X notified Y” to a running flow.
Pick Google Cloud Workflows if your automation is lightweight orchestration inside GCP — coordinating Cloud Run, Functions, Pub/Sub, and HTTP endpoints — and you want it defined as code-first YAML that lives in git and pairs with Eventarc. It’s the cleaner engineering primitive when the events and services are already on Google’s side.
For our publish → notify → log chain, the deciding factor is where the notify lands: a Slack or email notification leans Logic Apps for the free connector; a fan-out into Cloud Run or Pub/Sub leans Workflows. Running the same chain on both made the connector-vs-code-first trade concrete.
This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud on the free tiers, wiring the same automation on each to see which orchestrator fits which job. The lab lives on tygart.media; the findings publish here.
What’s the free tier for Azure Logic Apps and Google Cloud Workflows?
Azure Logic Apps (Consumption) includes a free grant of 4,000 built-in actions per month. Google Cloud Workflows includes 5,000 internal steps and 2,000 external steps per month free. Both comfortably cover a realistic automation cadence, so a small glue chain runs at $0 on either.
Which is better for no-code automation, Logic Apps or Cloud Workflows?
Logic Apps is the no-code choice — it has a visual drag-and-drop designer and hundreds of pre-authenticated connectors for SaaS services. Cloud Workflows is code-first YAML with no big SaaS catalog, so it suits engineers orchestrating GCP services rather than non-developers gluing apps together.
Does Cloud Workflows have a connector library like Logic Apps?
No. Cloud Workflows orchestrates GCP services and arbitrary HTTP endpoints, but it has no large prebuilt SaaS connector catalog the way Logic Apps does. To integrate a third-party SaaS in Workflows, you call its HTTP API and handle authentication yourself, whereas Logic Apps provides a ready-made connector.
How do I trigger automation when an article is published?
On Azure, a Logic App can be triggered by an HTTP request, a schedule, or a connector event, then call further connectors with no code. On Google Cloud, a Workflow is typically triggered via Eventarc or Pub/Sub for cloud-native events, or by HTTP. Each is strongest for events that originate inside its own cloud.
Which is better for gluing SaaS and cloud events together?
Logic Apps wins for SaaS glue thanks to its connector library and visual designer, making things like “notify Slack when X happens” nearly code-free. Cloud Workflows wins for lightweight, code-first orchestration of GCP services that lives in git and pairs with Eventarc and Pub/Sub. Pick by where your events and services already live.
Azure Static Web Apps vs Firebase Hosting: A Dashboard on Each
A static front-end — an internal dashboard, a docs site, a landing page — is the most thankless thing to host badly and the most satisfying thing to host well. You want a global CDN, free SSL, a custom domain, and CI/CD that redeploys when you push, all without standing up a server or paying a cent. Both Azure and Google have a purpose-built free product for exactly this, and they’re both genuinely excellent.
We host the same internal dashboard on both Azure Static Web Apps and Firebase Hosting, on the free tiers, and compare. Short answer: this is a toss-up — both are excellent, pick by ecosystem. Azure Static Web Apps free tier gives you 100 GB of bandwidth, 2 custom domains, 0.5 GB per app, free managed SSL, and built-in CI/CD straight from GitHub. Firebase Hosting’s free Spark plan gives you 10 GB of storage, 360 MB/day of transfer, free SSL, and custom domains. The right answer is whichever cloud your other services already live in.
This is the breakdown from the running lab on tygart.media — bandwidth and limits, CI/CD, auth and functions integration, custom domains, and the CDN.
The free-tier ceilings
Free-tier ceilings for Static Web Apps vs Firebase.
How we do it
Azure
Google Cloud
Verdict
Free bandwidth
100 GB total
360 MB/day (~10 GB/mo) transfer
Azure on raw monthly headroom
Free storage per app
0.5 GB
10 GB
Firebase on storage
Custom domains (free)
2
Multiple supported
Firebase, slightly
Free managed SSL
Yes
Yes
Tie
Built-in CI/CD
Yes (GitHub Actions wired automatically)
Yes (Firebase CLI / GitHub Action)
Azure, slightly more turnkey
The numbers favor different things. Azure leads on monthly bandwidth — 100 GB is a lot of dashboard traffic — while Firebase leads on storage, with 10 GB versus Azure’s 0.5 GB per app. For an internal dashboard, neither limit is close to binding: the assets are small and the audience is a handful of people. Firebase’s 360 MB/day transfer cap is the one to watch only if a dashboard goes unexpectedly viral, which an internal tool won’t.
CI/CD, auth, and functions
CI/CD, auth, and functions on each host.
This is where “static hosting” stops being just a CDN and starts being a platform.
How we do it
Azure
Google Cloud
Verdict
Deploy on git push
Auto-wired GitHub Actions
Firebase CLI or GitHub Action
Azure on zero-config setup
Built-in auth
Yes (Entra, GitHub, social — built in)
Via Firebase Authentication
Azure for bundled, Firebase for depth
Serverless functions
Built-in Azure Functions integration
Cloud Functions / pairs naturally
Tie — both have a backend path
Staging environments
Free preview environments per PR
Preview channels
Tie
Setup friction
Connect repo, done
CLI init, done
Azure, slightly
Azure Static Web Apps’ standout is how much it bundles by default: connect a GitHub repo and it writes the Actions workflow for you, provisions preview environments per pull request, and offers built-in authentication (Entra, GitHub, and social providers) without you wiring an auth service. Firebase matches the capability but composes it from named products — Firebase Authentication and Cloud Functions — which is more à la carte and, if you’re already deep in Firebase, more powerful and familiar.
Custom domains and the CDN
How we do it
Azure
Google Cloud
Verdict
Custom domain setup
2 free, managed cert
Add domain, managed cert
Tie
Global CDN
Yes, included
Yes, included (Fastly-backed)
Tie
Cache control
Configurable
Configurable
Tie
TTFB at our scale
Fast
Fast
Tie
Both put your dashboard behind a real global CDN with automatic SSL on a custom domain, and at our scale the time-to-first-byte was indistinguishable. This part is genuinely a wash — both clouds have solved static delivery.
What surprised us
What surprised us hosting the same dashboard.
Azure’s per-PR preview environments are a delight. Open a pull request and you get a live URL of that exact change, free, with no setup. For reviewing dashboard tweaks it’s better than we expected.
Firebase’s storage allowance is the bigger one. 10 GB versus 0.5 GB sounds dramatic, but for a static front-end neither limit matters — the assets are tiny.
Azure’s built-in auth saved real work. Adding GitHub login to an internal dashboard was nearly free of code on Azure; on Firebase it meant wiring Firebase Authentication, which is more capable but more steps.
The hosting itself is a non-event on both. Push, it’s live, it’s fast, it’s free. That’s the whole experience — exactly as it should be.
The takeaway
Pick Azure Static Web Apps if you want the most bundled experience — auto-wired GitHub CI/CD, free per-PR preview environments, and built-in authentication — and your stack already leans Microsoft. The 100 GB bandwidth is generous for any internal tool.
Pick Firebase Hosting if you’re already in the Firebase/Google ecosystem and want its deeper, composable Authentication and Cloud Functions, or you value the larger 10 GB storage allowance. It pairs naturally with the rest of Firebase.
Honestly, for a static dashboard you can’t go wrong. We run the dashboard on whichever cloud hosts the data and functions behind it — co-location beats cleverness. Both deliver the dashboard fast, on a custom domain, with free SSL, at $0.
This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud on the free tiers, hosting the same dashboard on each to feel where the platforms differ. The lab lives on tygart.media; the findings publish here.
What do the free tiers of Azure Static Web Apps and Firebase Hosting include?
Azure Static Web Apps’ free tier includes 100 GB of bandwidth, 2 custom domains, 0.5 GB of storage per app, free managed SSL, and built-in GitHub CI/CD. Firebase Hosting’s free Spark plan includes 10 GB of storage, 360 MB/day of transfer, free SSL, and custom domains. Azure leads on bandwidth; Firebase leads on storage.
Which is better for hosting a static site or dashboard for free?
Both are excellent and the choice comes down to ecosystem. Azure Static Web Apps bundles more by default — auto-wired CI/CD, per-PR preview environments, and built-in authentication. Firebase Hosting pairs naturally with Firebase Authentication and Cloud Functions and offers more free storage. Pick the one matching the rest of your stack.
Does Azure Static Web Apps include built-in authentication?
Yes. Azure Static Web Apps offers built-in authentication with Entra ID, GitHub, and social providers without wiring a separate auth service, which makes adding login to an internal dashboard nearly code-free. Firebase achieves the same through Firebase Authentication, which is more capable but takes more setup.
Do both Azure Static Web Apps and Firebase Hosting give free SSL and custom domains?
Yes. Both provide free managed SSL certificates and support custom domains on the free tier — Azure includes 2 custom domains, and Firebase supports adding custom domains with managed certificates. Both also put your site behind a global CDN at no cost.
Will I hit the free hosting limits with an internal dashboard?
Almost certainly not. An internal dashboard serves small assets to a few people, so neither Azure’s 100 GB bandwidth nor Firebase’s 360 MB/day transfer comes close to binding. Firebase’s daily transfer cap would only matter if a public site went unexpectedly viral.
Cosmos DB vs Firestore: A Free-Tier Operations Ledger on Both Clouds
Every real content operation grows a small database it didn’t plan for: a ledger of what got published when, a metadata store tracking which article has an audio version, which has been translated, which is queued. It’s not big data — it’s a few thousand small records that need to be written cheaply, queried quickly, and never cost anything. The question is which cloud’s free NoSQL tier carries that load forever.
We run the same small ops ledger and content-metadata store on both Azure Cosmos DB and Google Firestore, on the free tiers, and watch the quotas. Short answer: Cosmos DB’s always-free tier is unusually generous — 1,000 RU/s of provisioned throughput plus 25 GB of storage, free for the life of one account per subscription. Firestore’s free tier is simpler but tighter — 1 GiB of storage with 50,000 reads, 20,000 writes, and 20,000 deletes per day. For a metadata store that fits either, Cosmos gives you more room; Firestore gives you less to think about.
This is the breakdown from the running lab on tygart.media — free-tier generosity, data model, query power, latency, and which one we’d trust with the ledger.
The free-tier ceilings
Free-tier ceilings for Cosmos DB vs Firestore.
This is where the two diverge most, and the units don’t line up cleanly — which is itself the point.
How we do it
Azure
Google Cloud
Verdict
Free throughput
1,000 RU/s provisioned
50K reads / 20K writes / 20K deletes per day
Cosmos for steady throughput
Free storage
25 GB
1 GiB
Cosmos — 25× the storage
Billing unit
Request Units (RU/s)
Per-operation daily quota
Different mental models
How many free tiers
One per subscription
Per project (Spark plan)
Tie, structurally
Fit for a metadata store
Generous
Comfortable for small stores
Cosmos on headroom
The mismatch in units is the real story. Cosmos meters everything in Request Units — a blended currency for reads, writes, and queries — and gives you a flat 1,000 RU/s continuously plus 25 GB. Firestore meters discrete daily operations — 50K reads, 20K writes, 20K deletes — and 1 GiB. For our ledger, Cosmos’s 25 GB is absurd headroom we’ll never approach, and 1,000 RU/s comfortably absorbs bursty publish events. Firestore’s daily caps are fine for a small store but you feel them: a chatty dashboard that re-reads the ledger on every page load can nibble through 50K reads faster than you’d expect.
Cosmos is multi-model: the same data can be addressed through a SQL-like NoSQL API, MongoDB’s wire protocol, Cassandra, Gremlin (graph), or Table. If you ever want to query the ledger like a graph, or you’re migrating off MongoDB, that optionality is real and free. Firestore is single-purpose by design — document collections with excellent real-time listeners, which is the thing to reach for when a dashboard should update live as the ledger changes. For a metadata store feeding a UI, those listeners are genuinely pleasant.
Latency and operational feel
Latency and operational feel.
How we do it
Azure
Google Cloud
Verdict
Read latency
Single-digit ms (tuned)
Low, very consistent
Tie at our scale
Provisioning model
Provisioned RU/s (or serverless)
Fully managed, no capacity knobs
Firestore on simplicity
Capacity tuning
You can over/under-provision
Nothing to tune
Firestore on hands-off
Setup friction
A few more knobs
Near-zero
Firestore
At our volume, both are fast enough that latency never registered as a difference. The operational feel diverges: Cosmos hands you knobs (RU/s, consistency levels, indexing policy) — power if you want it, a thing to learn if you don’t. Firestore has almost no knobs, which is the right call when the database is a side character in your stack and you never want to think about capacity.
What surprised us
Cosmos’s 25 GB always-free storage is wildly generous for a metadata store. We will not approach it. It reframed Cosmos from “enterprise database” to “perfectly viable free tier.”
Firestore’s daily read quota is the thing to watch. It’s not the storage that bites — it’s a chatty UI re-reading the ledger. Cache reads or you’ll surprise yourself.
The RU/s model has a learning curve. Cosmos’s Request Unit currency is unintuitive at first; once it clicks, capacity planning is straightforward, but day one is more conceptual than Firestore.
Firestore’s real-time listeners are a quiet joy. For a live dashboard, “the data just updates” without polling is worth a lot.
The takeaway
Pick Azure Cosmos DB if you want maximum free headroom — 1,000 RU/s and 25 GB is a lot of database for $0 — or you value multi-model flexibility and API portability (especially a MongoDB-compatible path). It’s our pick when the ledger might grow or change shape.
Pick Firestore if you want the simplest possible managed document store with first-class real-time listeners and nothing to tune, and your store stays comfortably inside 1 GiB and the daily operation caps. It’s the right call when the database should disappear into the background.
For our ops ledger, Cosmos’s always-free generosity is hard to argue with — but for the live dashboard that reads the ledger, Firestore’s real-time listeners are the nicer developer experience. Running the same store on both made the trade explicit instead of theoretical.
This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud on the free tiers, keeping the same ops ledger on each to see where the quotas really pinch. The lab lives on tygart.media; the findings publish here.
What does the free tier of Cosmos DB and Firestore actually include?
Azure Cosmos DB’s always-free tier gives 1,000 RU/s of provisioned throughput plus 25 GB of storage, free for one account per subscription. Firestore’s free Spark tier gives 1 GiB of storage with 50,000 reads, 20,000 writes, and 20,000 deletes per day. Cosmos offers far more storage; Firestore meters by daily operations.
Is Cosmos DB or Firestore more generous on the free tier?
For storage and steady throughput, Cosmos DB is more generous — 25 GB and a continuous 1,000 RU/s versus Firestore’s 1 GiB and daily operation caps. Firestore is perfectly adequate for a small metadata store, but a chatty application can hit its daily read quota. Cosmos gives more headroom for growth.
What’s the difference between Cosmos DB and Firestore’s data model?
Cosmos DB is multi-model: the same data can be queried as documents, key-value pairs, graphs, or columns, and it speaks NoSQL, MongoDB, Cassandra, Gremlin, and Table APIs. Firestore is a focused document database — collections and documents — with excellent real-time listeners. Cosmos offers flexibility; Firestore offers simplicity.
Which is better for a serverless content metadata store?
Both work well. Choose Cosmos DB if you want generous free storage, multi-model flexibility, or a MongoDB-compatible path. Choose Firestore if you want a zero-tuning managed store with real-time listeners that update a dashboard live, and your data fits inside 1 GiB and the daily operation limits.
Will I hit Firestore’s free quota with a small app?
Storage usually isn’t the problem — 1 GiB holds a lot of small records. The daily read quota of 50,000 is what catches people: a dashboard that re-reads the same data on every page load can consume it quickly. Caching reads keeps a small app comfortably inside the free tier.
Azure Neural TTS vs Google Cloud Text-to-Speech: Audio Versions of Every Article
Adding an audio version of every article is one of those low-effort, high-leverage moves: it makes your content accessible to people who’d rather listen, it gives you a “play this article” widget that lifts time-on-page, and the audio file itself becomes another thing search and assistants can surface. The work is entirely automated — text goes in, an MP3 comes out — so the only real decisions are which voice sounds least like a robot and which free tier covers your back catalog.
We auto-generate audio versions of the same articles on both Azure Neural TTS and Google Cloud Text-to-Speech, on the free tiers, and listen. Short answer: this one’s an honest toss-up. Both produce genuinely natural neural voices, both give you SSML control, and both run our audio pipeline for $0/month. Azure’s free tier is 500,000 characters/month (~60–80 article audio versions of neural voices); Google’s is 1,000,000 characters/month of Standard voices and 1,000,000 characters/month of WaveNet/Neural2 premium voices. Pick by ecosystem and by which voice you’d rather hear.
This is the breakdown from the running lab on tygart.media — voice naturalness, SSML control, voice variety, free ceilings, and the accessibility/SEO payoff.
The free-tier ceilings
Free-tier ceilings for Neural TTS vs Cloud TTS.
How we do it
Azure
Google Cloud
Verdict
Free neural/premium chars/month
500,000 (Neural)
1,000,000 (WaveNet/Neural2)
Google — 2× headroom
Free standard chars/month
n/a (neural is the tier)
1,000,000 (Standard)
Google on raw volume
Roughly how many article audios
~60–80 neural/mo
~140 premium/mo
Google
Always-free
Yes
Yes
Tie
Our actual bill
$0
$0
Tie where it counts
A 1,200-word article runs around 6,500–7,000 characters, so Azure’s 500K neural budget covers roughly 60–80 full article audio versions a month, and Google’s 1M premium budget covers roughly twice that. For a publisher shipping a handful of articles a week, both stay free with room to spare — the 2× gap only bites if you’re voicing a large back catalog in one go.
Voice quality and SSML control
Voice quality and SSML control.
This is where you actually choose, and it’s genuinely close.
How we do it
Azure
Google Cloud
Verdict
Voice naturalness
Excellent, very expressive
Excellent, very natural
Tie — both clear the “robot” bar
Voice variety
Huge neural catalog, many styles
Large WaveNet/Neural2 catalog
Slight edge Azure on styles
Speaking styles / emotion
Yes (cheerful, newscast, etc.)
More limited emotional styles
Azure
SSML control
Full SSML + style/prosody tags
Full SSML
Azure, slightly
Custom voice
Yes (custom neural voice)
Yes (custom voice)
Tie
Languages / locales
140+ locales
50+ languages, many voices
Azure on locale breadth
Both clear the bar that matters: neither sounds like a 2010-era text-to-speech engine, and a casual listener wouldn’t immediately clock either as synthetic. Azure edges ahead on expressiveness — its neural voices support named speaking styles (newscast, cheerful, empathetic) that are perfect for an article read-aloud, and its SSML supports fine prosody control. Google’s Neural2 voices are beautifully natural and, to some ears, a touch warmer; the emotional-style controls are just a little thinner.
The accessibility and SEO payoff
Accessibility and SEO payoff of audio articles.
The audio isn’t only a nice-to-have. It does real work.
How we do it
Azure
Google Cloud
Verdict
Accessibility win
Listen instead of read
Listen instead of read
Tie
Output format
MP3 / WAV / streaming
MP3 / LINEAR16 / OGG
Tie
Pipeline integration
REST + SDKs
REST + SDKs
Tie
Time-on-page lift
Audio widget keeps people on page
Same
Tie
An audio version gives screen-reader users and “I’d rather listen” users a first-class way to consume the piece, and the on-page player tends to lift dwell time — a signal that doesn’t hurt. The mechanics are identical on both clouds: feed text, get an MP3, embed it.
What surprised us
Both are genuinely good now. We expected one to clearly win on naturalness and neither did — the synthetic-voice era is over on both clouds.
Azure’s speaking styles are the sleeper feature. Being able to render an article in a “newscast” or “cheerful” style without writing prosody by hand made the read-alouds noticeably more engaging.
Google’s free character budget is the bigger one. 1M premium characters is real headroom; if you’re voicing a back catalog, that matters more than a half-point of naturalness.
The MP3s are interchangeable. Once embedded, listeners couldn’t reliably tell which cloud voiced which article in a blind test we ran on ourselves.
The takeaway
Pick Azure Neural TTS if you want maximum expressiveness — named speaking styles, fine prosody control, and the broadest locale catalog — and your Microsoft ecosystem is already where the rest of your stack lives. The 500K free characters cover a normal publishing cadence comfortably.
Pick Google Cloud Text-to-Speech if you want the larger free character budget (1M premium) for voicing a big back catalog, or you simply prefer the warmth of the Neural2 voices, and your stack is GCP-centric.
For us this is the rare comparison with no loser. We run the pipeline on whichever cloud the rest of that article’s workflow already lives on — and the listener can’t tell the difference either way.
This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud on the free tiers, generating audio versions of the same articles on each to hear where the voices differ. The lab lives on tygart.media; the findings publish here.
How many free characters do Azure and Google text-to-speech give you per month?
Azure Neural TTS gives 500,000 free neural characters per month, which is roughly 60–80 article audio versions. Google Cloud Text-to-Speech gives 1,000,000 free Standard characters and 1,000,000 free WaveNet/Neural2 premium characters per month, roughly double Azure’s premium headroom. Both stay free for a normal publishing cadence.
Which text-to-speech sounds more natural, Azure or Google?
Both produce genuinely natural neural voices, and in blind listening neither clearly wins. Azure edges ahead on expressiveness with named speaking styles like newscast and cheerful, while Google’s Neural2 voices are very natural and, to some ears, slightly warmer. The synthetic-robot problem is solved on both.
Can I auto-generate an audio version of every blog post for free?
Yes. Both clouds expose a simple REST API that turns article text into an MP3, and their free character budgets cover a typical few-articles-a-week cadence at $0. Google’s larger free budget is better if you want to voice a big back catalog in one pass.
Does Azure Neural TTS support SSML and speaking styles?
Yes. Azure supports full SSML plus named speaking styles (newscast, cheerful, empathetic and more) and fine prosody control, which makes article read-alouds noticeably more engaging. Google also supports full SSML, but its emotional-style controls are thinner.
Does adding an audio version of articles help accessibility and SEO?
Yes. An audio version gives screen-reader and listen-first users a first-class way to consume the content, improving accessibility, and the on-page audio player tends to lift time-on-page, which is a positive engagement signal. The benefit is identical whether you generate the audio on Azure or Google.
Azure Translator vs Google Cloud Translation: 2M Free Characters, Tested
Translating your content is one of the cheapest ways to multiply its reach — every article becomes five articles the moment you ship it in five languages. The catch is that machine translation is metered by the character, and a content pipeline burns characters fast. So the real question for a bootstrapped publisher isn’t “which engine is best?” — it’s “which free tier lets me run a multilingual pipeline forever without ever seeing a bill?”
We translate the same articles into multilingual variants on both Azure Translator and Google Cloud Translation, on the free tiers, and watch where each one runs out. Short answer: for a perpetual $0 pipeline, Azure Translator wins on the ceiling — its free tier is 2,000,000 characters/month and it’s always free, which is roughly 300 article-length translations a month. Google Cloud Translation gives you a generous-but-capped 500,000 characters/month and then it’s paid, and it earns its keep on quality and language coverage.
This is the breakdown from the running lab on tygart.media — free ceilings, translation nuance, document vs text, and which one we actually point the pipeline at.
The free-tier ceilings
Free-tier ceilings for Translator vs Cloud Translation.
This is the headline difference, and it’s not close.
How we do it
Azure
Google Cloud
Verdict
Free characters/month
2,000,000, always free
500,000, then paid
Azure — 4× the ceiling
Roughly how many articles
~300 article translations/mo
~75 article translations/mo
Azure
What happens at the cap
Pay-as-you-go kicks in
Pay-as-you-go kicks in
Tie (mechanism)
Always-free vs 12-month trial
Always free
Always free (the 500K is perpetual)
Tie
Fit for a perpetual pipeline
Excellent
Tight
Azure
The math is the whole story. A typical 1,200-word article is around 6,500–7,000 characters. Translate it into five languages and you’ve spent ~35,000 characters on one article. Azure’s 2M ceiling absorbs dozens of articles across multiple languages every month without a cent; Google’s 500K runs dry after a couple of weeks of the same cadence. If your single hard constraint is “never pay for translation,” Azure is the answer before you even look at quality.
Translation quality and nuance
Translation quality and nuance.
Free ceilings decide whether you can run the pipeline. Quality decides whether you should publish what comes out.
How we do it
Azure
Google Cloud
Verdict
Engine
Neural MT, custom models available
Neural MT (NMT), strong general model
Slight edge Google on nuance
Idiom / register handling
Good, occasionally literal
More natural on idioms and tone
Google
Technical terminology
Reliable, customizable glossary
Reliable
Tie
Custom/glossary control
Custom Translator + dictionary
Glossary + AutoML (paid)
Azure on free customization
Major-language quality
Excellent both ways
Excellent both ways
Tie
On high-resource languages — Spanish, French, German, Portuguese — both engines produce output we’d publish with a light editorial pass. Google has a slight edge on idiom and register: it tends to “sound like a person” a beat more often, especially on conversational copy. Azure closes most of that gap with Custom Translator and inline dictionaries, which let you pin brand terms and preferred phrasings — and those customization tools are usable inside the free workflow.
Language coverage and document mode
Language coverage and document mode.
How we do it
Azure
Google Cloud
Verdict
Languages supported
100+
100+ (NMT subset varies)
Tie
Long-tail / low-resource
Broad
Broad, often strong
Google, slightly
Document translation
Yes (preserves formatting)
Yes (separate API surface)
Tie
Text translation API
Simple REST
Simple REST
Tie
Batch throughput
High
High
Tie
Both clouds clear 100 languages, so coverage isn’t a deciding factor for a Western-market content site. Document translation — feeding in a formatted file and getting the same layout back in another language — exists on both; we mostly use plain text translation because our content is markdown and we re-render it ourselves.
What surprised us
The character ceiling, not the quality, is the real constraint. We went in expecting a quality shootout and came out realizing that for a content pipeline, “2M free vs 500K free” decides the workflow long before anyone compares a single sentence.
Azure’s always-free 2M is genuinely always free. It’s not a 12-month trial that lapses into charges — it resets every month indefinitely. That’s rare enough that we double-checked it.
Google’s output reads slightly more human on conversational copy. For marketing-voice pieces we noticed Google needed less editorial cleanup; for technical articles the two were indistinguishable.
Glossaries matter more than the base engine. Once you pin your brand and product terms, the gap between the two narrows to almost nothing.
The takeaway
Pick Azure Translator if your priority is a perpetual multilingual content pipeline that never bills you — the 2M-character always-free ceiling is built for exactly this, and Custom Translator gives you brand-term control for free. It’s our default for high-volume article translation.
Pick Google Cloud Translation if quality on conversational, idiom-heavy copy is your top concern and your volume fits comfortably under 500K characters/month — its NMT output tends to need a lighter editorial pass.
For us, running the same site on both clouds, the translation pipeline lives on Azure: at our cadence we’d blow through Google’s free tier in two weeks, and Azure’s ceiling means the multilingual variants ship at $0, month after month.
This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud on the free tiers, translating the same articles on each to see where the ceilings really sit. The lab lives on tygart.media; the findings publish here.
How many free characters do Azure Translator and Google Cloud Translation give you per month?
Azure Translator’s free tier is 2,000,000 characters per month and it’s always free, resetting every month indefinitely. Google Cloud Translation’s free tier is 500,000 characters per month, after which you pay per character. For a content pipeline, Azure’s ceiling is roughly four times larger.
Which machine translation is more accurate, Azure or Google?
Both use neural machine translation and produce publish-quality output on major languages. Google has a slight edge on idiom, tone, and conversational register, while Azure closes most of that gap with its free Custom Translator and dictionary features. For technical content the two are hard to tell apart.
Can I run a multilingual website translation pipeline for free?
Yes. Azure Translator’s 2,000,000 free characters per month is enough for roughly 300 article-length translations, which covers a typical publishing cadence across several languages at $0. Google’s 500,000 free characters works for lower-volume sites but runs out faster at the same pace.
Does Azure Translator support document translation that keeps formatting?
Yes. Azure offers a document translation mode that preserves the original layout and formatting of files, alongside a simple text translation REST API. Google Cloud Translation offers document translation too. We mostly use plain text translation because our content is markdown that we re-render ourselves.
How many languages do Azure Translator and Google Cloud Translation support?
Both support more than 100 languages, so coverage is rarely the deciding factor for a Western-market site. Google sometimes edges ahead on lower-resource languages, but for common European and Latin American languages the two are equivalent in reach.
Here’s the number that reorganized how we think about search: ~84% of our organic traffic comes from Bing. Not Google. Bing — and the Copilot and ChatGPT surfaces that draw on Bing’s index. Yet for a long time, like nearly everyone, we watched only Google Search Console and treated Bing as an afterthought.
That’s the blind spot this article is about. Short answer: use both consoles, but if Bing drives your traffic, stop treating Bing Webmaster Tools as optional — it has data, indexing controls, and an AI-insights surface that Google Search Console doesn’t, and it’s reporting on the search engine that’s actually sending you readers.
This is the side-by-side from running both consoles on the same media property: what each one tells you, where Bing is quietly ahead, and how we wired the Bing Webmaster Tools API into our editorial calendar.
The core reporting — query, position, CTR
Core reporting: query, position, CTR.
At the surface, the two consoles look like twins. Both give you queries, impressions, clicks, average position, and CTR. The differences are in coverage and freshness.
How we do it
Job
Bing Webmaster Tools
Google Search Console
Verdict
Query / position / CTR
Yes, per query and page
Yes, per query and page
Tie on the basics
Data freshness
Often faster to update
~2-3 day lag
Bing edges ahead
Historical window
Generous
16 months
Toss-up
API access
Full API: position + CTR per query/page
Search Analytics API
Bing — the API is the underrated weapon
AI / Copilot insights
Dedicated AI-traffic insights
No equivalent surface yet
Bing, clearly
Market it reports on
Bing + Copilot + ChatGPT-via-Bing
Google only
Depends on your traffic mix
The honest read: for the basic dashboard, they’re close enough that you’d never switch for the UI. The reasons to take Bing seriously are whose traffic it reports on and what it lets you do about it — the AI insights tab and the API.
Indexing: IndexNow vs crawl-when-it-feels-like-it
Indexing: IndexNow vs crawl-when-it-feels-like-it.
This is the most concrete operational difference, and it’s lopsided.
How we do it
Job
Bing Webmaster Tools
Google Search Console
Verdict
Tell it about a new URL
IndexNow — push, indexed near-instantly
URL Inspection → “Request indexing” (queued)
Bing — push beats poll
Bulk submission
IndexNow ping + sitemap
Sitemap, then wait
Bing
Control over crawl
Crawl control, block/allow
Limited crawl controls
Bing — more knobs
Re-crawl on edit
Re-ping IndexNow
Hope, or re-request
Bing
IndexNow is the standout. Instead of submitting a sitemap and waiting for a crawler to wander by, you push a URL the moment it changes and it’s picked up almost immediately — and because IndexNow is a shared protocol, one ping notifies participating engines. Google’s model is still largely “request indexing and wait.” For a content site that publishes and edits constantly, push beats poll every time. We ping IndexNow on publish and on every meaningful edit.
The AI / Copilot insights tab
The AI insights tab is the differentiator.
Google Search Console has no real equivalent here yet. Bing Webmaster Tools surfaces AI-traffic insights — visibility into how your content shows up across Bing’s AI-powered and Copilot surfaces. Given that those surfaces (and ChatGPT’s web results, which draw on Bing) are an increasing share of how people find answers, this is the single console feature most aligned with where discovery is heading. If you care about GEO at all, it’s the dashboard that tells you whether the AI assistants are actually pulling you in.
Wiring the BWT API into the editorial calendar
The Bing Webmaster Tools API is the part most sites never touch, and it’s the most actionable. It returns position and CTR per query and per page — which is a ready-made content-optimization loop:
Pull query/position/CTR from the BWT API on a schedule.
Find pages ranking on page one with weak CTR (good position, bad headline/meta) — fast wins.
Find queries where we rank position 5-15 with real impressions — the “one good edit from page one” list.
Feed both lists straight into the editorial calendar as prioritized rewrites.
Because Bing drives most of our traffic, this loop is pointed at the engine that actually moves our numbers. Running the same loop off Google Search Console’s API would optimize for the 16% of traffic, not the 84%.
What surprised us
Bing’s data is often fresher than Google’s. We frequently see new queries in Bing Webmaster Tools before they show up in Search Console.
IndexNow is faster than anything Google offers — and it’s free and standard. The gap between “push and it’s indexed” and “request and wait” is real and daily.
The AI insights tab has no GSC counterpart. For a site doing GEO, that’s the most forward-looking surface either console offers.
Almost nobody verifies their site in Bing Webmaster Tools. You can import directly from Google Search Console in a couple of clicks, so the only reason most sites skip it is that they’ve never looked at where their traffic comes from.
The takeaway
This was never a “pick one” — it’s “stop ignoring one.” Google Search Console is still essential; Google isn’t going anywhere. But running only GSC is a bet that Google’s view of your site is the only one that matters, and our traffic data says that bet is wrong by a factor of five.
Use both. Watch Google Search Console for the Google slice. But if a large share of your organic traffic comes from Bing — and a surprising number of content sites are in exactly that position without checking — then Bing Webmaster Tools is your primary console: fresher data, IndexNow for instant indexing, the AI/Copilot insights surface, and an API you can wire straight into your editorial calendar.
The 84% lesson is simple: measure where your readers actually come from, then watch the console that reports on it. For us, that meant promoting Bing from afterthought to the dashboard we open first.
This is part of our “Two Clouds, One Site” series — we run the same media property on Azure and Google Cloud, on the free tiers, and report what watching both ecosystems actually teaches us. The lab lives on tygart.media; the findings publish here.
Should I use Bing Webmaster Tools if I already use Google Search Console?
Yes — they report on different search engines, so using only Google Search Console hides all of your Bing performance. If any meaningful share of your traffic comes from Bing, Copilot, or ChatGPT’s Bing-powered results, Bing Webmaster Tools shows data and offers indexing controls that Search Console doesn’t. You can import your site from Search Console in a couple of clicks.
What is IndexNow and is it faster than Google indexing?
IndexNow is a protocol that lets you push a URL to search engines the moment it’s published or changed, instead of waiting for a crawler. It’s typically much faster than Google’s “request indexing and wait” model, and because it’s a shared standard, one ping notifies participating engines. For sites that publish or edit frequently, it’s a meaningful indexing-speed advantage.
Does Bing Webmaster Tools have an API?
Yes. The Bing Webmaster Tools API exposes per-query and per-page data including position and CTR, plus URL submission. That makes it practical to pull your search performance on a schedule and feed it into a content-optimization loop — for example, flagging page-one results with weak CTR or near-miss rankings to prioritize for rewrites.
What does the Bing Webmaster Tools AI insights tab show?
It surfaces how your content appears across Bing’s AI-powered and Copilot surfaces, giving visibility into AI-driven discovery that Google Search Console has no direct equivalent for yet. For sites focused on Generative Engine Optimization, it’s the most forward-looking view either console offers into whether AI assistants are pulling in your content.
Why would a site get most of its traffic from Bing instead of Google?
It’s more common than people assume, especially for niche or B2B content, sites strong in Bing-heavy regions or browsers, and content that surfaces well in Copilot and ChatGPT’s Bing-powered results. The lesson is to measure your actual referral mix rather than assume Google dominates — many sites only discover their Bing share once they verify in Bing Webmaster Tools.
Pick a serverless platform and you’re picking a default for the next five years of your stack. Most comparisons of Azure Functions vs Google Cloud Run are written from the docs. This one isn’t — we deployed the same worker to both, in production, on the free tiers, and watched what happened.
The worker is simple on purpose: it takes a webhook, does a little work, writes a record, returns JSON. The kind of glue every real system has dozens of. Boring is exactly what you want when you’re measuring the platform and not the app.
The short answer
The short answer — Functions vs Cloud Run.
If you just want the verdict: Cloud Run wins for anything containerized and anything where you care about not storing deploy keys. Azure Functions wins when your automation already lives in the Microsoft ecosystem and benefits from Logic Apps, Event Grid, and Entra sitting right next door. Both run our worker for $0/month. The tie-breakers are deploy security and what else is in the neighborhood.
Now the detail.
Deploying the same worker
Deploying the same worker on both clouds.
This is where the two platforms feel most different, and where Google Cloud quietly pulls ahead.
How we do it
Azure Functions
Google Cloud Run
Verdict
Unit of deploy
Function app (code + host)
Container image
Cloud Run if you’re already containerized
Deploy auth
Publish profile / service principal
Workload Identity Federation — no stored keys
Cloud Run, decisively
Cold start
Noticeable on Consumption plan
Negligible at our scale
Cloud Run
Local dev parity
Functions Core Tools (good)
“It’s just a container” (great)
Cloud Run
The headline is the deploy auth. Our Cloud Run workers deploy from GitHub Actions using Workload Identity Federation — GitHub proves its identity to Google with a short-lived token, and no service-account key is ever stored in the repo. That’s not a convenience; it’s the single biggest reduction in credential risk you can make in a CI/CD pipeline. Azure Functions can get close with OIDC + a service principal, but the container-native, keyless Cloud Run path was simpler to lock down and is the model we standardized on.
What the free tier actually gives you
Both platforms have genuinely generous always-free serverless tiers. The numbers that matter for a glue worker:
How we do it
Metric
Azure Functions
Google Cloud Run
Verdict
Free requests/month
1,000,000
2,000,000
Google — 2× headroom
Free compute
400,000 GB-s
360,000 GiB-s + 180,000 vCPU-s
Roughly even
Scale to zero
Yes (Consumption)
Yes
Tie
Max instances control
Yes
Yes (and per-service concurrency)
Cloud Run, slightly
Our actual bill
$0
$0
Tie where it counts
At our volume — thousands of invocations a month, not millions — both are free and stay free. The 2M-vs-1M request gap only matters if you’re genuinely high-traffic. For most glue workloads, you will never see a bill on either.
The neighborhood effect
A serverless function is rarely alone. It fires because something happened and it triggers something else afterward. That’s where the ecosystems diverge — and where Azure earns its keep.
Azure Functions sits next to Logic Apps (4,000 free built-in actions/month), Event Grid (100,000 free operations/month), and Entra ID for identity. If your automation is event-driven and Microsoft-centric, the glue around the function is already there and already free.
Cloud Run sits next to Eventarc, Cloud Workflows, Pub/Sub, and Cloud Scheduler — the same pattern on Google’s side, equally capable.
Neither is “better” in the abstract. The right answer is whichever cloud your other services already live in. A function that triggers a Logic App next door beats a function that has to reach across clouds to do the same thing.
What surprised us
What surprised us in the head-to-head.
Cloud Run cold starts basically disappeared. At our concurrency the container was warm often enough that we stopped thinking about it. Azure Functions on the Consumption plan had more noticeable cold starts for the same workload.
Azure’s free side-resources are real. Functions itself is free, but watch the storage account and Application Insights it provisions alongside — those can accrue tiny charges. Set a budget alert on day one.
Keyless deploy changed our security posture more than any single config. Once the repo holds zero secrets for deploys, an entire category of “leaked key” incidents just can’t happen.
The takeaway
For a containerized, security-conscious, GitHub-Actions-driven stack, Cloud Run is our default — the keyless deploy and the request headroom settle it. But “default” isn’t “only”: when a workload belongs in the Microsoft ecosystem — triggered by Microsoft events, feeding Microsoft services, governed by Entra — Azure Functions is the right tool, and it runs for the same $0.
Run the same worker on both for a week. The platform stops being a religious debate and becomes a placement decision: put the work where its neighbors already are.
This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud, on the free tiers, and write up what we learn. The lab lives on tygart.media; the findings publish here.
Is Azure Functions or Cloud Run cheaper?
For typical glue workloads, both are free and stay free. Cloud Run offers more free requests per month (2M vs 1M) and Azure offers 400,000 GB-seconds of free compute. At thousands of invocations a month you will not see a bill on either; the cost difference only appears at high traffic.
Which is more secure to deploy?
Cloud Run, because it supports keyless deploys via Workload Identity Federation — GitHub Actions authenticates with a short-lived token and no service-account key is stored in the repo. Azure Functions can approximate this with OIDC and a service principal, but the container-native keyless path is simpler to secure.
Can I run the same code on both Azure Functions and Cloud Run?
Yes. If you package the worker as a container, Cloud Run runs it directly and Azure Functions can run it via a custom handler or containerized function. We deploy the same worker logic to both; the differences are in deploy tooling and the surrounding event services, not the code.
When should I choose Azure Functions over Cloud Run?
Choose Azure Functions when your automation already lives in the Microsoft ecosystem — triggered by Event Grid, orchestrated by Logic Apps, or governed by Entra ID. Co-locating the function with the services it talks to beats reaching across clouds.
Do serverless cold starts matter on either platform?
At moderate concurrency, Cloud Run cold starts were negligible in our testing because the container stayed warm. Azure Functions on the Consumption plan showed more noticeable cold starts for the same workload. For latency-sensitive endpoints, test under your real traffic before deciding.
Most “Azure vs Google Cloud” articles are written by people who run neither in production. They paraphrase the pricing pages and call it a comparison.
We do something different: we run the same media property on both clouds at the same time — and the entire thing costs $0/month. Google Cloud is the live operational stack. Azure is a parallel “newsroom” of always-free services running on a dedicated lab domain, tygart.media, mirroring each capability of the live site. Two clouds, one operation, both AI ecosystems watching it work.
This is the desk-by-desk breakdown — what each cloud actually does for us, where the free tier runs out, and which one wins each specific job. No theory. This is the running system.
Why run on both clouds at once
Why run on both clouds at once.
There’s a strategic reason beyond “free is fun.” Search and AI assistants don’t share a brain. Google’s models optimize for Google’s index; Microsoft’s Copilot and Bing optimize for Microsoft’s graph. When ~84% of your organic traffic comes from Bing, having your stack only inside Google’s telemetry is a blind spot.
Running enrichment through Azure puts the same content inside Microsoft’s service graph the same way Google Cloud puts it inside Google’s. You stop guessing how each ecosystem sees you, because you’re operating inside both.
The serverless compute plane
The serverless compute plane.
The heart of the stack: code that runs after you push a file and close the laptop.
How we do it
Azure
Google Cloud
Verdict
Service
Azure Functions
Cloud Run
Cloud Run for containers; Functions for glue
Free ceiling
1M requests/month
2M requests/month
Google, on raw headroom
Deploy model
Functions Core Tools / GitHub Actions
Keyless deploy via Workload Identity Federation
Google — no stored keys is a real security win
What surprised us
Generous, but watch billable side resources
Cold starts negligible at our scale
—
Our bill
$0
$0
Tie where it counts
Pick Cloud Run if you’re already containerized and want keyless CI/CD. Pick Azure Functions if your automation lives in the Microsoft ecosystem and you want Logic Apps next door.
The content enrichment desks
This is where Azure’s always-free tier quietly outclasses expectations — a full newsroom of AI services that never bill at our volume.
How we do it
Job
Azure
Google Cloud
Verdict
Translation
Translator — 2M chars/mo free (~300 articles)
Cloud Translation
Azure — bigger perpetual free ceiling
Article audio
Neural TTS — 500K chars/mo
Cloud Text-to-Speech
Toss-up; both natural
Entity extraction (for GEO)
AI Language — 5K records/mo
Cloud Natural Language
Azure — likely the same signal family Bing uses
Site search
Azure AI Search — 3 indexes free
Vertex AI Search
Azure — it’s the engine behind Bing
The entity-extraction line matters most. We feed articles through Azure AI Language to pull named entities and key phrases, then saturate the content with them. We’re optimizing for the same entity signals Microsoft’s own systems use to select content — which is the whole game when Bing drives most of your traffic.
The storage and front-end layer
How we do it
Job
Azure
Google Cloud
Verdict
Document store
Cosmos DB — 1,000 RU/s + 25GB free
Firestore
Azure — Cosmos free tier is generous (one per subscription)
Relational
Azure SQL — serverless free
Cloud SQL (no perpetual free)
Azure, clearly
Static hosting
Static Web Apps — 100GB bandwidth
Firebase Hosting
Tie; both excellent
For a small operations ledger or a knowledge base, Azure’s always-free Cosmos DB and serverless SQL are the standout — Google Cloud has no equivalent perpetual-free relational tier.
What it actually costs: nothing (if you’re disciplined)
What it actually costs when you stay disciplined.
The honest caveat: free compute can still trigger billable side resources. A “free” VM drags along disks, public IPs, and monitoring logs that bill immediately with no throttling. The discipline that keeps the bill at zero:
Deploy from the free-services blade, not the general catalog.
Set a budget alert on day one — before you provision anything.
Prefer serverless over VMs — the consumption tiers reset monthly and don’t drag side resources.
One Cosmos DB free tier per subscription — plan around it.
Do that, and a real, AI-enriched media property runs across two clouds for $0.
The takeaway
Single-cloud is a bet that one ecosystem’s view of your content is the only one that matters. When the traffic data says otherwise — when most of your readers arrive through the other company’s search and AI — bilateral cloud stops being a novelty and becomes the obvious posture. The free tiers make it cost nothing but discipline.
Is it really free to run on both Azure and Google Cloud?
Yes, at small-site scale. Both clouds offer always-free serverless tiers (Azure Functions 1M requests/month, Cloud Run 2M requests/month) plus free AI, storage, and hosting services. The cost risk is billable side resources like VM disks and public IPs — avoidable by staying serverless and setting a budget alert.
Which is better for serverless, Azure or Google Cloud?
Cloud Run wins on raw request headroom (2M vs 1M/month) and keyless deploys via Workload Identity Federation. Azure Functions wins if your automation already lives in the Microsoft ecosystem and benefits from Logic Apps and Event Grid next door.
Why would you run the same site on two clouds?
AI ecosystems don’t share telemetry. Google’s models favor Google’s index; Bing and Copilot favor Microsoft’s graph. If a large share of your traffic comes from Bing, running enrichment through Azure puts your content inside Microsoft’s service graph instead of leaving it a blind spot.
Does Azure have a better free tier than Google Cloud?
For perpetual always-free services, Azure is broader — 65+ always-free services including Cosmos DB (1,000 RU/s + 25GB) and serverless Azure SQL, which Google Cloud has no direct perpetual-free equivalent for. Google Cloud wins on serverless request volume and keyless security.
What’s the catch with Azure’s always-free tier?
Limits reset monthly and overages bill immediately with no throttling. Free VMs also trigger billable disks, public IPs, and monitoring logs. Deploy from the free-services blade, prefer serverless, and set a budget alert before provisioning.
