Introduction

A quick overview of hotglue

What is hotglue?

hotglue enables you to offer native, user-facing SaaS integrations to your customers in minutes without sacrificing control over the data.

hotglue is embeddable, cloud-based, and built on the Python ecosystem — enabling developers to support more data sources, manage data cleansing & transformation, and offer a self-serve experience to their users. With hotglue, any developer can build a data integration pipeline in minutes without months of development and maintenance.


What's different about hotglue?

Open source connectors

All of hotglue's connectors (taps) are completely open source and based on the Singer spec for creating connectors to 3rd party systems. There are already hundreds of connectors available created by open source contributors – including hotglue.

We are partnered with Meltano which is creating a community around the Singer spec to create well-maintained connectors to every 3rd party system you can imagine. In our view, the only way to keep integrations updated with the latest SaaS platforms and other data sources is via an open source community of developers. This vision is already being realized (as of April 2021, the Meltano community has exceeded 1,000 members).

Interesting, but why should I care?

One of the biggest reasons developers are (rightly) opposed to using an integration platform is because they want to avoid blockers when shipping new features (and integrations). For example, if your users want an integration with a platform hotglue doesn't support, you likely don't want to wait for the hotglue team to add it to their roadmap.

Since hotglue is based on Singer, you could easily create a new Singer tap yourself (for instance, using the Singer SDK). This way your team is assured you can ship new integrations leveraging the hotglue platform, without waiting on our team. Pretty cool, right?

Stateful integrations

hotglue was designed to correlate data across 3rd party systems. For example, hotglue makes it easy to sync Quickbooks Invoices and Salesforce Opportunities, and programmatically match each opportunity to an invoice.
This type of behavior is possible because hotglue's integrations are stateful – developers have access to a full picture of a user's data through snapshots. This makes it easier to build complex integrations while relying on hotglue to deal with orchestration, data integrity, and more.

Handles non-standardized APIs

SaaS APIs are far from unified – extract the data you need before it reaches your product. hotglue comes with a Python-based transformation layer, so developers can write simple transform scripts to standardize data before it gets to your backend.

hotglue jobs + standardizing datahotglue jobs + standardizing data

hotglue jobs + standardizing data


What are embedded integration (iPaaS) platforms?

Embedded integration platforms enable developers to build native integrations faster and more scalably by sitting within your product. End users connect their data sources within your web app, but the iPaaS handles authentication with the 3rd party system and orchestration of data syncs.

Extract

hotglue leverages open source Singer taps to securely provide access to the most popular data sources out of the box. From Salesforce to HubSpot, we've got you covered.

Through the hotglue widget, you can provide users with a simple self-serve interface to connect their data sources to your app with just two lines of code.

Read more about how extraction is handled in the hotglue platform here.

Load

All data from your configured Singer taps is moved to Python processing and consumption by your application. Data never leaves your cloud environment, so your data is safe every step of the way.

Transform

hotglue enables developers to leverage the Python ecosystem to compose transformation scripts. Built with developers in mind, hotglue combines the power of Python modules like Pandas and Dask with the power of AWS, all in a simple always-ready workspace powered by JupyterLab.

Read more about the benefits of the embedded integration paradigm here.


Did this page help you?