Migration overview
The Tiny SFTP Server is designed as a minimalist tool for quick, simple file transfer tasks. It requires no installation, runs as a standard desktop application, and is ideal for ad-hoc usage.
As your needs evolve, requiring background automation, multiple user accounts, or additional protocols, the intentional architectural limits of the Tiny edition may be reached. The Buru SFTP Server addresses these production scenarios with a scalable, service-oriented architecture.
Already decided to upgrade?
If you are ready to move to Buru SFTP Server, you can skip this comparison and go straight to the Migration Guide to start transferring your configuration immediately.
Security and authentication
Tiny SFTP Server is secure from the client perspective, utilizing standard SSH encryption for data in transit. It stores passwords in a plaintext configuration file, which is as secure as any other file (like an unencrypted SSH private key) as long as the host filesystem is secured.
Buru SFTP Server enhances security for multi-user and enterprise environments:
Secure hashing
Passwords are salted and hashed using SHA-512 by default, ensuring credentials are never stored in a readable format even if the user database is compromised.
Public key auth
Both Tiny and Buru support SSH public key authentication for passwordless login, though Buru allows multiple keys per user.
Windows authentication
Integrate with local or Active Directory Windows accounts (Pro edition) to leverage existing organizational identities.
Account lockout
Automatically protect against brute-force attacks by locking accounts after repeated failed attempts.
Operational modes and availability
Both servers offer "auto-start" features, but they function differently depending on your deployment needs:
- Tiny SFTP Server: Includes an option to start serving files automatically as soon as the executable is launched. However, it remains a desktop application that requires an active user session and manual execution (or a startup script) to run.
- Buru SFTP Server: Offers dual modes of operation. It can run as a Windows Service, which starts with the OS and runs even when no user is logged in, or as a Portable App launched from the command line for on-the-go scenarios.
Windows service
Runs continuously in the background without requiring an active user login.
Portable mode
Run as a standalone command-line application from a USB stick or script.
High availability
Optimized for 24/7 production environments and unattended background operations.
Multi-protocol support and scalability
While Tiny SFTP Server focuses exclusively on SFTP, Buru SFTP Server is a multi-protocol solution designed to handle diverse file transfer requirements.
FTP/FTPS support
In addition to SSH/SFTP, Buru supports serving files via plain FTP and secure FTP over TLS (FTPS).
Unlimited users
Manage distinct accounts with unique permissions, unlike the single-user limit of Tiny.
Complex virtual paths
Map multiple physical directories from different locations to a single user's virtual filesystem.
Monitoring and administration
Tiny SFTP Server offers a minimal interface suitable for manual oversight. Buru SFTP Server provides professional tools for auditing and remote management:
Detailed logs
Separate server and access logs (available in JSON) for troubleshooting and auditing user activity.
Web Administration
Configure users and monitor the server remotely via a browser-based dashboard.
Command line (CLI)
Full management via burusftp.exe, allowing for powerful automation and scripting.
Comparison summary
The following table summarizes the capabilities of both editions.
| Feature | Tiny SFTP Server | Buru SFTP Server |
|---|---|---|
| Primary Use Case | Ad-hoc transfers, Testing | Production, Services, Automation |
| Running Mode | Desktop Application | Windows Service & Portable CLI |
| Max Users | 1 | Unlimited |
| Max Mapped Folders | 1 | Unlimited |
| Password Storage | Plaintext (Secure if file is) | Secure SHA-512 Hash |
| Protocols | SFTP | SFTP, SSH, SCP, FTP, FTPS |
| Authentication | Internal & Public Key | Internal, Public Key, & Windows Auth |
| Administration | Desktop GUI / Config File | Web Admin, CLI, Config File |
Next steps
If your current usage requires background stability, multi-protocol support, or advanced auditing, we recommend upgrading to Buru SFTP Server. Follow the Migration Guide to transfer your existing configuration.