Storage connectors
Attach release binaries via Google Drive, OneDrive, a custom server, or an S3-compatible bucket instead of pushing large files through the core API on every upload.
Storage connectors link LicenPro to external file hosts. Use them when installers, delta packages, or release notes live on cloud drives or your own CDN—release records in LicenPro still point to version metadata while artifacts resolve from remote storage.
Storage lifecycle
- Connect — authenticate provider at Storage hub.
- Configure — pick folders, credentials, or custom server base URL.
- Upload / link — place binaries in provider UI or LicenPro storage browser.
- Bind to release — associate artifact path/id when editing a release.
- SDK update check — client resolves download URL via update API + storage metadata.
- Revoke — disconnect provider; existing release links may break until re-linked.
Storage hub
Sidebar: Storage. Connect external file hosts before you attach binaries to releases.
Provider comparison
- Google Drive — one click with LicenPro's own Google app (no Google Cloud project); LicenPro sees only the files it creates; upload/list/delete via
/api/storage/google-drive/…; Pro plan. - OneDrive — one click with LicenPro's own Microsoft app (no Azure app registration); personal and work or school accounts; a
LicenProfolder is created on connect; list/upload via/api/storage/onedrive/…; Pro plan. - Custom server — your HTTPS endpoint; LicenPro proxies list/upload/delete per
/api/CustomServerStorage/…; included on every plan (the Free plan's only storage). - S3-compatible — your own bucket on Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Hetzner or MinIO; access key instead of OAuth; list/upload via
/api/storage/s3/…; Pro plan.
Google Drive
Open Storage → Google Drive (or pick Google Drive in a release) and click Connect Google Drive. Choose the Google account for your release files (any account, not necessarily the one you use for LicenPro) and approve one consent screen. No Google Cloud project, client ID or secret is needed.
- What LicenPro can access — only the files and folders it creates in your Drive (Google's
drive.filepermission). It cannot see or change your other files. ALicenProfolder is created for your releases. - Upload through LicenPro — files you add to Drive yourself are not visible to LicenPro, so upload release files from the release form or the Storage page.
- Connected before October 2026 with your own Google Cloud client? Click Connect once more. Release files linked before the change keep downloading for your customers; upload one again from its release to move it to the new connection.
- Tokens are stored encrypted. Disconnect removes LicenPro's access; you can also remove it from your Google account's third-party access page.
OneDrive
Open Storage → OneDrive (or pick OneDrive in a release) and click Connect OneDrive. Sign in with the Microsoft account for your release files (personal, or work or school; not necessarily the one you use for LicenPro) and approve one consent screen. No Azure app registration, client ID, secret or redirect URI is needed.
- What LicenPro can access — your own OneDrive files (Microsoft's
Files.ReadWritepermission, shown as "read and write your files"), your email (User.Read) and a lasting connection (offline_access). LicenPro works only in the folders you use for releases. - LicenPro folder — created at the root of your OneDrive when you connect; an existing
LicenProfolder is reused. - Work or school accounts — some organizations let only an admin approve new apps. If Microsoft asks for admin approval, ask your Microsoft 365 admin to approve "LicenPro Storage", or connect a personal account. A work account also needs a OneDrive (SharePoint Online) license.
- Connected earlier with your own Azure app? Click Connect once more with the same Microsoft account: your folder and the release files already linked keep working.
- Tokens are stored encrypted and refreshed automatically. Disconnect removes LicenPro's access; you can also remove it at
account.microsoft.com/privacy/app-access(personal) ormyapps.microsoft.com(work).
S3-compatible storage
One connector covers every service that speaks the S3 API. Each service (Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Hetzner, MinIO) has its own card under Storage → Connect a provider; Connect opens the setup with that service picked, its endpoint format, region and addressing style already filled in.
- Cloudflare R2 — create a bucket, then an R2 API token with Object Read & Write limited to that bucket. Endpoint
https://<account-id>.r2.cloudflarestorage.com, regionauto. R2 charges no egress fees, which suits update delivery. - Amazon S3 — create a bucket and an IAM user whose policy allows
s3:ListBucketon the bucket (limited to your prefix with ans3:prefixcondition) ands3:GetObject,s3:PutObject,s3:DeleteObjectonarn:aws:s3:::BUCKET/PREFIX*. No endpoint needed; enter the bucket's region. The setup page generates this policy for you. - Others (B2, Wasabi, Spaces, Hetzner, MinIO) — enter the endpoint shown with your bucket; path-style addressing is on by default.
- Optionally set a folder prefix (default
licenpro/): LicenPro only lists and uploads under it. - Save & Test — LicenPro lists the prefix, then writes, reads and deletes a small probe object. The secret key is stored encrypted and never shown again.
- The endpoint must be
httpson a public address; private, loopback and cloud-metadata addresses are refused. - The bucket can stay private. SDK update packages download through the LicenPro API after the license check, as for every provider, and are verified (size, SHA-256, signature) before install.
- Browser download links handed to customers are presigned URLs valid for 15 minutes, created only after the entitlement check.
- Changing the endpoint or bucket while releases use it asks for confirmation; those releases must have their update package verified again.
Operator workflow
- Open Storage from sidebar.
- Choose provider → complete OAuth or enter server URL + credentials.
- Verify test upload appears in provider browser.
- When publishing a release, attach artifact reference instead of embedding large blobs in API payloads.
- Validate SDK update path downloads from expected URL in staging.
Roles & plans
- Product owners — typically configure storage used by their releases.
- Free plan — Custom Server only.
- Pro plan — Custom Server, Google Drive, OneDrive and every S3-compatible service.
- Existing connections — an account on Free that is already connected to Google Drive, OneDrive or S3 can still manage or disconnect it.
- System Admin — troubleshoot connector OAuth failures platform-wide.
