Filerun Canceled My Lifetime License After I Requested A Receipt

Filerun Canceled My Lifetime License After I Requested A Receipt

Introduction

I recently encountered a situation that many self-hosted enthusiasts and homelabbers may find familiar. A user on a popular DevOps subreddit shared their experience with FileRun, a self-hosted file management solution. After purchasing a personal license for €49 on September 11, 2026, they anticipated seamless usage of the software they had come to rely on. However, when they reached out to FileRun Support requesting an invoice or proof of purchase for their records, the response they received was less than straightforward.

The support team’s reply began with: “If we provide you one, we will convert the licens…” - a response that was truncated but clearly indicated a significant change to their licensing model. This situation raises important questions about license management, vendor relationships, and the vulnerabilities of depending on commercial software in homelab environments.

As DevOps engineers and sysadmins who often build careers around self-hosted solutions, we understand that the appeal of tools like FileRun extends far beyond their feature sets. We value the control, privacy, and independence that self-hosted infrastructure provides. When a vendor alters terms, converts licensing models, or creates uncertainty around existing purchases, it directly impacts our infrastructure planning and risk management strategies.

This experience serves as a catalyst for a deeper exploration of FileRun as a technology platform. Whether you’re currently using FileRun, considering it for your homelab, or simply interested in the broader implications of commercial self-hosted software licensing, this comprehensive guide will provide the technical context you need to make informed decisions.

We’ll examine FileRun’s architecture, deployment options, configuration patterns, and operational considerations from a DevOps perspective. More importantly, we’ll discuss the infrastructure implications of license management, vendor communication, and the practical realities of maintaining self-hosted services when business terms shift unexpectedly.

Understanding the Topic: FileRun as a Self-Hosted File Management Solution

What Is FileRun?

FileRun is a self-hosted web-based file manager and online storage solution written primarily in PHP. Since its inception, it has positioned itself as an alternative to commercial cloud storage services like Dropbox or Google Drive, but with the critical distinction that all data resides on your own infrastructure. For DevOps practitioners and homelab enthusiasts, this architecture offers significant advantages: complete data sovereignty, no arbitrary storage limits imposed by third parties, and the ability to integrate directly with existing infrastructure investments.

The application typically runs on a LAMP (Linux, Apache, MySQL/MariaDB, PHP) or LEMP (Linux, Nginx, MySQL/MariaDB, PHP) stack, though modern deployments increasingly utilize containerization. FileRun connects to a backend database to store metadata about files, user accounts, and sharing permissions, while the actual file content remains on your chosen storage medium—whether that’s local disks, network-attached storage, or cloud storage integrations.

History and Development

FileRun has been under active development for several years, with the core team releasing updates that balance new features with backward compatibility. The platform originated from the need for a more feature-rich self-hosted file manager than solutions like ownCloud or Nextcloud offered at the time, particularly around web-based preview capabilities, advanced sharing controls, and integrated office document viewing.

The commercial licensing model that the Reddit user encountered is characteristic of many PHP-based self-hosted applications. Unlike fully open-source projects governed by permissive licenses (MIT, Apache, GPL), FileRun operates on a dual-model where a free community edition exists alongside paid “personal” and “professional” licenses that unlock additional features. This model funds continued development while providing a entry point for users who want to test the software before committing financially.

Key Features and Capabilities

From a technical standpoint, FileRun offers several features that make it worthy of consideration in a self-hosted infrastructure:

• Web-based interface: Access files from any browser without installing client software
• Advanced permission system: Granular control over who can view, edit, share, or download specific files and folders
• Integrated office document preview: Native viewing of PDFs, images, text files, and Microsoft Office documents within the web interface
• User accounts and groups: Multi-user support with departmental or project-based group assignments
• Link sharing with expiration: Generate shareable links that automatically expire after a set period
• Image and video transformations: On-the-fly resizing, cropping, and format conversion
• Activity logging: Audit trail of file access and modifications
• API access: Programmatic interaction for integration with other systems

Pros and Cons

Advantages:

1. Complete data control: Unlike SaaS alternatives, you determine where data lives, who accesses it, and how it’s protected
2. No vendor lock-in: Standard file formats, database structures that can be inspected and modified
3. Cost-effective for moderate usage: One-time or annual licensing versus per-GB subscription models
4. Rich feature set: Comprehensive feature set that rivals many commercial offerings without requiring multiple integrations
5. Self-contained deployment: Single application with minimal external dependencies beyond a web server and database

