Overview
Google’s index is unrivaled, but its SERP feeds ad-tech. Whoogle VPS Hosting gives you the relevance without the surveillance by proxy-fetching results on a private, always-on server. Dedicated EPYC vCPUs, DDR5 RAM, and pure-NVMe disks keep first-byte latency low, while a 10 Gbps backbone absorbs traffic spikes. Hourly billing lets you scale a personal node for pennies or a school-wide search head for busier hours.
Description
Whoogle Search is an ad-free metasearch engine that returns results without tracking or JavaScript. On Cloudzy, it’s preinstalled and served over HTTPS with a self-signed certificate by default.
Access the Web Interface
- Open your browser and go to: https://<server-ip>
- Accept the browser’s warning (self-signed certificate).
- Log in with the credentials you set during deployment (securely preserved on your server).
Advanced Features
These are the practical upgrades that matter for a private search proxy. They cut first-byte time, keep responses steady during traffic spikes, and give you a safe rollback if an update misbehaves.
- Dedicated vCPUs & DDR5 RAM – prevent noisy-neighbor stalls on concurrent queries.
- Pure NVMe storage – > 500k IOPS for favicon cache, log rotation, and result pages.
- 10 Gbps network port – handles dozens of simultaneous users without 429 errors.
- On-demand snapshots & rollback – freeze before major updates; revert in seconds.
- Hourly billing – clone staging instances for pennies, delete them when testing ends.
Ease of use
The dashboard handles power actions, snapshots, and region moves. Point DNS to the static IP when you’re ready, or use the IP directly at https://<server-ip> for immediate access.
SEO-Friendly (Performance Focus)
A faster, tracker-free SERP improves user experience on privacy portals, school intranets, and corporate dashboards—indirectly boosting Core Web Vitals for any public pages that embed Whoogle results. NVMe I/O plus a 10 Gbps uplink keep TTFB consistently low.
Full Website Control
Root privileges unlock header tweaks, firewall rules, backup scheduling, and update cadence. KVM isolation protects containers and processes from neighbor workloads, while dedicated IPs keep HTTPS valid and CAPTCHAs rare.
Powerful Tools
These utilities are preinstalled or one click away. They cover HTTPS, hardening, updates, metrics, and backups so you can focus on the search experience instead of server chores.
- Preinstalled Whoogle Search
- Optional hardening and monitoring add-ons (e.g., Fail2Ban, node_exporter)
- Remote backup recipes to S3/GCS
- Cron templates for nightly log pruning
All utilities benefit from the predictable memory and I/O profile of a Whoogle VPS, so heavy query bursts and favicon caching never time out.
Global Reach
Serve users from the data center that’s nearest to them. Cloudzy operates 10 points of presence across three continents:
- North America – New York City, Dallas, Miami, Utah, Las Vegas
- Europe – London, Amsterdam, Frankfurt, Zurich (Switzerland)
- Asia-Pacific – Singapore
Every location delivers the same 10 Gbps uplink, Tier-1 carrier mix, and 99.95% uptime SLA; the only variable is distance.
Application Details
- OS: Ubuntu 24.04 LTS
- Runtime: Docker Engine (latest), Docker Compose Plugin
- Applications: Whoogle Search (latest stable from benbusby/whoogle-search), Nginx (Alpine from Docker Hub)
- Init System: systemd
- Provisioning: cloud-init
- Minimum RAM: 1 GB
- IP Types: IPv6, IPv4
Deploy Whoogle Search Now: your private, ad-free search is ready in minutes.
Important: Configuration & Domain Responsibilities
You get full SSH/root access on every OCA. That power also means your changes can break the app. Please read this before tweaking configs.
- You manage the domain. We don’t sell or host domains/DNS. If the app needs a domain, you must point your domain to the server (A/AAAA/CNAME, and MX/TXT if relevant). SSL issuance and many dashboards depend on this being correct.
- Changing the domain/hostname after install isn’t trivial. Many OCAs write the domain into configs (.env, reverse proxy, app URLs). If you change it, also update:
- Reverse proxy (Nginx/Caddy) and TLS certificates
- App “external URL”/base URL and callback/webhook URLs
- Any hard-coded links in the app or add-ons
- Credentials matter. Renaming the default admin, rotating passwords, or changing service ports without updating the app config can lock you out or stop services. Keep credentials safe and in sync across the app, proxy, and any integrations.
- Nameserver changes can cause downtime. Moving your domain to new nameservers or editing NS records triggers propagation delays. Plan changes, lower TTL ahead of time, and verify A/AAAA records before switching.
- Firewall/port edits can break access. If you change SSH, HTTP/HTTPS, RDP, or app ports, update firewalls (UFW/CSF/security groups) and reverse-proxy rules accordingly.
- Email (SMTP) ports are restricted by default. Outbound mail ports (e.g., 25/465/587) may be closed to prevent abuse. If your OCA must send email, request SMTP Access from support or use a transactional email provider (SendGrid/Mailgun/SES) via API or approved SMTP.
- Email & allowlists. If the app sends mail or receives webhooks, changing IPs/hostnames may affect deliverability or allowlists. Update SPF/DKIM/DMARC and any IP allowlists.
- Before any big change: take a snapshot. Use the panel’s snapshot/backup first. If a plugin, update, or config edit backfires, you can roll back in minutes.
- Support scope. We provide the server and the preinstalled OCA image. Ongoing application-level configuration (domains, DNS, app settings, plugins, custom code) is the user’s responsibility.
Quick rule of thumb: if you touch domain, ports, passwords, hostnames, or proxy/SSL configs, expect to update the app’s settings too, and snapshot first.
- Open your browser and go to
https://<server-ip> - Accept the browser’s warning (self-signed certificate)
- Log in with the credentials you set during deployment (securely preserved on your server)