The trust boundary
What runs where.
The Connector and every sandbox run on a VM or Kubernetes cluster you own. Your data platforms sit outside the line.
Sources, untouched
Sandbox, per request
Starts on approval, next to the source. Loads only the approved slice.
Approved consumers
AlienGiraffe Connector · your VM or Kubernetes
Raw rows don't cross the line. Not to us, not to a cloud.
Crosses only if you send it: query logs to your S3 or Postgres.
What crosses the line
What stays, and what can leave.
Stays in your network
- Raw rows from your sources
- Source credentials, held by the Connector on your infrastructure
- The sandbox and everything loaded into it, deleted automatically when access expires
- Query results viewed in the explorer, which has no export or download
Can cross, only if you set it up
- Query results, to the apps, AI agents, or vendors a request approves, through the API or MCP
- Query logs, to your own S3 bucket or Postgres, through Fluentd, if you configure it
Requested, approved, logged
An auditor can answer every question from one record.
Approvers are set by requester role. Low-risk templates can auto-approve; the rule that approved them is recorded like a person would be.
- Requester
- Who asked, through your SSO
- Scope
- Datasource, tables, columns, row filters, date window
- Template
- Which template, if any
- Risk score
- From the sources and fields touched
- Approver
- Who approved, or which auto-approve rule
- Sandbox
- When it started and what it loaded
- Queries
- What was run against the sandbox
Deployment and identity
Your hosts, your network, your sign-on.
Short-lived by default
Every sandbox has an end date, 24 hours unless the request sets one. A cleanup job revokes access and deletes the sandbox when it passes.
Self-hosted
A single-VM bundle on Docker or Podman, or a Helm chart on Kubernetes. No registry access needed for the bundle.
Read-only to sources
The Connector reads sources through read-only logins you create and can revoke. A read-only Oracle account works.
SSO and organizations
Requesters and approvers sign in through your identity provider, with roles mapped from it. One deployment can hold several organizations.
Security packet
Architecture, data flow, deployment options, and a pre-filled questionnaire.
Leave a work email and we'll send it.