SplitQuest Enterprise: Self-hosted Deployment Full PDF Automation. Total Data Sovereignty.
Integrate SplitQuest's smart splitting, searching, and renaming into your secure infrastructure. Our Self-hosted solution offers the same speed as the cloud version while ensuring your data remains secure.
Your Data, Your Infrastructure, Your Rule
SplitQuest Self-hosted is engineered for high-compliance environments where data residency is non-negotiable.
Total Data Sovereignty
Maintain 100% control. Files are processed locally on your hardware or your private cloud solution.
Air-Gapped Ready
Designed for secure environments with restricted or zero internet connectivity.
Enterprise Performance
Get the full power of SplitQuest's document processing capabilities running on your own hardware. Scale processing power based on your workload and performance requirements.
Regulatory Compliance
Simplify HIPAA, GDPR, and SOC2 audits by keeping sensitive document contents within your internal network.
How it Works
SplitQuest Self-hosted is delivered as a secure, containerized application or standalone binary designed to integrate seamlessly with modern IT stacks.
Deployment
The application resides entirely on your local servers or private cloud (AWS, Azure, GCP).
Security-First Architecture
SplitQuest does not "phone home" with your document data. All file processing and metadata extraction remain strictly internal.
Licensed Activation
Access is governed by a dedicated Enterprise License Key, issued only to contracted partners.
Request Self-hosted Access
To maintain the highest security standards and ensure version integrity, the SplitQuest Self-hosted installer is not available for public download. Deployment access is restricted to authorized clients with an active service agreement.
Already a Client?
If you have an active Enterprise contract and require a fresh deployment link or an update, please contact your Account Manager or reach out to our technical team to receive your secure, time-limited installation token.
New to SplitQuest?
Not yet a client? Schedule a demo and request self-hosted option. To discuss your specific infrastructure needs and receive a formal quote for an Self-hosted license, please reach out to our Client engagement team.
Installation Guide
Select your server platform for platform-specific installation instructions:
Supported Distributions: Ubuntu 22.04+, CentOS 7+, RHEL 8+, Debian 10+, Amazon Linux 2
Why Linux: Native Docker support, better resource efficiency, robust security, and enterprise-grade stability.
Supported Versions: Windows Server 2019+, Windows 10/11 Pro (for development)
Requirements: Docker Desktop with WSL2 backend, Windows Subsystem for Linux 2 (WSL2)
Supported Versions: macOS 10.15+ (Catalina and later), both Intel and Apple Silicon (M1/M2/M3)
Requirements: Docker Desktop for Mac, Xcode Command Line Tools
Linux Distributions
Linux Installation
# Install / Reinstall Docker (Ubuntu / Debian)
sudo apt-get remove -y docker docker-engine docker.io containerd runc || true
sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get install -y ca-certificates curl gnupg lsb-release
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | \
sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
echo "deb [arch=\"$(dpkg --print-architecture)\" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \"$(. /etc/os-release && echo \"$VERSION_CODENAME\")\" stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update
sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
# Add current user to docker group (idempotent)
if ! groups $USER | grep -q docker; then
sudo gpasswd -a $USER docker
fi
# Activate new group in current shell (may require re-login in some cases)
newgrp docker <<'EOF'
echo "Docker group activated in subshell"
EOF
# Final update & verification
sudo apt-get update -y
docker --version
docker compose version || docker compose --version
# Notes for other distributions:
# RHEL / CentOS / Rocky / Alma:
# sudo yum remove docker docker-client docker-client-latest docker-common docker-latest \
# docker-latest-logrotate docker-logrotate docker-engine || true
# sudo yum install -y yum-utils
# sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
# sudo yum install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
# sudo systemctl enable --now docker
# sudo usermod -aG docker $USER
# Amazon Linux 2:
# sudo amazon-linux-extras enable docker
# sudo yum clean metadata
# sudo yum install -y docker
# sudo systemctl enable --now docker
# sudo usermod -aG docker $USER
Windows Requirements (WSL2 Only)
Windows Setup Steps (WSL2 Required)
# Run in PowerShell as Administrator (Windows Server included) wsl --install # or for older versions dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart # Restart computer, then set WSL2 as default wsl --set-default-version 2 # Install a Linux distribution (Ubuntu recommended) wsl --install -d Ubuntu
# Download from: https://docker.com/products/docker-desktop # IMPORTANT: During installation, select "Use WSL 2 instead of Hyper-V" # After installation, go to Docker Desktop > Settings > Resources > WSL Integration # Enable integration with your Ubuntu/Linux distribution # Verify installation in WSL2 terminal (NOT PowerShell): # Open Ubuntu from Start Menu or type: wsl docker --version docker compose --version # Test Docker works in WSL2 docker run hello-world
macOS Requirements
macOS Setup Steps
# In Terminal: xcode-select --install # Verify installation: xcode-select -p
# Download from: https://docker.com/products/docker-desktop # Or install via Homebrew: brew install --cask docker # Start Docker Desktop from Applications # Verify installation: docker --version docker compose --version
# In Docker Desktop > Settings > Resources: # CPU: Allocate 2+ cores # Memory: Allocate 4GB+ RAM # Disk: Ensure 10GB+ available
Universal Hardware Requirements
CPU Requirements
Minimum: 2 cores (64-bit)
Recommended: 4+ cores
Production: 8+ cores
Memory Requirements
Minimum: 4GB RAM
Recommended: 8GB RAM
Production: 16GB+ RAM
Storage Requirements
Application: 5GB
Documents: 10GB+
Total: 20GB+ recommended
Verify Prerequisites by Platform:
# Check Docker installation docker --version docker compose --version # Verify system resources df -h # Check disk space (need 20GB+) free -h # Check available memory (need 4GB+) nproc # Check CPU cores (need 2+) # Test Docker is working docker run hello-world # Check port availability sudo netstat -tulpn | grep -E ':80|:443' # or sudo ss -tulpn | grep -E ':80|:443'
# All commands should be run in WSL2 terminal (Ubuntu/Debian) # Check Docker installation docker --version docker compose --version # Verify system resources (in WSL2 terminal) df -h # Check disk space (need 20GB+) free -h # Check available memory (need 4GB+) nproc # Check CPU cores (need 2+) # Test Docker is working docker run hello-world # Check port availability sudo netstat -tulpn | grep -E ':80|:443' # or sudo ss -tulpn | grep -E ':80|:443' # Note: WSL2 status can be checked in PowerShell if needed: # wsl --list --verbose
# Check Docker installation docker --version docker compose --version # Verify system resources df -h # Check disk space (need 20GB+) sysctl hw.memsize # Check total memory sysctl hw.ncpu # Check CPU cores # Check Xcode Command Line Tools xcode-select -p # Test Docker is working docker run hello-world # Check port availability sudo lsof -i :80 sudo lsof -i :443 # Check Docker Desktop resource allocation # Go to Docker Desktop > Settings > Resources
Recommended: One-command install script for Linux
This command downloads the install script and automatically downloads/extracts the SplitQuest package:
curl -fsSL https://splitquest-onprem-releases.s3.amazonaws.com/onprem/install.sh | bash
Alternative: Manual download for Linux
# Download package and checksum wget https://splitquest-onprem-releases.s3.amazonaws.com/onprem/splitquest-onprem-latest.tar.gz wget https://splitquest-onprem-releases.s3.amazonaws.com/onprem/splitquest-onprem-latest.tar.gz.sha256 # Verify integrity (important for security) sha256sum -c splitquest-onprem-latest.tar.gz.sha256 # Extract if verification passes tar -xzf splitquest-onprem-latest.tar.gz cd splitquest-onprem-v*/
Recommended: One-command install (WSL2 Terminal)
Open WSL2 terminal (Ubuntu, Debian) and run:
curl -fsSL https://splitquest-onprem-releases.s3.amazonaws.com/onprem/install.sh | bash
Alternative: Manual Download in WSL2
Download and extract directly in WSL2 terminal:
# Download and extract in WSL2 wget https://splitquest-onprem-releases.s3.amazonaws.com/onprem/splitquest-onprem-latest.tar.gz wget https://splitquest-onprem-releases.s3.amazonaws.com/onprem/splitquest-onprem-latest.tar.gz.sha256 # Verify integrity (important for security) sha256sum -c splitquest-onprem-latest.tar.gz.sha256 # Extract if verification passes tar -xzf splitquest-onprem-latest.tar.gz cd splitquest-onprem-v*/
Recommended: One-command install script for macOS
This command downloads the install script and automatically downloads/extracts the SplitQuest package:
curl -fsSL https://splitquest-onprem-releases.s3.amazonaws.com/onprem/install.sh | bash
Alternative: Homebrew-style download for macOS
Using curl with verification:
# Download and extract in one step curl -fsSL https://splitquest-onprem-releases.s3.amazonaws.com/onprem/splitquest-onprem-latest.tar.gz | tar -xz cd splitquest-onprem-v*/
Manual download for macOS
# Download with curl curl -O https://splitquest-onprem-releases.s3.amazonaws.com/onprem/splitquest-onprem-latest.tar.gz curl -O https://splitquest-onprem-releases.s3.amazonaws.com/onprem/splitquest-onprem-latest.tar.gz.sha256 # Verify integrity (optional but recommended) shasum -a 256 -c splitquest-onprem-latest.tar.gz.sha256 # Extract tar -xzf splitquest-onprem-latest.tar.gz cd splitquest-onprem-v*/
install.sh, setup-ssl.sh,
and .env.template.
Configure your deployment by editing the
.env
file with your specific settings:
Copy template and start configuration:
# Copy the template to create your configuration cp .env.template .env # Edit the configuration file nano .env # or use your preferred editor
Required Configuration Sections:
# Your SplitQuest license key (required) LICENSE_KEY=YOUR_LICENSE_KEY_HERE
# MySQL Database Configuration MYSQL_DATABASE=splitquest_onprem MYSQL_USER=splitquest MYSQL_PASSWORD=your_secure_mysql_password_here MYSQL_HOST=mysql MYSQL_PORT=3306 MYSQL_ROOT_PASSWORD=your_secure_root_password_here
Important: Change the default passwords to secure, unique values for production use.
Choose between local storage (recommended for self-hosted) or S3-compatible storage:
# Local Storage (Recommended for self-hosted) STORAGE_TYPE=local LOCAL_STORAGE_PATH=/app/storage MAX_FILE_SIZE_MB=1000 STORAGE_CLEANUP_ENABLED=true STORAGE_CLEANUP_DAYS=30
# S3 Storage Configuration STORAGE_TYPE=s3 AWS_BUCKET_NAME=your-s3-bucket-name AWS_ACCESS_KEY=your-s3-access-key AWS_SECRET_KEY=your-s3-secret-key AWS_REGION=us-east-1
# Django Secret Key (generate a unique one for production) DJANGO_SECRET_KEY=your-long-random-secret-key-here # Internal encryption key (auto-generated if not set) ENCRYPTION_KEY=auto-generated-on-startup # Allowed hosts (use * for self-hosted flexibility) ALLOWED_HOSTS=*
Generate secure keys using:
python -c "from django.core.management.utils
import get_random_secret_key;
print(get_random_secret_key())"
# Custom domain (optional) - leave blank for IP/hostname access DOMAIN= # Email for Let's Encrypt SSL (required if using custom domain) LETSENCRYPT_EMAIL= # Use staging certificates for testing (true/false) LETSENCRYPT_STAGING=false
./setup-ssl.sh.
Once your
.env
file is configured, run the main installer:
Platform-Specific Installation Commands:
Start the installation on Linux:
# Make script executable and run chmod +x install.sh ./install.sh
Start the installation on Windows (WSL2):
# In WSL2 terminal (Ubuntu/Debian): cd splitquest-onprem-v*/ chmod +x install.sh ./install.sh
Start the installation on macOS:
# In Terminal: cd splitquest-onprem-v*/ chmod +x install.sh ./install.sh
- ✓ Validate your configuration and system requirements
- ✓ Check Docker installation and requirements
- ✓ Pull Docker images and set up containers
- ✓ Start all services (web, celery, redis, mysql, nginx)
- ✓ Wait for services to be ready and test connectivity
- ✓ Make the application available at http://localhost
Installation Output:
You'll see output similar to:
==================================================================
SplitQuest Self-hosted Installation
Version 1.0.1
==================================================================
ℹ️ Checking configuration file...
✓ Configuration file validated successfully
ℹ️ Domain:
ℹ️ Email:
ℹ️ Performing pre-flight checks...
✓ Docker is installed
✓ Docker Compose is installed
✓ Docker daemon is running
✓ Sufficient disk space available
✓ Memory check completed
ℹ️ Starting SplitQuest services with Docker Compose...
✓ Services started successfully
ℹ️ Waiting for services to be ready...
✓ All services are ready
==================================================================
🎉 SplitQuest Self-hosted Installation Complete! 🎉
==================================================================
✓ Application is running at: http://localhost
✓ All services are healthy and ready
✓ You can now access the SplitQuest web interface
Next Steps:
• Access the application at http://localhost
• Optional: Set up SSL/HTTPS with ./setup-ssl.sh
• Check logs: docker compose -f docker-compose.onprem.yml logs
Access Your Application:
mdi-web
Web Interface
Access SplitQuest via web browser:
http://localhost
http://your-server-ip
http://your-domain.com
mdi-monitor
Service Management
Common management commands:
# Check service status docker compose -f docker-compose.onprem.yml ps # View logs docker compose -f docker-compose.onprem.yml logs -f # Restart services docker compose -f docker-compose.onprem.yml restart # Stop services docker compose -f docker-compose.onprem.yml down
Prerequisites for SSL Setup:
.env filePlatform-Specific SSL Setup Commands:
Testing/Staging (Linux):
Use staging certificates to test your setup without hitting rate limits.
./setup-ssl.sh --staging
Production (Linux):
Use real Let's Encrypt certificates for production deployment.
./setup-ssl.sh --production
Testing/Staging (Windows WSL2):
Use staging certificates to test your setup without hitting rate limits.
# In WSL2 terminal: cd splitquest-onprem-v*/ chmod +x setup-ssl.sh ./setup-ssl.sh --staging
Production (Windows WSL2):
Use real Let's Encrypt certificates for production deployment.
# In WSL2 terminal: cd splitquest-onprem-v*/ chmod +x setup-ssl.sh ./setup-ssl.sh --production
Testing/Staging (macOS):
Use staging certificates to test your setup without hitting rate limits.
# In Terminal: cd splitquest-onprem-v*/ chmod +x setup-ssl.sh ./setup-ssl.sh --staging
Production (macOS):
Use real Let's Encrypt certificates for production deployment.
# In Terminal: cd splitquest-onprem-v*/ chmod +x setup-ssl.sh ./setup-ssl.sh --production
- ✓ Request Let's Encrypt SSL certificates automatically
- ✓ Configure nginx for HTTPS with auto-redirect from HTTP
- ✓ Set up automatic certificate renewal
- ✓ Make your site available at https://your-domain.com
- ✓ Automatically enable secure cookie and CSRF settings
After SSL Setup:
Access URLs:
https://your-domain.com
http://your-domain.com
Security Features:
FAQs
Find quick answers to common questions about our services and support options.
mdi-download
Installation Questions
For optimal performance, we recommend:
- CPU: 2+ cores (64-bit), 4+ cores recommended for production
- RAM: 4GB minimum, 8GB+ recommended for heavy document processing
- Storage: 10GB+ available space (5GB for application, 5GB+ for documents)
- OS: Linux (Ubuntu 22.04+, CentOS 7+, RHEL 8+), Windows 10+ with WSL2, macOS 10.15+
- Docker: Engine 20.10+ and Compose 2.0+
- Network: Ports 80 and 443 available, internet connectivity for initial setup
Verification commands:
# Check system resources df -h # Should show 10GB+ available free -h # Should show 4GB+ available docker --version # Should be 20.10+ docker compose --version # Should be 2.0+
Yes, but ONLY through WSL2! SplitQuest Self-hosted does not support direct Windows Server installation. You must use WSL2 (Windows Subsystem for Linux) for all Windows deployments.
Required Setup Steps:
-
Install Windows Subsystem for Linux 2
(WSL2):
wsl --install -d Ubuntu - Install Docker Desktop with WSL2 backend
- Enable WSL2 integration in Docker Desktop settings
- Run ALL installation commands from a WSL2 terminal (never PowerShell/CMD)
Yes! SplitQuest Self-hosted runs excellently on macOS using Docker Desktop for Mac. Requirements:
- macOS 10.15+ (Catalina or later) - works on both Intel and Apple Silicon (M1/M2/M3)
-
Install Xcode Command Line Tools:
xcode-select --install - Install Docker Desktop for Mac (download from docker.com or use Homebrew)
- Configure adequate resources in Docker Desktop settings (4GB+ RAM, 2+ CPU cores)
Platform performance ranking for SplitQuest Self-hosted:
1. Linux (Best)
Native Docker support, optimal resource efficiency, enterprise stability, best for production deployments.
2. macOS (Excellent)
Great for development and testing, excellent performance on Apple Silicon, easy setup and management.
3. Windows via WSL2 (Good)
Requires WSL2 - No direct Windows Server support. Runs well through WSL2, slightly higher resource overhead due to virtualization layer.
After installation, verify everything is working:
# Check if containers are running (should show all services as 'Up') docker compose -f docker-compose.onprem.yml ps # View application logs (should show successful startup) docker compose -f docker-compose.onprem.yml logs splitquest_web | tail -20 # Test web interface (should return HTTP 200) curl -I http://localhost/health # Test database connectivity docker compose -f docker-compose.onprem.yml exec mysql mysql -u splitquest -p splitquest_onprem -e "SELECT 1;"
Expected results:
- All containers should show status 'Up'
- Health check should return HTTP 200 OK
- Web interface should be accessible at http://localhost
- Database connection should succeed
If issues occur: Check the
installation logs with
docker compose -f docker-compose.onprem.yml
logs
mdi-license
Licensing Questions
To obtain an self-hosted license:
- Contact our sales team at [email protected]
- Provide your organization details and use case
- Receive a quote based on your requirements
- After purchase, you'll receive your license key
-
Configure this in your
.envfile
Yes! We offer a 30-day trial license for evaluation purposes. Contact our sales team to request a trial license. The trial includes:
- Full feature access
- Processing up to 1,000 documents
- Technical support during evaluation
- Migration assistance if you decide to purchase
When your license expires:
- The application will display warnings 30 days before expiration
- Processing capabilities will be limited after expiration
- Existing data and documents remain accessible
- Contact sales to renew your license before expiration
We recommend setting up license renewal alerts in your calendar.
mdi-cog
Configuration Questions
SplitQuest Self-hosted uses MySQL as the database, which is pre-configured in the Docker deployment. The MySQL database is automatically set up when you run the installation script.
Default MySQL Configuration:
# MySQL Database Configuration in .env MYSQL_DATABASE=splitquest_onprem MYSQL_USER=splitquest MYSQL_PASSWORD=your_secure_mysql_password_here MYSQL_HOST=mysql MYSQL_PORT=3306 MYSQL_ROOT_PASSWORD=your_secure_root_password_here
Why MySQL?
- Proven stability: MySQL is battle-tested for production workloads
- Excellent performance: Optimized for the SplitQuest document processing workflow
- Easy management: Simple backup, restore, and maintenance procedures
- Wide compatibility: Works seamlessly across all supported platforms (Linux, macOS, Windows with WSL2)
.env file to secure, unique values
before deploying to production.
SplitQuest provides automated SSL/HTTPS setup using Let's Encrypt certificates. To configure HTTPS:
-
Configure your domain in the
.envfile:# In your .env file DOMAIN=your-domain.com [email protected] LETSENCRYPT_STAGING=false # Set to true for testing
- Ensure DNS is configured: Point your domain's A record to your server's IP address
-
Run the SSL setup script:
./setup-ssl.sh --production
The script will automatically:
- Request SSL certificates from Let's Encrypt
- Configure nginx for HTTPS
- Set up automatic certificate renewal
- Enable HTTP to HTTPS redirection
./setup-ssl.sh --staging to avoid
Let's Encrypt rate limits.
Yes! Configure custom storage paths in your
.env file:
# Storage Configuration in .env STORAGE_TYPE=local LOCAL_STORAGE_PATH=/custom/path/to/storage # Maximum file size in MB MAX_FILE_SIZE_MB=1000 # Storage cleanup settings STORAGE_CLEANUP_ENABLED=true STORAGE_CLEANUP_DAYS=30
Alternative: S3 Storage
# S3 Storage Configuration in .env STORAGE_TYPE=s3 AWS_BUCKET_NAME=your-bucket-name AWS_ACCESS_KEY=your-access-key AWS_SECRET_KEY=your-secret-key AWS_REGION=us-east-1
mdi-wrench
Troubleshooting Questions
Follow this troubleshooting checklist:
-
Check Docker status:
docker --version && docker compose --version -
Verify configuration file:
cat .env | grep -E "LICENSE_KEY|MYSQL_PASSWORD" | head -2 -
Check port availability:
netstat -tulpn | grep -E ":80|:443|:3306" -
Review installation logs:
docker compose -f docker-compose.onprem.yml logs --tail=50 -
Check system resources:
df -h && free -h -
Re-run installation: Run
./install.shagain - it includes validation and will show specific errors.
Permission issues vary by platform. Here are platform-specific solutions:
For Linux systems:
-
Add your user to the docker
group:
sudo usermod -aG docker $USER -
Log out and back in, then
verify:
groups | grep docker - Check file permissions on directories
- On SELinux systems (RHEL/CentOS), configure contexts
For Windows with WSL2:
- Ensure Docker Desktop is running with WSL2 integration enabled
-
In WSL2 terminal, add user to docker
group:
sudo usermod -aG docker $USER -
Restart WSL2:
wsl --shutdown(in PowerShell) - Check file permissions between Windows and WSL2 filesystems
For macOS systems:
- Ensure Docker Desktop for Mac is running
- Check Docker Desktop file sharing settings (Preferences > Resources > File Sharing)
-
Verify Docker daemon is
accessible:
docker ps - Check file permissions on macOS filesystem
Platform-specific Docker troubleshooting steps:
Linux Docker troubleshooting:
# Check Docker service status sudo systemctl status docker # Start Docker if not running sudo systemctl start docker sudo systemctl enable docker # Check Docker daemon logs sudo journalctl -fu docker # Verify Docker installation docker version docker info # Check available resources df -h free -h
Windows WSL2 + Docker troubleshooting:
# Check WSL2 status (in PowerShell) wsl --list --verbose # Ensure WSL2 integration is enabled in Docker Desktop # Docker Desktop > Settings > Resources > WSL Integration # Check Docker in WSL2 terminal docker version docker info # Restart Docker Desktop if needed # Right-click Docker Desktop > Restart # Check WSL2 resources wsl --shutdown # Then restart WSL2 terminal
macOS Docker troubleshooting:
# Check Docker Desktop status docker version docker info # Restart Docker Desktop # Docker Desktop > Troubleshoot > Restart # Check resource allocation # Docker Desktop > Settings > Resources # Ensure 4GB+ RAM, 2+ CPU cores allocated # Check Docker Desktop logs # Docker Desktop > Troubleshoot > Get support # Clear Docker cache if needed docker system prune -a
Create regular backups of your SplitQuest data:
-
Database backup:
docker compose -f docker-compose.onprem.yml exec mysql mysqldump -u splitquest -p splitquest_onprem > backup-$(date +%Y%m%d).sql -
Document storage backup:
tar -czf documents-backup-$(date +%Y%m%d).tar.gz ./data/documents/ ./data/uploads/ -
Configuration backup:
cp .env config-backup-$(date +%Y%m%d).env -
Complete backup script:
#!/bin/bash DATE=$(date +%Y%m%d) docker compose -f docker-compose.onprem.yml exec mysql mysqldump -u splitquest -p splitquest_onprem > backup-$DATE.sql tar -czf splitquest-backup-$DATE.tar.gz .env docker-compose.onprem.yml ./data/ backup-$DATE.sql
Tip: Set up automated backups using cron jobs for regular data protection. Store backups in a separate location from your SplitQuest installation.
mdi-alert-circle
Common Issues
mdi-help-circle
Get Support
Need help with your installation? Our team is here to assist you.
