Security and ownership

Your server stays yours. The deployment workflow stays visible.

Understand the ownership boundary, outbound agent connection, permissions, and customer responsibilities in Opslin.

Direct answer

Opslin is designed to coordinate approved deployment tasks on a compatible Linux VPS you control. It does not take ownership of your server, infrastructure account, application code, or production decisions.

Server ownership: Customer
Agent connection: Initiated outbound from the connected server
Operational access: Scoped to the account, organisation, and permissions in use
Customer responsibility: Infrastructure account, code, data, and production decisions

Outbound connection model

Opslin uses an agent connection initiated from the server you connect. This supports a workflow where the server reaches the control plane instead of exposing a separate public management port for the agent channel.

Permissions and approvals

Operational actions are tied to the Opslin account and organisation that authorise them. Teams should review access, permissions, connected servers, and deployment settings before using a production environment.

What Opslin does not replace

Opslin does not remove the need for sound application security, backups, access control, provider-account security, or production review. Compatibility and operational limits still apply during beta.

Last reviewed: July 28, 2026