Connexion

Why "connexion" instead of "connection"

The spelling is deliberate: SkyeConnex uses "connexion" (the older variant) to make clear that the platform's relationship to each provider is a configured, named, scoped relationship — not a generic network connection. Each connexion has a name, an authentication context, a region (probed or declared), a health status, and a policy scope.

What a connexion holds

Provider type (S3, Azure Blob, GCP, Backblaze B2, Cloudflare R2, Wasabi, MinIO, Hetzner, OVH, Scaleway, Dropbox, Google Drive, OneDrive, Box, etc.)
Authentication credentials (OAuth tokens, access keys, role ARNs) — encrypted at rest
Region (probed via provider API where possible; operator-declared otherwise)
Health status — provider heartbeats every ~5 minutes
Scope — personal, company-shared, or reseller-scoped

Connexion health

The platform continuously probes each connexion. Stale OAuth credentials raise a badge before the next upload fails. An aggregated connexion-issues banner appears on the file browser, so operators learn about provider problems before failed writes rather than from them. Auto region detection runs on connexion creation and refresh.

Sharing connexions

Connexions can be personal or promoted to company-shared. Once shared, every account in the company inherits the connexion for use in their scatter set. Re-authorisation flows are operator-friendly; stale credentials surface before they affect uploads.

Tier-gated connexion limits

The Free tier supports 1 connexion. Pro: 3. Premium: 7. Enterprise and Sovereign: unlimited. Adding the 8th connexion on Premium prompts a clear upgrade path.

Bring your own provider

The provider plugin SDK lets customers integrate a sovereign or regional provider not in the catalogue. Roughly 500 lines of plugin code implements the CloudProvider interface: upload, download, delete, health-check, region-detect. The plugin runs alongside the standard connexion machinery.