Important: Using, running, or uploading remote development tools that execute IDE backend processes on the server violates our Terms of Service. Please ensure your development workflow complies with these guidelines to avoid service disruption or account suspension. Running your IDE locally and connecting via SSH/SFTP for file transfers is permitted and encouraged.
What Are Remote Development Tools?
Remote development tools allow developers to run their IDE (Integrated Development Environment) directly on the server, rather than on their local computer. Tools like PhpStorm Remote Development* and VSCode Remote SSH establish an SSH connection and execute the IDE’s backend processes on the server itself, using the server’s CPU, memory, and disk resources to index files, analyse code, and provide intelligent features.
w
Popular remote development features include:
- PhpStorm Remote Development – Runs the IDE backend on the server, indexing and analysing your entire codebase remotely
- VSCode Remote SSH – Executes VSCode’s language servers and extensions directly on the server
- Remote development containers – Launches full development environments on the server with continuous resource consumption
- Code Server – Web-based IDE environments running on the server
- Jupyter notebooks or similar development environments – Interactive development tools hosted on the server
Important Distinction: This is completely different from connecting your local IDE to the server using SSH/SFTP for file transfers. Using your IDE on your local computer to connect via SSH/SFTP for controlled file uploads and downloads is allowed and recommended.
The key difference:
- Allowed: Your IDE runs on your local computer and transfers files via SSH/SFTP when you save
- Prohibited: Your IDE runs on the server, consuming server CPU, memory, and disk I/O continuously
This policy specifically addresses remote development features where the IDE backend executes on the server, not traditional SSH/SFTP file synchronisation from a locally-running IDE.
Prohibited Activities
The following activities are strictly prohibited on all Ecenica hosting accounts (shared hosting/cPanel and VPS):
- Running remote IDE processes on the server
- Uploading remote development tools or their configuration files to your hosting account
- Hosting web-based IDE environments such as Code Server or similar applications
- Using remote development features that execute IDE backend processes on the server
- Installing development containers or environments that run continuously on the server
This prohibition applies regardless of whether your account is on a shared hosting or VPS environment.
Why we block Remote Development Tools
Remote development tools are prohibited on our hosting platform for the following reasons:
Server Resource Consumption
When an IDE runs on the server, it creates excessive resource usage:
- CPU consumption: Code indexing, analysis, and intelligent features consume significant processing power
- Memory usage: IDE backend processes can consume 500MB-2GB of RAM continuously
- Disk I/O: Constant file system scanning, indexing operations, and cache writes
- Process overhead: Multiple background processes running simultaneously
- Persistent connections: Long-running SSH sessions that never terminate
System Stability Impact
The intensive operations performed by remote development tools can destabilise servers. On shared hosting, excessive resource consumption by one account impacts all customers sharing the same physical hardware, causing:
- Slower website load times for all users
- Email delivery delays
- Database connection failures
- Service interruptions during peak usage
On VPS hosting, uncontrolled resource usage can consume all available server resources, degrading performance for any applications or services running on your VPS.
Consequences of Using Remote Development Tools
If remote development tools are detected on your account—whether running, uploaded, or configured—you may experience the following consequences:
Immediate Service Disruption
- Email service interruption – Your email may stop working due to excessive disk I/O and memory consumption
- Website downtime – Your website may become slow or completely unresponsive
- Database connection failures – High server load prevents database connections from being established
- Service suspension – Account services may be suspended without warning to protect server stability
Account Resource Exhaustion
- CPU limits exceeded, causing process termination
- Memory allocation failures leading to crashed processes
- Disk quota consumption from IDE caches and temporary files
- Exceeding file descriptor limits, preventing new connections
Account Action
- First violation: Warning email/ticket with 24-hour notice to cease usage, remove all remote development tools, and delete related files
- Continued usage: Temporary account suspension until IDE backend processes are terminated and all remote development tools and related files are completely removed from your account
- Repeated violations or failure to comply: Permanent account termination
- Hosting of remote development tools as a service: Immediate permanent account termination
Uploading or hosting remote development tools—even if not currently running—constitutes a violation of our Terms of Service and may result in account suspension or termination.
Approved Alternative Development Methods
We recommend these approved workflows instead:
Local IDE with SSH/SFTP (Recommended)
Connect your local IDE (PhpStorm, VSCode, Sublime Text, etc.) to the server using standard SSH/SFTP connections for manual file transfers. This allows you to:
- Edit files locally on your computer where the IDE backend runs
- Upload files only when you explicitly save or deploy them
- Use built-in SSH/SFTP clients without running IDE processes on the server
- Maintain full IDE functionality (code completion, debugging, refactoring) without impacting server performance
- Configure your IDE’s deployment settings to upload on save or manual sync
This approach is actively encouraged and provides the best balance between convenience and server stability. Your IDE remains on your local machine; only the files are transferred to the server.
Git-Based Deployment
Use Git version control with automated deployment:
- Develop locally on your computer with your IDE running locally
- Commit changes to a Git repository (GitHub, GitLab, Bitbucket)
- Deploy to your hosting account via Git pull, webhooks, or automated CI/CD pipelines
FTP/SFTP File Transfer
Upload completed files manually using dedicated FTP/SFTP clients:
- FileZilla
- Cyberduck
- WinSCP
cPanel File Manager
Use the built-in cPanel File Manager for small edits directly in your browser when quick changes are needed.
Detection and Monitoring
Our systems actively monitor for:
- Remote IDE backend processes running on the server (e.g.,
idea,code-server,remote-ssh-server) - IDE configuration files and remote development tool uploads (
.idea/remote-dev-server,.vscode-server, Code Server binaries, etc.) - Presence of remote development tool files in your account directories
- Abnormal CPU and memory consumption patterns consistent with IDE indexing operations
- Persistent SSH connections with high resource usage rates
- File system patterns indicating IDE cache and index operations
Note: Standard SSH/SFTP connections for manual file transfers from a locally-running IDE will not trigger these alerts. Only remote IDE backend processes running on the server and uploaded remote development tools are monitored and restricted.
Questions?
If you require assistance setting up an approved development workflow using your local IDE with SSH/SFTP deployment, please contact our support team. We’re happy to help you establish a deployment process that meets your needs whilst maintaining server stability for all customers.
