Self-hosting is the recommended way to run UXWizz: your analytics stay on infrastructure
you control, while built-in tools handle much of the routine application maintenance.
Update UXWizz with one click and use scheduled tasks to enforce storage limits and clean old data automatically.
For most teams, self-hosting offers the best balance: direct control over the server and database without manually maintaining every part of the analytics application. UXWizz includes a guided Linux installer, a validated updater with progress and rollback protection, and scheduled maintenance tasks. Managed hosting remains available when you also want to outsource the underlying server administration.
Operational differences between the two UXWizz hosting options
Decision factor
Self-hosted UXWizz
Managed dedicated VPS
Infrastructure ownership
Your organization chooses and controls the server, region, database access, and hosting provider.
UXWizz arranges a separate VPS for your installation and operates it as a managed service.
Maintenance
UXWizz application updates are installed with one click. Scheduled tasks can enforce storage limits and delete old data. Your team still maintains the operating system, PHP/MySQL stack, TLS, backups, and server capacity.
Built-in UXWizz maintenance plus routine server monitoring and administration are included in the managed service.
Backups
Your team defines, tests, secures, and retains database and application backups.
Backups are included; confirm the required schedule and retention when requesting a quote.
Pricing basis
UXWizz license plus your chosen infrastructure and internal operations.
UXWizz license, server cost, and management fee; the quote depends on expected traffic and workload.
Best fit
Most teams that want direct data-location and infrastructure control and can maintain a standard PHP/MySQL server.
Teams wanting a dedicated UXWizz instance while outsourcing routine server work.
Start with self-hosting when your team already operates a website or PHP/MySQL server. Managed hosting is available by request when you want UXWizz to operate the server too.
Requirements and deployment
What self-hosting UXWizz requires
UXWizz requires 64-bit PHP 8.3 or newer with PDO MySQL and ZIP, plus MySQL 8.0 or MariaDB 10.7 or newer. The database can run on the same server or separately. Install through the guided Linux setup, Docker, compatible shared hosting or cPanel, or the WordPress plugin path.
Traffic is only one sizing factor. Total stored sessions, enabled heatmaps, recording mode, retention, and MySQL configuration also affect CPU, memory, and disk use. The full session-recording mode uses more resources than the recommended default recorder.
Practical server starting points
Starting specifications by monthly website traffic
Monthly visits
Suggested resources
Stored-session checkpoint
Under 10,000
1 vCPU, 1 GB RAM, and 10 GB disk. Suitable shared hosting or a small VPS can work.
Consider more resources above roughly 500,000 stored sessions.
Under 50,000
2 vCPU, 2 GB RAM, and 25 GB disk.
Consider more resources above roughly 1 million stored sessions.
Under 200,000
4 vCPU, 8 GB RAM, and 50 GB disk.
Consider more resources above roughly 5 million stored sessions.
Under 1 million
8 vCPU, 32 GB RAM, and 320 GB disk.
Consider more resources above roughly 10 million stored sessions.
1 million or more
Use a powerful dedicated server.
Consider moving MySQL or MariaDB to a separate server instance.
These are starting guidelines, not fixed limits. Monitor actual CPU, memory, database, and disk use, then scale for your traffic mix and enabled recording features.
1. Size the environment
Estimate monthly traffic, total stored sessions, heatmap and recording use, retention needs, and the number of tracked sites. Start from the guidelines above, then monitor real database and server load.
2. Install the platform
For a new Linux server, run curl -fsSL https://www.uxwizz.com/install.sh | sudo bash and follow the prompts. You can also use Docker, compatible shared hosting or cPanel, or WordPress. Complete setup, then add the tracking code to the websites you own.
3. Configure data handling
Choose server location, access controls, backups, retention, storage limits, sensitive-field masking, ignored pages/elements, and the tracking behavior appropriate for your use case.
4. Operate and scale
Enable scheduled tasks so UXWizz automatically enforces storage limits and removes old data. Install releases through the authenticated updater and review its progress. Your team continues to monitor backups, server health, database performance, and capacity as traffic or retention grows.
What UXWizz handles
Guided Linux installation with secure defaults and automatic requirement checks.
Validated application updates with progress, retries, migration checks, and rollback protection.
Scheduled enforcement of configured storage limits.
Automatic cleanup of old analytics and session-recording data.
What remains under your control
Server security, PHP/MySQL maintenance, TLS, and access controls.
Backup policy, monitoring, recovery, and infrastructure capacity.
The storage and retention limits that scheduled tasks enforce.
For Agency/MultiDB, backups for every analytics database and the MultiDB mapping files.
How database use grows
Heatmaps and session recordings usually account for the largest database usage. Quantitative statistics, page visits, and events are smaller and can often be retained longer than old qualitative replay and heatmap data.
How to keep storage predictable
Track only the features you need, prefer the default recording mode when it is sufficient, set storage and retention limits, and let scheduled cleanup remove old recordings and heatmaps while retaining useful aggregate statistics.
Cristian Buleandră — Founder