1ProNAS1ProNAS Downloads
DocumentationBack to website
SIGNED CONNECTORS · RELEASE STATUS

Connect your NAS without exposing it to the internet.

1ProNAS connectors use outbound HTTPS and tenant-bound identities. Packages will be published here only after signing, checksum verification, compatibility testing and rollback validation are complete.

Connector release status

No production connector binary is publicly released yet. Do not download 1ProNAS packages from third-party websites or accept unsigned files.
In development

Synology Connector

Planned native SPK package for supported Synology NAS models, with guided pairing and signed updates.

In development

Universal Linux / Docker Connector

For compatible Linux file servers, Docker-capable NAS devices, TrueNAS SCALE and controlled gateway deployments.

Planned

Windows Connector

Signed Windows service for Windows Server shares and authorised bridges to unsupported NAS devices.

Planned

QNAP Connector

Native QPKG after the universal Linux connector and package-signing pipeline are stable.

How connector pairing works

  1. The client administrator creates a connector in the 1ProNAS portal.
  2. The portal issues a short-lived pairing code.
  3. The connector sends the code over outbound HTTPS.
  4. The control plane binds it to one tenant and one device record.
  5. The pairing code expires and cannot be reused.
  6. The connector continues with its tenant-bound machine identity.

Human portal passwords and connector credentials remain separate. A connector key is never used to sign in to the client portal.

Package and command security

  • Every release must include a SHA-256 checksum and detached signature.
  • Windows installers require Authenticode signing.
  • NAS packages require vendor-compatible package signing.
  • Updates use signed manifests and staged rollout.
  • Archive and reclaim commands include tenant, connector, expiry, nonce and policy information.
  • The connector rejects expired, replayed, altered or wrong-tenant commands.
The control plane does not directly delete customer files. The connector must verify archive evidence, policy and a dry run before any approved source action.

Release channels

  • Stable: normal production use.
  • Candidate: controlled customer validation.
  • Beta: feature testing with explicit approval.
  • Internal: Axon engineering only.

Published packages will include supported operating systems, NAS models, minimum control-plane version, release notes, upgrade instructions and rollback instructions.

Read connector documentation