Product Overview

What is Stylus SFTP Server?

Stylus SFTP Server is an enterprise-grade file-transfer platform. Users connect over SFTP, FTP and FTPS, or WebDAV, or from any browser through the built-in file portal — all against one set of accounts, quotas, and audit trail. A built-in Knowledge Base and an identity model of organizations and groups round out the platform. Designed for production deployment, it runs on both Windows and Linux — as a Windows service, a Linux systemd service, or a standalone process on either.

Each user connects via any supported protocol and receives an isolated home directory. Downstream systems pick up transferred files from the shared filesystem or database backend, making Stylus SFTP Server a simple, reliable file-exchange hub.

Key Features

Transfer Protocols

Authentication

Identity Model — Organizations, Groups, Virtual Folders

Editions

Stylus SFTP Server ships in four editions, gated at runtime by an activation.key file:

EditionNotable capabilities
Free Single SFTP connection, XML flat-file or bundled H2 users, local filesystem storage, log-file audit. Perfect for evaluation and low-volume personal use.
Standard Adds FTPS, unlimited connections, JDBC / LDAP authentication, JDBC / syslog / webhook audit, and the identity model (organizations, groups, virtual folders).
Professional Adds the database storage backend (files as ref-counted BLOBs in SQL Server / MySQL / PostgreSQL) and MFA.
Enterprise Adds Portal white-label branding, PGP signing (Portal Sign button, /KEYS endpoint), and cloud vault secret storage.

The License tab in the admin console shows the current edition, customer, expiry date, and source of the running activation key. See Administration » License Management for the update / clear workflow.

Filesystem & Uploads

Security

Monitoring & Audit

Administration

Architecture Overview

Component Technology Role
Runtime Java 21 (LTS) Application platform
SSH / SFTP engine Built-in SFTP protocol implementation
FTP / FTPS engine Apache FtpServer 1.2.0 FTP/FTPS protocol implementation
Default database H2 (embedded) Zero-config storage; upgrade path to SQL Server, MySQL, or PostgreSQL
Connection pool HikariCP JDBC connection pooling
Caching Caffeine Account and quota caches
Password hashing Bouncy Castle BCrypt and SSH cryptographic operations
Web server Embedded Tomcat 11 Web admin console and file transfer portal
Logging Log4j 2 + SLF4J facade Application and audit logging
Windows service Apache Commons Daemon (procrun) Service registration and lifecycle

Deployment Model

Stylus SFTP Server follows a simple file-exchange pattern:

  1. Users connect via SFTP or FTPS and authenticate against the configured provider.
  2. Each user is placed in an isolated home directory.
  3. Uploaded files go through a staging phase (written as .tmp files) and are atomically renamed upon successful completion.
  4. Downstream systems pick up completed files from the shared filesystem.
Tip Downstream processes should ignore .tmp files — these indicate uploads that are still in progress.

System Requirements

Requirement Minimum Recommended
Java 21 (LTS) 21 or later
Operating system Windows Server 2016+ or Linux Windows Server 2022 or current Linux LTS
Memory (JVM heap) 512 MB 1 GB or more
Disk space Sufficient for home directories and the embedded database. Plan according to expected transfer volume.
Note The staging directory (.tmp files) and the final target directory must reside on the same filesystem volume, because the server uses ATOMIC_MOVE to rename completed uploads.