Feature Comparison
This guide compares the features available in KFtray's graphical and terminal interfaces to help you choose the right tool for your needs.
Interface Comparison
| Feature | KFtray (GUI) | KFtui (Terminal) |
|---|---|---|
| TCP/UDP Forwarding | ✅ | ✅ |
| Multiple Port Forwards | ✅ | ✅ |
| GitHub Sync | ✅ | Coming Soon |
| HTTP Traffic Logging | ✅ | Coming Soon |
| System Tray Integration | ✅ | ❌ |
| Resource Usage | Moderate | Light |
| Direct Configuration Editing | ✅ | Coming Soon |
State and Process Management
While KFtray and KFtui share the same database and configurations, they manage port forwarding processes independently. A port forward started in one interface will show as running in both, but must be stopped from the interface that started it.
Use Case Recommendations
Choose KFtray GUI when:
- You prefer a graphical interface
- You need GitHub synchronization
- You want HTTP traffic logging
- You need system tray integration
- You work primarily on desktop environments
Choose KFtui when:
- You work in terminal-based environments
- You prefer lightweight resource usage
- You want keyboard-driven controls
- You work with headless systems
Interface-Specific Features
KFtray GUI Exclusive
- GitHub configuration sync
- HTTP traffic logging
- System tray notifications
- Visual configuration editor
- Drag-and-drop support
KFtui Exclusive
- Lower resource usage
- Terminal multiplexer support
- Keyboard-driven workflow
- Remote server compatibility
Process Independence
Important notes about process management:
- Port forwards started in KFtray must be stopped in KFtray
- Port forwards started in KFtui must be stopped in KFtui
- Status is visible in both interfaces
- Configuration changes are immediately visible in both interfaces
Choose the interface that best matches your workflow and environment requirements, keeping in mind the process management considerations.