Most installations and maintenance work can be carried out remotely. On-site visits are only required for hardware installations or critical problems. This saves time and costs and enables fast response times.
Remote installation: standard for software
What can be installed remotely?
Software components:
- Operating system and base software
- AI platform (Docker Compose or Kubernetes)
- AI models and configuration
- Monitoring tools (Prometheus, Grafana)
- API gateways (LiteLLM)
Configuration:
- Network configuration
- Firewall rules
- SSL certificates
- User management
- Integrations
Advantages:
- Faster installation (no travel time)
- Lower costs (no travel expenses)
- More flexible scheduling
- Immediate availability
Prerequisites for remote installation
Network access:
- VPN connection to the server
- SSH access
- Firewall rules for remote access
Hardware already on site:
- Hardware must be physically installed
- Network connection available
- Power supply available
On-site installation: required for hardware
When is on-site installation needed?
Hardware installation:
- Physical setup of servers
- Network cabling
- Power connection
- Cooling (if required)
Complex setups:
- Multi-server clusters
- Special network configurations
- Air-gapped systems (without internet)
Initial installation:
- For completely new setups
- When no remote infrastructure exists
On-site installation process
Day 1: Hardware setup
- Physical setup
- Network connection
- Initial functional tests
Day 2: Software installation
- Operating system installation
- Base configuration
- Set up remote access
Day 3: Configuration (mostly remote)
- AI platform installation
- Models and configuration
- Testing
Remote maintenance: standard in maintenance package
What’s included in the monthly maintenance?
24/7 remote monitoring:
- System monitoring (Prometheus, Grafana)
- Performance metrics
- Automatic alerts
Remote maintenance:
- Software updates
- Security patches
- Configuration adjustments
- Troubleshooting
Remote support:
- Technical support via email/phone
- VPN-secured access to dashboards
- Remote logging and analysis
Advantages:
- Fast response times (no travel time)
- Lower costs (no travel expenses)
- Proactive monitoring
- Early problem detection
On-site visits: only when needed
When are on-site visits required?
Hardware problems:
- Defective hardware components
- Network hardware issues
- Cooling issues
Critical problems:
- System failure that cannot be resolved remotely
- Air-gapped systems without internet
Planned maintenance:
- Hardware upgrades
- Extended installations
- Training (if desired)
Costs:
- On-site visits are not included in standard maintenance
- Billed separately (if required)
- Usually not required for standard setups
Comparison: remote vs on-site
| Aspect | Remote | On-site |
|---|---|---|
| Speed | Fast (no travel time) | Slower (travel time) |
| Costs | Low (no travel expenses) | Higher (travel expenses) |
| Availability | Immediately available | Scheduling required |
| Suitable for | Software, configuration | Hardware installation |
| Response time | Minutes to hours | Hours to days |
Typical scenarios
Scenario 1: Standard setup (mostly remote)
Installation:
- Day 1: Install hardware on site (on-site)
- Day 2–3: Software installation (remote)
- Total: 1 on-site day + 2–3 remote days
Maintenance:
- 100% remote (standard)
- On-site only for hardware problems
Scenario 2: Fully remote (when hardware is available)
Prerequisite:
- Hardware already available
- Network access available
Installation:
- 100% remote possible
- Total: 3–5 remote days
Maintenance:
- 100% remote (standard)
Scenario 3: Air-gapped system (on-site required)
Prerequisite:
- No internet access
- Isolated network
Installation:
- 100% on-site required
- Total: 5–7 on-site days
Maintenance:
- On-site required for updates
- Remote monitoring via isolated network possible
Best practices
1. Set up remote access early
After hardware installation:
- Set up VPN connection
- Configure SSH access
- Install monitoring tools
Advantage: All further work can then be done remotely.
2. Monitoring from the start
Set up remote monitoring:
- Prometheus + Grafana
- Alertmanager for critical states
- Remote logging
Advantage: Problems are detected early, before they become critical.
3. Documentation
Document remote access details:
- VPN configuration
- SSH access
- Monitoring dashboards
Advantage: Fast response times for problems.
Next steps
Would you like to know more about remote and on-site options?
- Contact us – Get advice on installation and maintenance options
Sources and further information:
- On-Premise AI for SMEs – Remote maintenance and monitoring