Open Brewery DB

Food and drink

Ready to useNo account needed

Open Brewery DB's public directory of breweries, cideries and brewpubs, with their locations and contact details. Ingest delivers this data to a data warehouse you own as 2 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What people use it for

  • Map breweries near youPlot breweries by location to find what is nearby or plan a trip.
  • Compare brewery typesSee the mix of breweries, brewpubs and cideries in an area.
  • Look up contact detailsFind a brewery's website, phone number or address in one place.

What you get

TableEach row is
Breweries
breweries
One brewery
Brewery search results
breweries_search
One brewery matching a search term

Good to know

  • Breweries: Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.
  • Brewery search results: Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.

How it works

  1. Choose Open Brewery DB. The data is public, so there is nothing to sign in to.
  2. Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
  3. Pick a schedule. Daily is the default, and weekly and monthly are there too.
  4. Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

What does the Open Brewery DB data include?
2 tables: breweries (one row per brewery) and brewery search results (one row per brewery matching a search term).
Do I need an account with Open Brewery DB?
No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Open Brewery DB data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?
As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?
No. Each run replaces the table, so it never holds two copies of the same row.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference

Connector openbrewerydb, version 0.1.0, a REST source, status stable, authentication none.

Vendor documentation: https://www.openbrewerydb.org/documentation

Configuration

KeyLabelTypeRequired
search_termBrewery search termstringyes

Resources

ResourceStatusPlanWritePrimary keyOverrides
breweries
All breweries in the directory — 11,848 records, proven via GET /breweries/meta, comfortably inside the 100k one-run batch cap, so a `full` plan completes each run.
stablefullreplaceid-
breweries_search
Breweries matching the customer's search term, returned whole in one full run. A subset of `breweries`, narrowed at the API rather than in the warehouse.
stablefullreplaceid-

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Get Open Brewery DB data into your warehouse

Last updated .