Hi HN, we’re Hassan and David from hotglue (https://hotglue.xyz). We make it easier for developers to build user-facing integrations. In this context, an integration is a way for users to sync their data from their business apps, like Salesforce and Quickbooks, to another. For example, if I wanted to use an app like Mailchimp, I’d use their Salesforce integration to sync all my contacts over automatically.

We came across this problem while working for a startup that was struggling to scale the Salesforce integration they built in house. We needed a tool that would sync the customer data from Salesforce directly to our backend, but there were very few solutions available. After talking to other engineers who had dealt with user-facing integrations, we found many teams were frustrated by building their own integration solutions from scratch (not to mention maintaining them). This inspired us to build a tool that helps engineering teams add integrations to their products without taking on more tech debt.

Often people are surprised this isn’t solved yet – what about all the data movement tools like Meltano, Airbyte, Fivetran, Stitch, etc.? The difference here is that the integrations we're talking about are not back-end things like pulling your own Google Analytics data to BigQuery so that in-house analysts can work on it. Rather, it’s things like importing a user’s Quickbooks or Salesforce data into your product so that your product becomes more useful to them. That’s what we mean by “user-facing”.

There are a few reasons why building such integrations in-house is tricky. SaaS platforms and their APIs vary widely—while products like Stripe offer stellar APIs and resources, other platforms run on legacy software requiring more involved integrations (such as closed-access APIs or legacy SOAP/XML systems). Second, reliability while syncing at scale can be a challenging task when onboarding users with higher volumes of data – no engineer wants to spend their weekend debugging why their infra crapped out. Lastly, building auth flows and handling API tokens can be cumbersome: catching permission errors and expired tokens can take hours of debugging when dealing with the more "enterprisey" business products.

In short: it’s a pain to have to build one of these for several different apps, and not the sort of thing anybody wants to specialize in. Projects to build these usually end up on the back burner, frustrating customers who expect your product to integrate cleanly with all their other business apps.

We make it easier to build user-facing integrations by providing a scalable framework that minimizes maintenance. Our integrations are built on open source Singer.io connectors that eliminate the need for you to directly interface with APIs (saving you from dealing with breaking API changes, rate limits, authorization, and more). We provide a catalog of all the data each source provides and allow you to pick the data you need without having to grok long API docs. This also means you aren't locked in to our library of connectors – you can write your own connectors in Python. From there, we orchestrate syncing data for you. Just set a schedule, or kick off a job via our API – we provide the infrastructure, so you don't need to worry about building a data pipeline from scratch.

Although we are minimizing the dev work to build an integration, we are *not* a no-code solution. In our experience, no-code tools can be powerful for simple use cases, but are often too restrictive to handle custom logic. hotglue features a Python transformation layer to enable you to manipulate the raw data from third-party apps before it gets to your backend, cherry-pick the data you need, and implement more complex logic. For example, you can join multiple tables, filter out data based on a complex expression, make API requests, write custom logic for specific users, and more.

We are super excited to share hot...