Show HN: OpenInt (YC W23) Open-Source iPaaS to Ship Product Integrations Quickly

[amadeo_warden]

Hi HN, we’re the team behind OpenInt (https://openint.dev). We started building a unified API for crypto payments at Map3 (YC W23), but scaling dozens of custom integrations for each customer was painful and repetitive. We learned how valuable it would be to have a platform that lets any team quickly stand up private and fully controlled integrations without reinventing the wheel each time.

OpenInt is an open-source integration platform as a service (iPaaS) that helps you ship product integrations in hours, not weeks. We just participated Mega Launch Week (Dec 2–6 https://launchweek.dev/lw/MEGA) and introduced (https://openint.dev/launch-week):

- Dec 2: OpenInt – Open-source iPaaS platform.

- Dec 3: @OpenInt/Connect – Fully featured integrations page for your app.

- Dec 4: OpenInt Sync – Automated data syncs straight into your database.

- Dec 5: OpenSDKs – Typesafe SDKs with an auth proxy for any API.

- Dec 6: Orchestrate & Our Partner Program – Unified aggregator orchestration plus our partner ecosystem (initial ones are also other OSS YC companies).

We think the above makes OpenInt the LAST integration you’ll ever need. If there’s any connector missing, tell us about it, and either we or one of our partners will write it for you in 72h for $1000.

We went through Y Combinator W23 and are now fully committed to building an open ecosystem. The stack is mostly TypeScript on Cloudflare Workers with Postgres for storage—designed to be easy to run and scale on your own infra. Long term, we want to see open-source AI agents assist developers in auto-generating and maintaining integrations and SDKs, collaborating directly within the repo.

Here’s[1] a 1-minute demo video to show how fast you can launch an integration. Check out the integrations list, star our GitHub repos (OpenInt[2] | OpenSDKs[3]), or hop into our Slack community (signup via https://openint.dev) to say hi.

[1]: https://www.youtube.com/watch?v=FpG7otZZhRw

[2]: https://github.com/openintegrations/openint

[3]: https://github.com/openintegrations/openSDKs

We're not quite ready for a full Launch HN yet (hence the Show!), but we’d love your feedback—tell us what’s missing, where we can improve, or what you’d like to build with OpenInt!

[amadeo_warden]

Hi folks!

This is Amadeo, a long-time hacker news passive reader.

I wanted to share a little story on how we ended up working on OpenInt. As mentioned, we started at YC as Map3, building unified APIs for Crypto. This was right as FTX blew up, so we couldn't find enough traction! We then pivoted into creating a consumer health app called Ally. After 9 months on it and realizing we weren't solving a meaningful enough problem, we tacked back into open-source dev tools. Initially, we launched Evefan (same area) in September, but after finding our first couple of customers, we stumbled into another OSS project called OpenInt. We acquired it and rebranded it and have decided to build on it :) We're now helping our first customers ship integrations to their end users and have been thrilled by the reception so far!

I'll be lurking through the day! I would love any pointers on how to make it easier for folks to launch and maintain integrations.

[tonyx]

How does this compare to other open source integration platforms like Nango or Airbyte?

[amadeo_warden]

I should start by saying that we love Nango & Airbyte, rely on Nango for certain oAuth flows, and support Airbyte as a Connector! I'd say the main high-level differences are:

1. We're built for self-hosting / single-tenant mode and focus on customers with this need. Our data plane runs in a Cloudflare worker on our customer's Cloudflare account, so we never get access to the data.

2. Airbyte is mainly focused on internal ETL data movement. Nango also syncs data into their app DB while we enable you to plug in your DB to collocate it with your app data for easier joins.

3. We'd like to think that OpenInt sits at a higher level than a regular iPaaS as we replace the glue code you'd have to write to bring in traditional unified APIs. Imagine being able to plug in and use both a Plaid and a Yodlee with a unified UI/API. Let them focus on what they do best. Orchestrate aggregators so genuinely become the last integration you'll ever need. More: https://openint.dev/launch-week/introducing-orchestrate-and-...