OnWeb · Web engineering and cloud
Managed web hosting on Google Cloud.
Infrastructure on Cloud Run with automatic scaling at peak, a CDN in front, certificates that renew themselves, daily backups and checks every 5 minutes. No server shared with strangers, and no ticket sitting unanswered over a holiday.
We work in English, Portuguese and Spanish. Headquarters in Belo Horizonte, Brazil.
01Overview
Web hosting
Web hosting is the infrastructure decision that shows up most in results and gets the least attention. It decides how long the server takes to start responding, what happens when 400 people arrive at once after a campaign, and how long the site stays down when something breaks on a Sunday.
Netlinks hosts through OnWeb, the group engineering practice, on managed Google Cloud. That means the account, the server, the certificate, the content delivery network and the backups all have an owner: the same team that handles technical SEO and website management.
It is the same infrastructure that carries the projects Netlinks builds, from the Next.js sites we run for Planning to the SP Labor store, migrated to Google Cloud with its homepage closing at 97 on mobile and 99 on desktop in PageSpeed.
- 5 min
- between availability checks
- 97 and 99
- PageSpeed mobile and desktop on the SP Labor homepage
- 4
- countries served, with offices in Belo Horizonte, London, Santiago and Panama City
- 24h
- of WhatsApp support with Alfred and the team
02Definition
What managed web hosting means
Managed hosting means somebody answers for the whole stack instead of renting you disk space. The difference shows in the questions you stop having to answer:
- Who applies the server security patch? On commodity hosting, you do. On managed hosting, the team running the cloud does.
- Who notices the site went down at 3 a.m.? On commodity hosting, your customer. On managed hosting, monitoring, which fires an alert within minutes.
- What happens when traffic triples? On commodity hosting the site slows to a crawl or falls over. On Cloud Run the application scales in seconds and shrinks back afterward.
- Where is the backup, and has anyone restored it? On commodity hosting the answer is usually vague. On managed hosting there is a daily copy and a restore test.
- Who watches the bill? On Netlinks managed hosting, cloud spend is reviewed month over month, with billing anomaly alerts in place.
You still own your infrastructure and your data. What changes is that there is a team on call instead of a control panel with a ticket form.
03Infrastructure
What runs under the hosting
The base is Google Cloud, with services chosen to match the type of site. No generic server configured once and forgotten for three years.
Cloud Run
A containerized application that scales automatically from zero to peak and back. You pay for real usage, with no idle machine waiting for next December.
Cloud SQL
Managed PostgreSQL or MySQL with automatic backups, point-in-time recovery and read replicas when volume calls for them.
CDN and caching
Static assets served close to the visitor, with cache rules by file type and controlled invalidation on publish.
Managed SSL
Certificates issued and renewed automatically, covering additional domains and subdomains. No more outages from an expired certificate.
Edge protection
A layer in front of the site filtering abuse, brute-force attempts and automated traffic that only burns resources.
Observability
Structured logs, latency and error metrics, availability checks and alerts that land in the team WhatsApp group.
05Performance
Hosting and speed: where infrastructure decides the score
A large share of page load time is decided before the browser paints anything: the time the server takes to start responding. A slow server puts a ceiling on your Core Web Vitals that no amount of image optimization will lift.
That is where infrastructure earns its keep: physical distance to the visitor, edge caching, compression, a modern connection to the browser, and a database that stays quick under load. The rest of the work, images, fonts and JavaScript, belongs to website optimization.
The SP Labor migration shows both halves together: moving to Google Cloud came with 6,433 images compressed from 4.0 GB to 1.4 GB and a technical audit that cut errors from 753 to 326 pages. The case study is SP Labor.
- Server response time measured alongside Search Console field data
- Edge caching configured by content type, with automatic invalidation on publish
- Images served in modern formats at the size the screen requests
- Database watched for slow queries, the most common cause of a heavy store page
06Switching
How we move you off your current host
Changing hosts scares people because everyone remembers a full day of downtime. Done with a method, the visitor sees nothing at all.
- 01
Inventory
Domains, subdomains, mailboxes, certificates, scheduled jobs, integrations, and everything the current server does beyond serving pages.
- 02
Copy and test
The new environment is built from a copy of the site and tested on a password-protected temporary address, with forms, checkout and integrations exercised.
- 03
Sync
A final database and file sync immediately before the switch, so no order or signup from that day is lost.
- 04
DNS cutover
Release in an agreed window, with time-to-live lowered beforehand and both environments answering during the transition.
- 05
Verification
Certificates, redirects, indexing, speed, email and integrations checked one by one the following day.
- 06
Follow-up
Two weeks of daily monitoring on errors, availability and rankings before the old server is switched off.
07Security
Security, backups and what happens when it goes wrong
Every host promises security. What separates them is what exists on the day of the incident: a recent copy someone has already restored, a record of who accessed what, credentials in a vault, and a response path written before the building caught fire.
On Netlinks managed hosting, credentials live in a secret manager, access follows least privilege, the site has daily database and file copies, and restores are tested periodically. The edge layer filters abuse before it reaches the application.
When the problem sits in the site rather than the infrastructure, the same team handles it: cleanup, hardening and a written report are part of website management. Companies running a larger cloud footprint will find the full picture in cloud management.
08Fit
When it is worth switching hosts
Not every site needs to leave shared hosting today. It is worth moving when at least one of these sentences describes your operation:
- A campaign has already taken the site down. If a media push brings the site to its knees, the problem is infrastructure architecture, and automatic scaling solves it.
- An hour offline costs money. Stores, lead portals and booking platforms have a cost per minute of downtime. Monitoring and on-call stop being a luxury.
- Nobody knows where the backup is. The most common symptom, and the most expensive one on the day of the incident.
- Speed has hit a ceiling. You have already optimized images and plugins and server response time is still high.
- You operate in more than one country. A visitor in the United States or Europe waiting on a server in Brazil feels the delay, and so does Google.
If none of that applies, the honest recommendation is to stay where you are and invest in content and search. The diagnosis tells you which of the two cases you are in.
09The deliverable
What you receive
Finished work, approved by you in the App and shipped. Not a report that only describes the problem.
A Google Cloud environment
The application on Cloud Run, a managed database, storage and networking configured for your type of site.
CDN and caching
Static content distributed close to visitors, with cache rules by file type and invalidation on publish.
SSL that never lapses
Managed certificates renewed automatically, covering the main domain and subdomains.
Daily backups
Database and file copies with a defined retention window and periodic restore tests.
Monitoring and alerts
Availability checks every 5 minutes, latency and error metrics, alerts in the shared WhatsApp group.
Cost reporting
Cloud consumption by service, month over month, with billing anomaly alerts and tuning recommendations.
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
Diagnosis
A read of the site, its traffic, its peaks and what the current host actually delivers. No commitment.
- 02
Sizing
The environment, database, CDN and an estimated monthly cost defined before any contract.
- 03
Build and test
The new environment created from a copy of the site and tested behind a password-protected address.
- 04
Cutover
Final sync, DNS change in an agreed window, and item-by-item verification the following day.
- 05
Operations
Monitoring, backups, infrastructure updates and on-call enter the routine.
- 06
Quarterly review
Capacity, cost, security and what changes next quarter, reviewed with your team.
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
Comes from Ambev and Agibank. Owns link building, digital PR and the authority that holds up both rankings and citations inside AI answers.
Ambev · Agibank
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
Sites that became a sales channel
Once the form or the checkout carries part of your revenue, every minute offline has a price tag.
Operations with spikes
Campaigns, seasonality, launches or a press hit. Automatic scaling keeps the site up on exactly the day that matters.
Companies in more than one country
Visitors outside Brazil need fast responses. Content distribution and infrastructure in the right region solve it.
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 is included in Netlinks web hosting?
A Google Cloud environment with Cloud Run, a managed database, a CDN, SSL certificates renewed automatically, daily backups with restore testing, availability checks every 5 minutes and monthly cloud cost reporting.
How is this different from shared hosting?
On shared hosting your site sits alongside hundreds of others, scales badly under load and gets support through a ticket queue. On managed hosting the environment belongs to your project, scales on its own, has tested backups and a team on call when something breaks.
Can you migrate my site without downtime?
The goal is that visitors notice nothing. The migration runs with a new environment tested on a temporary address, a final database and file sync immediately before the switch, and a DNS cutover in an agreed window with both environments answering during the transition.
Does the hosting suit WordPress and WooCommerce?
It does, and that is one of the most common uses alongside Next.js projects. The environment is sized against page count, traffic volume and catalog weight.
What about corporate email?
Email and website are separate services and we recommend keeping them that way. We configure your domain's sending and authentication records for your email provider, without hosting mailboxes on the same server as the site.
How does support work when the site goes down?
Checks run every 5 minutes and the alert reaches the shared WhatsApp group once the site stays down past 5 minutes. From there it is diagnosis, restore or repair, with a written account of what happened.
Who owns the cloud account?
You do. We work both in your company's own account, with Netlinks administering it, and in an environment we manage with consumption reporting. Either way, the access and the data are yours and you can leave at any time.
How much does web hosting cost?
It depends on traffic, database size, file volume and the availability level the operation requires. The consumption estimate comes out of the sizing exercise, before any contract, and real cost is tracked month over month.
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.