VDS is an apartment with thick neighbor walls: root is yours, patching is per our agreement. Recommended when custom software, high isolation, or custom rules are needed. Webify sets up resource and network; doesn't leave unlimited "you handle it," writes the boundary.
You choose the resources and software.
Process
- 01
Resource
CPU, RAM, disk, and operating system are selected.
- 02
Network
Firewall, SSH/RDP, and backup channel are opened.
- 03
Software
Desired stack (web, data, queue) is installed or your image is placed.
- 04
Delivery
Access, backup, and patching model are delivered in writing.
What’s included
- Root access and custom software
- Scalable resource
- Linux / Windows options
- Network and security rules
Who it’s for
- Those running custom software
- Those wanting high isolation
- Agency / multi-client hosters
- Peaks where corporate hosting isn't enough
When is VDS needed?
Root, cron, queue worker, custom database, or banned plugin list exceed shared panel. Then VDS is discussed. Getting VDS "to be cooler" is a risk of unpatched open door.
Windows, Active software, or MSSQL need isn't solved on shared Linux. OS is chosen from the start; changing later is reinstallation.
Agencies consider container or account isolation instead of separate VDS for each client. Model is cost and security balance.
Patching and backup can be your job
In unmanaged VDS, updates are yours. In managed model, patching window is ours, application is yours. Mixed responsibility produces breaches; separated in one sentence in quote.
Snapshot and external backup are different. If disk corrupts, snapshot may not be enough. 3-2-1 rule (copy, medium, location) is explained.
SSH key replaces password. Shared root password shouldn't be in Slack. Personal account is opened.
Network, DDoS, and cost
Security group (port) isn't left open by default. If RDP/SSH is open to the world, scanning starts within minutes. IP restriction or VPN is discussed.
DDoS mitigation depends on infrastructure provider. VDS isn't a miracle shield; upper layer may be needed.
Resource scales vertically (add RAM) or horizontally (second machine). Application architecture determines this, not sales slide.
Migration
Migration from old VDS is with rsync / image. When IP changes, DNS and license locks (software) shouldn't be forgotten.
Static IP is needed for email and some integrations. When moving from shared IP to VDS, SPF/DKIM is rewritten.
Cost is cheap unmanaged VDS + your night. Managed difference is human hours.
Managed and unmanaged boundary
Unmanaged VDS looks cheap; patching, security group, and backup are yours. If forgotten SSH is open to the world, scanning starts within minutes. In managed model, patching window is ours, application business rule is yours. Mixed responsibility produces breaches; separated in one sentence in quote.
Root password or key is yours. Emergency access procedure is written; shared root in Slack is both security and exit issue. Personal account is opened, shared superuser is closed.
VDS is generally too much load for a small corporate showcase. Corporate or WordPress hosting requires less operation. Getting root "to be cooler" is a risk of unpatched open door.
Network, backup, and monitoring
Security group isn't left open by default. SSH/RDP IP restriction or VPN is discussed. DDoS mitigation depends on infrastructure provider; VDS isn't a miracle shield, upper layer may be needed.
Snapshot is instant disk image, external backup is separate copy. If disk corrupts, snapshot alone may not be enough. 3-2-1 rule (copy, medium, location) is explained. When contract ends, disk isn't your property; get the archive, deletion procedure is written.
In managed model, basic uptime is monitored. Application performance (slow query, queue buildup) is APM, can be separate item. Resource scales vertically (add RAM) or horizontally (second machine); architecture determines this.
Operating system, panel, and migration
Web and PHP are generally Linux; MSSQL and some corporate stacks require Windows. Changing later is reinstallation. ISO or your image is placed per provider rule.
If you want cPanel or similar panel, license is a separate line. Panel doesn't replace root; it's a convenience layer. Keeping email on VDS is possible but there's reputation and blacklist risk—separate corporate email is calmer for most brands.
When migrating from old VDS, when IP changes, DNS, license locks, and SPF/DKIM are rewritten. Webify sets up resource and network; doesn't leave "unlimited you handle it." 0850 885 28 44 is the same team.
