Our stack choices are pragmatic rather than religious. For ingestion, Airbyte and Fivetran are both good options, and the choice depends on your source portfolio and budget: Fivetran is more expensive but needs less maintenance, while Airbyte is open source and works excellently self-hosted. For custom-built connectors, we work with Meltano or our own Python layer. For orchestration, Airflow remains the de facto standard, but Dagster and Prefect have strengths in data asset tracking and developer experience respectively. We advise based on your team's skills and operational needs.
For transformation, dbt is our starting point — almost all modern warehouse projects use dbt for SQL models with tests, lineage and documentation. For Python-based transformations (denoising, feature engineering, NLP) we use dbt-python, Polars or Spark, depending on scale. For the warehouse layer itself, we have extensive experience with Snowflake, BigQuery, Azure Synapse, Databricks, Redshift and ClickHouse, plus on-prem Postgres with Citus for situations where cloud is not an option.
For BI on top, we can work with any mainstream tool (Power BI, Tableau, Looker, Metabase) or build a custom BI tool when you need embedded analytics or multi-tenancy. For observability, we use Monte Carlo or Soda, and for data catalogues DataHub or OpenMetadata. For AI integrations, we work with LangChain, LlamaIndex or a custom RAG orchestration, and we build vector tables on pgvector, Weaviate, Pinecone or Snowflake Cortex.
The idea behind these choices is always the same: you get a warehouse built on open standards (SQL, Parquet, Iceberg, dbt), so your team can switch vendors in future without losing your data model. Vendor independence isn't a marketing slogan but an architectural principle: we build warehouses that you can maintain yourself, or that another team can take over from you.