OnWeb · Web engineering and cloud
Google Cloud management with no surprise on the invoice.
Planned migration, an environment sized against real usage, permissions reviewed, billing anomaly alerts and monitoring with someone on call. You get the cost report by service every month and know exactly what you are paying for.
We work in English, Portuguese and Spanish. Headquarters in Belo Horizonte, Brazil.
01Overview
Google Cloud management
Google Cloud management is the service of running a company's cloud when that company does not want to keep an infrastructure team of its own: migrating what still sits on an old server, sizing the environment against real usage, reviewing permissions, monitoring, responding to incidents and watching the bill month over month.
It is where money leaks quietly. A machine running 24 hours for a site that only gets visitors during business hours, a database oversized since migration day, a staging environment nobody switched off, a storage bucket holding backups from 2021. None of that takes the site down, and all of it lands on the invoice.
Netlinks administers Google Cloud through OnWeb, the group engineering practice, on the same infrastructure that runs the Netlinks App and our clients' sites. The people looking after your cloud are the people who also answer for the speed and the management of the site running on it.
- 753 to 326
- pages with errors in the SP Labor audit
- 4.0 to 1.4 GB
- of images compressed in the same project
- 5 min
- between availability checks
- 24h
- of monitoring, with alerts on WhatsApp
02Scope
What Google Cloud management covers
The contract covers the full cycle: getting into the cloud, staying secure inside it, and not paying more than you need. Every item below has a named owner and shows up in the monthly report.
Cloud migration
An inventory of what runs today, a staged migration plan, a tested target environment and a cutover in an agreed window, without stopping the business.
Cloud Run and containers
Packaged applications, versioned deploys, automatic scaling from zero to peak, managed domains and certificates.
Cloud SQL and data
A managed database with automatic backups, point-in-time recovery, read replicas when volume calls for them, and slow query review.
Spend under control
Consumption reporting by service, idle resource review, machine rightsizing and billing anomaly alerts.
Security and access
Least-privilege permissions, credentials in a secret manager, networks closed by default and edge protection against abuse.
Monitoring
Availability checks, latency and error dashboards, structured logs and alerts landing in the team WhatsApp group.
03Cost
Where a cloud bill leaks, and how we close it
Cloud bills grow by accumulation, not by decision. Nobody approves the increase: each project adds a resource, nobody switches off what is left over, and six months later the total has doubled while the business has not.
A cost review is the first thing we do when taking over an environment. It usually finds machines running outside working hours, forgotten staging environments, orphaned disks from deleted instances, old backups sitting in an expensive storage class, logs retained far past their usefulness, and egress traffic that a CDN should have served.
After the cleanup comes control: budgets with alerts, a consumption dashboard by service, a monthly review, and the rule that every new resource is born with an owner and an expiry date. The report goes to your team with the numbers in plain language.
- An inventory of everything in the project, each item with a declared owner and purpose
- Machines and databases rightsized against the last 30 days of real usage
- Staging environments powered down outside working hours
- Billing anomaly alerts that fire before the invoice closes
04Security
Cloud security: access, secrets and network
Most cloud incidents do not start with an exotic exploit. They start with a key left inside the codebase, a user holding owner rights who should have had read access, a database open to the whole internet, and a project that still trusts a former vendor's account.
The Netlinks security review runs through five fixed questions: who has access and to what, where credentials are stored, what is exposed to the internet, what is being logged, and how you recover from a disaster.
The result is an environment with least-privilege roles, secrets in a vault with rotation, a database reachable only by the application, audit logging enabled and backups with restores tested. When the problem sits in the site rather than the cloud, the same team fixes it, inside website management.
05Migration
What migrating to Google Cloud looks like
Migration is the moment of highest risk and highest payoff. Run in stages, with a tested environment and a defined rollback point, it happens without your customers noticing.
- Month 1
Inventory and design
What runs today, where, with which dependencies, at what data volume, and which windows the business allows. The output is the target design with a cost estimate.
- Month 1
Target environment
Project created, network, permissions, secret manager, database and application built and validated against a copy of the data.
- Month 2
Testing with real data
Site, integrations, forms, checkout and scheduled jobs exercised in the new environment, behind a password-protected address.
- Month 2
Cutover
Final sync, DNS change in an agreed window, with the old environment kept standing as the rollback point.
- Month 3
Stabilization
Scaling and caching tuned against real traffic, a cost review after the first full invoice, and repairs on whatever surfaced.
- Ongoing
Operations
Monitoring, backups, updates, security reviews and the monthly consumption report enter the routine.
06Track record
SP Labor: Google Cloud migration and a technical audit
SP Labor is a WooCommerce store selling laboratory equipment, with a large catalog and years of accumulated content. The site was migrated to Google Cloud and went through a technical audit closed on 21 August 2026.
The audit numbers: errors fell from 753 to 326 pages, warnings from 2,803 to 1,020, the sitemap went from 383 files to 20, and 6,433 images were compressed, cutting 4.0 GB down to 1.4 GB. The homepage closed at 97 on mobile and 99 on desktop in PageSpeed.
The point worth taking if you are weighing a migration: the gain did not come from changing servers alone. It came from using the move to fix what was wrong in the site, with both practices working together. The full case study is SP Labor.
07Engagement models
Your account or ours, and how much on-call
There are three contract shapes, and the choice comes down to who wants to own the billing account and how much on-call the operation needs.
| Client account | Netlinks managed environment | One-off project | |
|---|---|---|---|
| Cloud billing | Direct with Google, on the company card | Inside the contract, with consumption reporting | As agreed in the scope |
| Administration | Netlinks with admin access | Netlinks, end to end | Delivery plus knowledge transfer |
| Monitoring | Included, with WhatsApp alerts | Included, with WhatsApp alerts | Optional, contracted separately |
| Best for | Companies with their own cloud policy | Teams who want one vendor to solve everything | A migration or review with a start and an end |
| Exit | Simply revoke the access | The project is transferred to your account | Ends fully documented |
08Operations
What you follow day to day
A well-run cloud is one you almost never have to look at. When you do, the information has to be ready:
- Availability, with checks every 5 minutes and every outage logged, duration included.
- Latency and errors by service, to separate slow application code from a database or network bottleneck.
- Consumption by service, compared against last month, with anomaly alerts configured.
- Security: permission changes, new access grants and configuration edits kept in an audit trail.
- Backups, showing the date of the last copy and the last restore test.
Alerts land in the WhatsApp group shared by your team and ours, where Alfred, the AI that runs our queue, answers 24 hours a day and escalates to a human when the case calls for it. The full picture is in technology.
09The deliverable
What you receive
Finished work, approved by you in the App and shipped. Not a report that only describes the problem.
Migration plan
An inventory of what runs today, the target design, a cost estimate and a stage-by-stage schedule with a defined rollback point.
A configured environment
Project, network, permissions, secret manager, database, application and certificates built to good practice.
Monthly cost report
Consumption by service, compared against the previous month, with tuning recommendations.
Security review
Access, secrets, internet exposure, audit logging and disaster recovery reviewed periodically.
Monitoring with alerts
Availability every 5 minutes, latency and error dashboards, alerts in the shared WhatsApp group.
Living documentation
How the environment is built, how to deploy, how to restore and who to call. Updated on every meaningful change.
10How it works
From the audit to the page going live
The same path on every project, with an owner and a date on each step.
- 01
Cloud diagnosis
A read of the current environment, the last few months of spend, the permissions and what is exposed. No commitment.
- 02
Plan by priority
What is a security risk, what is wasted money and what is a migration project, sorted by urgency.
- 03
Cleanup
First wave: idle resources switched off, excess permissions revoked, backups created and monitoring switched on.
- 04
Migration or restructuring
Where it applies, a new environment built, tested and cut over in an agreed window.
- 05
Monthly operations
Monitoring, backups, updates, cost review and reporting enter the cycle.
- 06
Quarterly review
Capacity, architecture, security and the roadmap for the next 90 days, reviewed with your leadership.
11Who leads
Who leads your project
The three of them own the process and manage the team on every account. No senior who shows up at kickoff and disappears: they sign off on the plan, review the work and talk to your team.
Digo Garcia
Founder and CAIO
Over 20 years in digital. Built and scaled Letras.mus.br, then worked at Méliuz and in the joint venture with Globo.com. Owns AI, technical SEO and engineering inside every project.
Letras.mus.br · Méliuz · Globo.com
André Mousinho
Chief SEO Officer
Comes from Rock Content, Tray/Locaweb and LWSA. Designs the keyword mapping, the content architecture and the GEO strategy that turns a brand into the answer.
Rock Content · Tray/Locaweb · LWSA
Gabriel Raposo
Chief Authority Officer
Leads link building and digital PR at Netlinks and ran, for Netlinks, the authority programs for BTG Pactual and Agibank. Before that, a career at Ambev. Owns the authority that holds up both rankings and citations inside AI answers.
Link building and PR · BTG Pactual and Agibank for Netlinks
And the team behind them: Nathália Barcala (cofounder and COO, governance), Roberto Murta (CTO), Marcelo Ligere (senior advisor, 30+ years, formerly Grupo Globo) and Alfred, the artificial intelligence that runs the day to day: delivery queue, reporting and 24/7 support on WhatsApp.
12Who it is for
Where this work pays off the most
Companies with no infrastructure team
The cloud exists, somebody set it up and left. You need an owner, documentation and a team on call.
Operations that grew fast
The invoice rose faster than the business and nobody can explain why. A cost review often pays for itself in the first quarter.
Teams leaving a legacy server
A dedicated server or legacy hosting with growing risk. The migration is planned in stages, with a rollback point.
13Case studies
Results with a name, a number and a date
Real projects, with what was done and what changed. No generic charts and no promises of a position.
FAQ
Frequently asked questions
What does Google Cloud management include?
The full administration of your environment on Google Cloud: migration, sizing, security, monitoring, backups, incident response and cost control, with a monthly consumption report by service.
Do you work in my Google Cloud account or yours?
Both. Many companies keep their own billing account and grant Netlinks admin access. Others prefer a managed environment, with consumption inside the contract and monthly reporting. Either way you can exit.
How do you bring the cloud bill down?
We start with an inventory, giving every resource an owner and a purpose. Then come rightsizing against real usage, powering down staging outside working hours, deleting orphaned disks and stale backups, reviewing egress traffic, and setting budgets with anomaly alerts.
Will migrating to Google Cloud take my site down?
Not when it runs in stages. The new environment is built and tested in parallel behind a password-protected address, the final sync happens immediately before the switch, and the old environment stays standing as a rollback point.
Do you also look after the site running on the cloud?
We do. Infrastructure and site sit with the same team, which removes the classic blame match between the server vendor and the website vendor. See website management and web hosting.
Which Google Cloud services do you use?
Whatever the project needs. For sites and applications the standard is Cloud Run for the app, Cloud SQL for the database, Cloud Storage for files, a CDN and load balancer in front, a secret manager for credentials, plus monitoring, logging and alerting.
Is there on-call outside business hours?
Monitoring runs 24 hours a day, with checks every 5 minutes and alerts in the shared WhatsApp group whenever something goes down. The level of human on-call outside business hours is set in the contract, based on how critical the operation is.
How much does Google Cloud management cost?
Cloud consumption depends on the environment and is estimated during sizing, before any contract. Management is a monthly fee based on the size of the environment and the on-call level. The initial diagnosis carries no commitment.
Keep reading
Related services
Next step
Get a diagnosis of your case
Tell us what your company sells and to whom. One of the three looks at your scenario, points out what is holding organic back today and shows where we would start.
- A review of your site and your market, with no commitment
- An answer from a senior specialist within 24 business hours
- A direct conversation: what can be done, in what order and how deep
Prefer WhatsApp?
Chat directly with a Netlinks Expert on WhatsApp.
Rather talk now? WhatsApp is answered by the team, with Alfred covering the rest of the day.
Talk to an Expert
Fill out the form and we will get back to you within 24 business hours.