Runtime and processes
Check a Redis workload where persistence mode, memory growth, eviction behavior, authentication, network exposure, backups, and restart semantics are chosen explicitly.
Redis server VPS
Choose memory for your Redis dataset and operating overhead. Configure private access, eviction behaviour and persistence to suit the application.
Hosting options
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check a Redis workload where persistence mode, memory growth, eviction behavior, authentication, network exposure, backups, and restart semantics are chosen explicitly.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
Redis holds its data set in memory, so the sizing rule is direct: the server needs RAM for your data, plus overhead for fragmentation, replication buffers, and the copy on write snapshot process. Set maxmemory to a value below total RAM, and choose an eviction policy that matches whether Redis is a cache or a primary store.
Persistence is a deliberate trade: RDB snapshots are compact and periodic, AOF logs writes for tighter durability at higher disk cost, and many cache deployments run with neither. A snapshot fork on a memory tight server can trigger the kernel out of memory killer, so leave headroom and watch used memory against the limit in INFO output.
Use an LRU style policy for cache workloads and noeviction when Redis holds data you cannot lose. The wrong policy either deletes needed keys or fails writes at the limit.
Bind Redis to localhost or a private interface and require a password for any wider access. An exposed Redis port is a well known entry point for compromise.
During an RDB save, copy on write can grow memory sharply on a write heavy instance. Keep free memory available or snapshots will fail or trigger the OOM killer.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.