Email is live in Sydney today. Everything after it earns its place only when we can explain where the relevant data goes, how long it stays, and what the customer can inspect.
These are directions, not products you can buy or rely on today.
What we are building toward
Three workloads. The same standard.
The roadmap is intentionally short. New capability should reduce the work needed to answer a residency question, not create a new system a customer has to audit.
01
Automation
Run the work in the region.
A regional automation runtime for the jobs and workflows that sit beside a sensitive-data product. Inputs, execution state, queues, and logs should be answerable against the same selected region.
Directional
02
Document extraction
Extract documents inside the boundary.
Upload, temporary storage, extraction, results, and deletion must all be described by the regional manifest. This is the next workload we want to prove with Australian design partners.
Directional
03
Messaging
Apply the model to messages.
SMS and conversations bring the same question back: where do message content, delivery records, provider events, and operational logs go? The answer needs to be as specific as it is for email.
