HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pontoon-data
Pontoon
Python2025–2025
pontoon-data / Pontoon

Pontoon

Open source data export platform. For devs who ship data to their customers 🚀

3Distinct people
3Mentions
0Explicit recommenders
244GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open source data export platform. For devs who ship data to their customers 🚀

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval3 dated mentions

Observed mentions: 2025-07-30 12:29:25 UTC to 2025-08-02 02:34:15 UTC.

012025-07-30 12:00:00 UTC to 2025-07-30 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 30, 12:002025-07-30 15:00:00 UTC to 2025-07-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-30 18:00:00 UTC to 2025-07-30 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-30 21:00:00 UTC to 2025-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 00:00:00 UTC to 2025-07-31 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 03:00:00 UTC to 2025-07-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 06:00:00 UTC to 2025-07-31 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 09:00:00 UTC to 2025-07-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 12:00:00 UTC to 2025-07-31 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 15:00:00 UTC to 2025-07-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 18:00:00 UTC to 2025-07-31 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 31, 18:002025-07-31 21:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-08-01 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 03:00:00 UTC to 2025-08-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 06:00:00 UTC to 2025-08-01 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 09:00:00 UTC to 2025-08-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 12:00:00 UTC to 2025-08-01 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 15:00:00 UTC to 2025-08-01 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-08-01 18:00:00 UTC to 2025-08-01 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 21:00:00 UTC to 2025-08-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-02 00:00:00 UTC to 2025-08-02 03:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 2, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 30, 12:002025-07-30 12:00:00 UTC2025-07-30 15:00:00 UTC110
Jul 30, 15:002025-07-30 15:00:00 UTC2025-07-30 18:00:00 UTC000
Jul 30, 18:002025-07-30 18:00:00 UTC2025-07-30 21:00:00 UTC000
Jul 30, 21:002025-07-30 21:00:00 UTC2025-07-31 00:00:00 UTC000
Jul 31, 00:002025-07-31 00:00:00 UTC2025-07-31 03:00:00 UTC000
Jul 31, 03:002025-07-31 03:00:00 UTC2025-07-31 06:00:00 UTC000
Jul 31, 06:002025-07-31 06:00:00 UTC2025-07-31 09:00:00 UTC000
Jul 31, 09:002025-07-31 09:00:00 UTC2025-07-31 12:00:00 UTC000
Jul 31, 12:002025-07-31 12:00:00 UTC2025-07-31 15:00:00 UTC000
Jul 31, 15:002025-07-31 15:00:00 UTC2025-07-31 18:00:00 UTC000
Jul 31, 18:002025-07-31 18:00:00 UTC2025-07-31 21:00:00 UTC000
Jul 31, 21:002025-07-31 21:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 1, 00:002025-08-01 00:00:00 UTC2025-08-01 03:00:00 UTC000
Aug 1, 03:002025-08-01 03:00:00 UTC2025-08-01 06:00:00 UTC000
Aug 1, 06:002025-08-01 06:00:00 UTC2025-08-01 09:00:00 UTC000
Aug 1, 09:002025-08-01 09:00:00 UTC2025-08-01 12:00:00 UTC000
Aug 1, 12:002025-08-01 12:00:00 UTC2025-08-01 15:00:00 UTC000
Aug 1, 15:002025-08-01 15:00:00 UTC2025-08-01 18:00:00 UTC110
Aug 1, 18:002025-08-01 18:00:00 UTC2025-08-01 21:00:00 UTC000
Aug 1, 21:002025-08-01 21:00:00 UTC2025-08-02 00:00:00 UTC000
Aug 2, 00:002025-08-02 00:00:00 UTC2025-08-02 03:00:00 UTC101

What Hacker News says

3 sources
> Open source: Pontoon is free to use by anyone And yet, the top level license file contains two licenses, a goddamn if statement, and finally a default to Elastic License which is not open source Then, because if this trickery, lawyers get to make good money because does "2. LICENSE file in the same directory as the work" combined with "4. Defaults to Elastic License 2.0 (ELv2)" mean that this zero byte file NAMED LICENSE but devoid of any content match clause 2 or 4? https://github.com/pontoon-data/Pontoon/blob/v0.2.0/data-tra... I hate cutesy licenses with all my heart. Just say you want to use Elastic, drop the Open Source pretense, and go back to selling software instead of trying to position yourself as "open" No educated person is going to give you free commits in the current state so no need to be opaque in hopes of tricking them
In Show HN: Pontoon – Open-source customer data syncs
alexdriedger¡Aug 1, 2025Submission

Show HN: Pontoon – Open-source customer data syncs

