Where does it run and what leaves the building? ATX AnalyticsTable runs on your machines and uses your own cloud tenant: six flows, all of them yours.
"Where does it run, and what leaves the building?"
Every security review of an analytics tool starts there. For ATX AnalyticsTable the answer fits in one picture.
The application runs on your machines: a signed installer on the analyst's workstation, or a signed container inside your own network. Everything it needs from the cloud comes from the tenant you already run and audit. Six flows cross the boundary, and every one of them is opened from the inside:
🔑 Identity. Single sign-on with OIDC or SAML, SCIM provisioning, roles from your directory. With Entra ID sign-in (beta), queries can run as the signed-in person, so the database's own row-level security still applies.
🗝️ Secrets. Database and storage credentials live in Azure Key Vault, AWS Secrets Manager, GCP Secret Manager or HashiCorp Vault. Project files hold only a vault:// reference. No API endpoint returns a stored key, not even to an administrator.
🤖 AI. Every outbound prompt passes one egress gate with PII masking. An administrator sets a ceiling per endpoint: a model in your own tenant may see schema and samples, a public one only schema and aggregates. Point it at your gateway in front of Azure AI Foundry and the workstation holds no model key at all.
🗄️ Databases. Azure PostgreSQL, Cloud SQL and RDS accept a short-lived Entra or IAM token in place of a stored password. Connections are read-only by default.
💾 Backups and logs. Scheduled project backups and a continuous copy of the logs go to your Blob, GCS or S3 bucket. Log segments are never overwritten, so object lock and immutability policies keep working.
📜 Audit. An append-only, hash-chained audit trail on every installation, forwarded to your SIEM as syslog over TLS. Each record carries its hash, so the SIEM copy can be checked against the chain.
What stays local: the project database, git history, the vault master key and a signed licence that verifies offline.
What reaches us: no customer data. The version check and the licence revocation check are optional and can be switched off by policy, which is how the same build runs air-gapped.
One limit, stated plainly: a key sealed to a workstation can be recovered by that machine's user. That is true of any desktop software. If that is not good enough for you, keep the model key in a gateway that signs users in by SSO.
This site needs JavaScript for the full experience. Every page above is reachable without it.