- Should we choose Databricks, Snowflake or BigQuery?
- It depends on your workloads and your team, and we will tell you honestly when Databricks is not the answer. Databricks suits heavy data engineering, streaming and machine learning, and teams comfortable in Python and Spark. Snowflake suits strong governance, data sharing and business-user AI with less platform engineering. BigQuery suits Google Cloud-centric teams and serverless analytics. We build on all three, which is exactly why the free AI assessment starts with your constraints rather than our preferences.
- Where does Databricks run, and can our data stay in South Africa?
- Databricks is deployed on top of AWS, Azure or Google Cloud rather than on its own infrastructure, so your workspace region follows the cloud you already use — and all three of those providers operate South African regions. Because service and region availability changes, we confirm the specific region against Databricks' published availability as part of the assessment rather than assuming it, and we document the result for your information officer before any data moves.
- What is Agent Bricks, and how is it different from just calling an API?
- Calling a model API from a notebook gives you an answer and no governance. Agent Bricks gives you an agent platform where tools are registered and governed in Unity Catalog, context comes from the lakehouse and vector search, external systems connect over MCP, and every call runs through an AI Gateway with logging, guardrails and PII detection. The difference shows up the day your compliance team asks what an agent accessed last Tuesday.
- Can we use Claude models on Databricks?
- Yes, natively. Databricks and Anthropic signed a five-year partnership to offer Claude models directly through the Data and AI Platform, available from a SQL query or a model-serving endpoint across AWS, Azure and Google Cloud deployments. Because the models are served inside the platform, you are not replicating data out to a separate model vendor and access remains governed by Unity Catalog. As an independent member of Anthropic's Claude Partner Network we use Claude where reasoning depth earns its cost, and cheaper models where it does not.
- Do we need Unity Catalog if we already have access controls?
- You need it more than you think, and the reason has changed. Unity Catalog began as centralised permissions and lineage, which is valuable but arguably optional on a small estate. It is now the layer that gives agents a governed definition of your business through Glossary and Domains, and that enforces Contextual Service Policies on what a tool may actually do. Once something non-human is querying your data, catalog governance stops being hygiene and starts being the control.
- How do we stop Databricks costs running away?
- Cost on Databricks is mostly a design problem rather than a pricing problem. We set cluster policies so nobody spins up a cluster twenty times the size of the job, right-size serverless workloads, consolidate overlapping jobs, and attribute DBU consumption by team and workload so the conversation about spend has names attached to it. On estates that grew organically this is usually the fastest measurable win in an engagement.
- Are you an official Databricks partner?
- We describe ourselves as a Databricks partner practice: that phrase describes our delivery capability on the platform, not a signed programme membership, and Automation Architects is independent of Databricks, Inc. and not affiliated with, sponsored by or endorsed by it. Our only formal programme membership is Anthropic's Claude Partner Network. We would rather be precise about that than let a badge do the talking.