Hi HN, We’re Alex and Kalan, the creators of Pontoon (https://github.com/pontoon-data/Pontoon). Pontoon is an open-source data export platform that makes it really easy to create data syncs and send data to your enterprise customers. Check out our demo here: https://app.storylane.io/share/onova7c23ai6 or try it out with docker: https://pontoon-data.github.io/Pontoon/getting-started/quick... While at our prior roles as data engineers, we’ve both felt the pain of data APIs. We either had to spend weeks building out data pipelines in house or spend a lot on ETL tools like Fivetran (https://www.fivetran.com/). However, there were a few companies that offered data syncs that would sync directly to our data warehouse (eg. Redshift, Snowflake, etc.), and when that was an option, we always chose it. This led us to wonder “Why don’t more companies
Read the rest
offer data syncs?”. It turns out, building reliable cross-cloud data syncs is difficult. That’s why we built Pontoon. We designed Pontoon to be: - Easily deployed: we provide a single, self-contained Docker image for easy deployment and Docker Compose for larger workloads (https://pontoon-data.github.io/Pontoon/getting-started/quick...) - Support modern data warehouses: we support syncing to/from Snowflake, BigQuery, Redshift, and Postgres. - Sync cross cloud: sync from BigQuery to Redshift, Snowflake to BigQuery, Postgres to Redshift, etc. - Developer friendly: data syncs can also be built via the API - Open source: Pontoon is free to use by anyone Under the hood, we use Apache Arrow (https://arrow.apache.org/) to move data between sources and destinations. Arrow is very performant - we wanted to use a library that could handle the scale of moving millions of records per minute. In the shorter-term, there are several improvements we want to make, like: - Adding support for DBT models to make adding data models easier - UX improvements like better error messaging and monitoring of data syncs - More sources and destinations (S3, GCS, Databricks, etc.) - Improve the API for a more developer friendly experience (it’s currently tied pretty closely to the front end) In the longer-term, we want to make data sharing as easy as possible. As data engineers, we sometimes felt like second class citizens with how we were told to get the data we needed - “just loop through this api 1000 times”, “you probably won’t get rate limited” (we did), “we can schedule an email to send you a csv every day”. We want to change how modern data sharing is done and make it simple for everyone. Give it a try https://github.com/pontoon-data/Pontoon. Cheers!
46 points ¡ Open discussion
kalanm¡Jul 30, 2025Submission

Show HN: Pontoon, an open-source data export platform

Hi HN, We’re Alex and Kalan, the creators of Pontoon (https://github.com/pontoon-data/Pontoon). Pontoon is an open-source data export platform that makes it really easy to create data syncs and send data to your enterprise customers. Check out our demo here: https://app.storylane.io/share/onova7c23ai6 or try it out with docker: https://pontoon-data.github.io/Pontoon/getting-started/quick... While at our prior roles as data engineers, we’ve both felt the pain of data APIs. We either had to spend weeks building out data pipelines in house or spend a lot on ETL tools like Fivetran (https://www.fivetran.com/). However, there were a few companies that offered data syncs that would sync directly to our data warehouse (eg. Redshift, Snowflake, etc.), and when that was an option, we always chose it. This led us to wonder “Why don’t more companies
Read the rest
offer data syncs?”. It turns out, building reliable cross-cloud data syncs is difficult. That’s why we built Pontoon. We designed Pontoon to be: - Easily deployed: we provide a single, self-contained Docker image for easy deployment and Docker Compose for larger workloads (https://pontoon-data.github.io/Pontoon/getting-started/quick...) - Support modern data warehouses: we support syncing to/from Snowflake, BigQuery, Redshift, and Postgres. - Sync cross cloud: sync from BigQuery to Redshift, Snowflake to BigQuery, Postgres to Redshift, etc. - Developer friendly: data syncs can also be built via the API - Open source: Pontoon is free to use by anyone Under the hood, we use Apache Arrow (https://arrow.apache.org/) to move data between sources and destinations. Arrow is very performant - we wanted to use a library that could handle the scale of moving millions of records per minute. In the shorter-term, there are several improvements we want to make, like: - Adding support for DBT models to make adding data models easier - UX improvements like better error messaging and monitoring of data syncs - More sources and destinations (S3, GCS, Databricks, etc.) - Improve the API for a more developer friendly experience (it’s currently tied pretty closely to the front end) In the longer-term, we want to make data sharing as easy as possible. As data engineers, we sometimes felt like second class citizens with how we were told to get the data we needed - “just loop through this api 1000 times”, “you probably won’t get rate limited” (we did), “we can schedule an email to send you a csv every day”. We want to change how modern data sharing is done and make it simple for everyone. Give it a try: https://github.com/pontoon-data/Pontoon. Cheers!
3 points ¡ Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.