Disadvantages and Considerations:

1. Licensing uncertainty: As the Reddit user’s experience demonstrates, commercial terms can change, potentially affecting already-purchased licenses
2. PHP-based architecture: While mature, PHP may not align with all technology stacks preferred by modern DevOps teams
3. Resource requirements: The application can be resource-intensive under heavy concurrent usage
4. Update management: Like any self-hosted application, keeping the software current requires ongoing attention
5. Feature gaps in free edition: Some valuable functionality restricted to paid license tiers

Use Cases and Scenarios

FileRun finds particular utility in several homelab and professional contexts:

• Family media hub: Centralized photo, video, and document access across devices without subscription fees
• Small business document management: Secure file sharing and collaboration without sending data to third-party services
• Developer workspace: Central repository for project documentation, diagrams, and shared resources
• Media serving: Pre-built thumbnail generation and format conversion for photo collections
• Backup consolidation: Single interface for managing and accessing backed-up files from multiple sources

Current State and Future Trends

The self-hosted file management landscape has evolved significantly since FileRun’s early days. Competitors have matured, containerization has become standard, and user expectations have shifted toward more modern, responsive interfaces. FileRun continues to update its feature set, with recent additions focusing on improved mobile responsiveness, enhanced sharing controls, and better integration with external storage backends.

From a market perspective, there’s growing interest in alternative licensing models that provide more predictability for customers. The industry trend toward subscriptionification of previously one-time-purchase software has created heightened awareness among self-hosted communities about the importance of license terms, update policies, and vendor communication channels.

How It Compares to Alternatives

When evaluating FileRun against competitors, several distinctions emerge:

vs. Nextcloud/ownCloud: These platforms are fully open-source under GPL licenses, ensuring that the core functionality remains freely available. However, they often require more extensive setup, have heavier resource footprints, and may lack some of FileRun’s polished document preview features out of the box.

vs. Seafile: Another mature self-hosted file storage solution with strong sync capabilities. Seafile’s architecture differs significantly, focusing on block-level syncing rather than pure web-based access. License models vary, with some features requiring separate purchases.

vs. Nextcloud AIO (All-in-One): Provides a simpler deployment path but may offer less flexibility in component selection and configuration.

vs. Commercial SaaS: The primary trade-off is between convenience and control. SaaS solutions offer zero-maintenance operation but cede data ownership and introduce ongoing costs. FileRun reverses this trade-off.

Real-World Applications and Success Stories

Organizations implementing FileRun typically report success when they approach it as part of a broader infrastructure strategy rather than a standalone solution. A common pattern involves using FileRun as the file management layer atop existing storage infrastructure—perhaps a TrueNAS or OpenMediaVault server—leveraging FileRun’s web interface while benefiting from the underlying storage platform’s features like snapshots, RAID configuration, and backup automation.

Development teams often appreciate FileRun’s API capabilities, integrating it with CI/CD pipelines for artifact management, or using it as a central repository for project documentation that needs to be accessible to distributed team members without relying on corporate cloud services.

Prerequisites

System Requirements

Before deploying FileRun, verify that your infrastructure meets the minimum requirements:

• Operating System: Linux-based system (Ubuntu 20.04+, Debian 11+, CentOS 8+, or similar)
• Web Server: Apache 2.4+/ or Nginx 1.18+ with PHP-FPM support
• PHP Version: 7.3 or 8.0+ (PHP 8.1+ recommended for security updates)
• Database: MySQL 5.7+/MariaDB 10.3+ or PostgreSQL 12+
• PHP Extensions: GD, mysqli/pdo_mysql, mbstring, xml, curl, zip, fileinfo
• Disk Space: Minimum 500MB for application files, plus storage for actual files
• Memory: 256MB minimum PHP memory limit, 512MB+ recommended for production

Required Software with Specific Versions

For a stable FileRun deployment, specific software versions reduce compatibility issues:

# Example version requirements
APACHE_VERSION="2.4.58"
NGINX_VERSION="1.25.0"
PHP_VERSION="8.2.12"
MYSQL