Linux environment
A supported, maintained Linux server environment suitable for the agent and Docker-based workloads.
VPS compatibility
Provider-neutral by design. Requirements-first by necessity.
Opslin is built for compatible Linux VPS and cloud virtual machines with a public IP, suitable permissions, networking access, and enough resources for the applications you intend to run.
Readiness explorer
Inspect the server boundary before installation.
Use the interactive preflight to understand the required layers. It is educational, not a real server scan.
Customer-controlled VPS123456Interactive preflight
Review the compatibility boundary
Passing this local checklist is not provider certification or a real compatibility test.
Compatibility checklist
What a server needs before you connect it.
Exact sizing depends on your workloads. Validate these fundamentals before using a server for production.
Reachable networking
A public IP and firewall rules that allow your applications, domains, and required outbound connections to work.
Administrative setup
Authorized administrative access is required to install and operate the server agent and supporting services.
Workload-sized CPU and memory
Capacity must cover the operating system, agent, builds, application containers, and any co-located services.
Durable storage
Choose storage capacity and performance for releases, container images, logs, databases, and growth.
A clean operational boundary
Use infrastructure you own or are explicitly authorized to administer, with provider recovery access retained.
Provider status
We do not label unvalidated providers as tested.
The current public page focuses on technical criteria because provider-specific test evidence and maintained compatibility labels are not yet published.
- Expected compatible
- Standard Linux VPS or cloud VM meeting the documented prerequisites. This is a compatibility expectation, not a completed provider certification.
- Not suitable
- Shared hosting without administrative access, unsupported operating systems, restricted networking, or infrastructure you are not authorized to manage.
- Before production
- Test agent reconnection, deploy and rollback behavior, DNS, SSL, provider recovery access, resource limits, and your backup strategy.
Your infrastructure. One clear workflow.
Validate with a test VPS first.
Use a non-critical server to verify connectivity and workload requirements before moving a production application.