Everything your IT needs before the approval: what VeloxFactory needs to run, what the Print Service needs, which connections are used and how your data is protected.
VeloxFactory server (self-hosted)
- Operating system
- Linux, or a Linux container on Windows
- PHP
- 8.2 or higher
- Web server
- Apache (recommended), nginx works too
- Database
- MySQL (default, recommended), SQL Server, PostgreSQL or SQLite, which is enough for smaller installations
- Services
- Supervisor and Redis, Redis and MySQL also as Docker containers
- Minimum
- 2 CPU cores, 2 GB RAM, 40 GB disk
Print Service
- Operating system
- Windows, every version .NET 10 runs on
- Runtime
- .NET 10
- Connection
- Directly by WebSocket, or it polls the print jobs through the API
Network
- Web and API
- HTTP or HTTPS
- WebSocket
- WS or WSS
- Ports
- Two: one for web and API, one for WebSocket
Security
- Encrypted connections with HTTPS/TLS.
- Login with a password, permissions per user.
- API tokens with fine grained permissions and a limited validity, admins can revoke them.
- History with automatic purge after a retention you set.
- Updates and security fixes.
- Regular security audits.
Managed SaaS
- Run by us on a dedicated server at Hetzner in Germany.
- Backups are made by us.
- A data processing agreement is available.
Questions from your IT?
We answer technical questions directly, from the people who build VeloxFactory.