For Databricks partners | AlienGiraffe
For Databricks consultants and SI architects

The part of the Databricks project that stalls.

Every regulated engagement has a list of sources that can't be ingested. AlienGiraffe gives you an answer for that list, so the rest of the project ships.

The stuck list

Sources that block regulated projects.

Each item links to the Databricks documentation that describes the limitation.

  • Oracle on RAC or Exadata RAC: not supported by the Oracle CDC connector. Databricks docs
  • DBAs who won't enable supplemental logging or grant LogMiner on the primary. Databricks docs
  • Data that may not leave the country or the building, even through federation's cloud compute. Databricks docs
  • Log files on SSH servers, which the SFTP connector can only copy in. Databricks docs

Where we fit in your architecture

Paste it into your proposal.

Databricks and Unity Catalog in the cloud; sandboxes next to the sources; what crosses the boundary and what doesn't. Free to use, PNG or editable SVG.

Reference architecture: sources, the sandbox, and the Alien Giraffe Connector inside the customer network; Databricks and Unity Catalog outside it, with policy flowing in and masked results flowing out.

What implementation looks like

Something your client's platform team will approve.

One VM

A container bundle on Docker or Podman. No registry access needed.

Or Kubernetes

A Helm chart for the cluster the client already runs.

Config as files

Datasources and request templates are versioned with the rest of the engagement.

What's in it for you

Partner benefits

Early access to the Unity Catalog integration

Your engagements get the first builds, and your architects shape what Unity Catalog passes in and gets back.

Co-delivery on your first engagement

Our engineers deliver the first deployment with your team: architecture session, security review, and DBA conversation included.

For architects

Technical FAQ

Partner field guide

Four pages for your next discovery call.

The comparison table, the architecture diagram, three discovery questions, and the deployment checklist.

Launch partners

Bring us one stuck use case.

Tell us about your firm and one source your client can't ingest. We'll come back with how the sandbox would sit in that architecture.

We reply to every application.