Astry runs in your cloud. Permissions are inherited from your source systems. The model only ever sees the files the asker is authorized to see — enforced at the operating system, not via prompt instructions.
Astry deploys into your Azure, GCP, or AWS account. Your vault, your Postgres, your audit logs — all on infrastructure you own. We hold no credentials to your environment.
Before any inference, the system computes the asker's authorized file set, copies only those files into a temporary sandbox, and runs the model with that directory as its world. You can't prompt-inject your way past a file that isn't there.
If a user can't see a Slack channel, they see nothing derived from it. Astry doesn't maintain a parallel permission store. The source system is the authoritative record.
In Bring-Your-Own-Cloud deployments, the engine runs inside an AMD SEV-SNP Confidential VM. Your cloud admin — and the cloud provider — cannot inspect or extract the running code.
Identity, authorization, and isolation are all decided in plain code. The model only becomes part of the system once access control has already been resolved.
The only third parties are the ones you choose. Bring your own keys, bring your own models, and Astry runs entirely inside your boundary.
We'll share the architecture whitepaper, current SOC 2 progress, and a deployment plan scoped to your cloud and identity provider.