Compute you can locate
Every workload runs on Australian-owned compute — BinaryLane cells for burst and edge, Tasmania Proxmox for the primary. The ownership of the metal is the legal boundary; the region placement is the latency boundary.
SOVEREIGN / ARCHITECTURE
Sovereignty is a build decision, not a badge.
Lots of products say “your data is safe with us.” Ptyktos makes a narrower, checkable claim: customer data never leaves Australian-owned metal, and no third party sits in the data path. That is not a policy page — it is how the system is built, and the build is public.
THE THREE CLAIMS
TLS terminates here
The edge is self-operated: certificates issued directly to Australian nodes, TLS terminated on them. No global proxy sits between your request and the engine — routing through one would hand a third party plaintext customer traffic, so the architecture excludes it rather than deprioritising it.
Provable, not asserted
The deployment recipes, the provisioning contracts, and the benchmarks are in public repositories. The claim “sovereign by architecture” is auditable the same way our benchmark numbers are: follow the artifacts.
THE DATA PATH
Your request, end to end.
Your client resolves the API over DNS (or natively, over the Ptyktos overlay for lowest latency) and lands on an Australian edge node that terminates TLS with its own certificate. The node authenticates the call against the credential store, serves it from the extraction and conversion engines running beside it, and appends the audit record to storage on the same jurisdiction. Backups and durable archives replicate to Australian-owned object storage. At no step does a non-Australian-owned system terminate, proxy, cache, or inspect your content.
THE LIMITS, STATED
What this claim is not.
It is not a security certification — certification work is scheduled and this page will carry the stamp when it is earned. It is not invisibility: your usage is metered and logged, and that log is yours to reconcile. And it is not a promise about external engines you explicitly choose to bring under BYOK Mode — those keys route to those providers, by definition, and the API tells you when that is happening.