Frequently asked questions.

Nobody but you. Files are AES-256-GCM encrypted on your device before any byte leaves it, and no shard-holder ever receives more than a fragment. Not your provider, not an operator with root, not us. A breach of any single provider — including a breach of SkyeConnex — yields ciphertext fragments that cannot be reassembled into anything readable.

Nobody, with one order. A subpoena reaches one provider holding a couple of shards; reconstruction needs a quorum of them, spread across every jurisdiction you chose. The request does not fail on appeal, it fails on arithmetic — there is no complete copy in any one place to produce. Residency alone does not give you this: if your provider answers to a foreign government, so does your data, wherever the server sits.

Not where the marketing region says — where SkyeMap shows it. You see every shard's actual jurisdiction, per file, right now, graded by how we know: verified by traceroute, declared by the provider, or merely inferred. Most vendors can tell you a region. We can show you a location, and sign a report saying so.

Yes, and you keep your keys. You hold the User Master Key, your shards sit in storage accounts you own, and the reconstruction maths is published. Leaving means switching off a coordinator, not negotiating the release of a hostage. Recoverability is architectural rather than contractual, so changing or ending an engagement does not affect files you already encrypted.

Nothing you did not approve. We do not train on customer data or metadata, and that is a property of the architecture rather than a promise in a policy. On SkyeGXU, embeddings, retrieval and inference run on your own hardware inside your boundary — document to answer without OpenAI, Azure or any third-party model provider seeing the corpus. Models are released by key, not downloaded: possession is not permission.

SkyeConnex is a multi-cloud sovereign storage and compliance platform. Files are encrypted client-side with AES-256-GCM, Reed-Solomon RS(5,2) erasure-coded into seven shards, and scattered across the customer's chosen storage providers across as many jurisdictions as required. The result: no single cloud, country, or government can read, surrender, or destroy your data — even under court order.

Sync tools replicate your file into each provider — each copy is independently readable, which gives you availability but not security against single-provider compromise. SkyeConnex uses Reed-Solomon erasure coding, which means no single provider holds enough of any file to read it. Compelling a read requires five providers across multiple jurisdictions simultaneously.

Yes. The User Master Key (UMK) is derived from your password (via scrypt) or recovery key and never leaves your device in unwrapped form. The server has no API path that returns plaintext — even with full database access, an operator cannot read your files.

During account setup you receive a 24-character recovery key that independently wraps your UMK. You can lose your password without losing your files — and zero-knowledge is preserved throughout, because the recovery key never leaves your custody.

Yes — both halves. ML-KEM-1024 (FIPS 203) hybrid key wrap. ML-DSA-87 (FIPS 204) signatures on every report and integrity certificate. Both shipping in production today, not on a roadmap slide.

No. The platform does not hold the capability to decrypt — the User Master Key is never on the server in unwrapped form. A court order to the platform can compel access logs and metadata, but not plaintext, because plaintext does not exist server-side.

A single provider holds only two of the seven shards your file is split into. Two shards cannot reconstruct the file. To compel reconstruction, a court must compel five different providers — in as many jurisdictions as you chose. In practice, the request fails at the second jurisdiction.

Every primitive in active use is NIST-published. FIPS 140-3 module certification is in progress — the test suite already produces KAT-style round-trip evidence and cryptographic boundary candidates are identified. There are no proprietary algorithms anywhere in the platform.

Yes. The platform supports eleven privacy regimes through region-tagging, signed audit log, deletion rights, breach detection, and data-subject-access tooling. GDPR (and UK-GDPR / DPA 2018) is one of the pre-configured compliance preset packs.

Yes. The provider plugin SDK lets you integrate a sovereign or regional provider not in the catalogue in fewer than 500 lines of code. The CloudProvider interface is the same regardless: upload, download, delete, health-check, region-detect.

Yes — through SkyeBucket. We expose an S3-compatible API at s3.skyeconnex.com. SigV4 authentication, path-style addressing, full compatibility with Cyberduck, boto3, awscli, rclone, Veeam, AWS Backup, and any other vendor toolchain that targets S3.

Yes — air-gapped deployment is an entitlement scoped at briefing. The same code that runs app.skyeconnex.com runs in a customer VPC, on-prem, or air-gapped. Includes the SkyeGXU on-prem inference subsystem — CPU or GPU — for sovereign AI workloads.

SkyeGXU is SkyeConnex's distributed compute subsystem — an ASP.NET Core coordinator and a WPF agent that runs ONNX models on customer hardware via DirectML. It exposes an OpenAI-compatible /v1/embeddings and /v1/search API, so existing RAG and semantic-search workloads work without sending data to OpenAI or Azure OpenAI.

Yes. Semantic search lets you find files by meaning rather than filename. The Barrista in-app assistant answers natural-language questions grounded in your own corpus. Both run through SkyeGXU on your own hardware — so the full path from document to answer stays inside your sovereignty envelope.

Bulk operations with multi-select for upload, plus large-file resumable uploads on every client surface. The five-endpoint chunked upload protocol (Init, Put, Status, Complete, Cancel) lets interrupted transfers resume by re-PUTting only the missing chunks. For S3-shaped workflows, point your existing tooling at SkyeBucket and migrate at line-rate.

Reads complete as long as any five of seven shards are reachable — meaning up to two providers can be down without affecting availability. Writes degrade gracefully: failed shard writes are retried with idempotent upload keys, and strict-mode hooks let you fail the upload (rather than degrade silently) when policy can't be satisfied.

Every share (account-to-account or link) records who shared, with whom, what permission grant, when. Every access — including by external link recipients — captures recipient identity into the audit log. CSV export streams; signed JSON exportable. Append-only chain.

Once a recipient has decrypted a copy on their device, you cannot prevent them retaining it — no cloud-storage product can. What SkyeConnex does ensure: the share itself becomes inaccessible at the platform, no further accesses succeed, and the revocation is audited and signed.

No — recoverability is architectural, not contractual. Both wrapped UMK variants (password-wrapped and PQ-hybrid wrapped) are unwrap-attempted on every login, and any change of scope explicitly unwraps both before clearing any wrapping. An organization that leaves SkyeConnex retains access to every file it encrypted while it was there. That is pillar four: if you cannot walk away, you were never in control.

Commercially, by deployment rather than by list price. Engagements are configured to your storage volume, the jurisdictions you need, and your integration footprint — so the shape of the deal follows the architecture you actually need. Book a briefing and we will scope it with you.

Founder Ross Norrie previously founded AssetMetrix (acquired by Microsoft, integrated into Microsoft Intune and Microsoft Graph). CFO Lora Simpson. Board includes Eli Fathi C.M. and Don Gibbs C.M. Advisors include Bill Kirwin (the Gartner analyst who originated Total Cost of Ownership in 1987). Corporate counsel: Perley-Robertson, Hill & McDougall LLP.

Investor engagement is active. Patents pending: SkyeConnex (39 claims, DGSI-aligned) and SkyeGXU. For investor inquiries, email [email protected] from your firm's domain.

Ottawa, Canada. Standard Canadian corporate structure.

The v1.2 whitepaper (June 2026, 36 pages) is the consolidated technical and commercial reference document. NDA-distributed — email [email protected] from your work domain to request.