Friction around integration and customization can be a major drag on your SaaS company's effectiveness and a significant source of lost opportunities. Market fit, adoption, and retention can suffer because customizing, extending, and integrating your SaaS is hard. Customer-specific features sometimes languish in the product backlog and never get done. Sales cycles can take long and opportunities are lost due to unique customer requirements or the need for IT to host the last mile of integration. Engineering is frequently unable to keep up with the stream of custom requirements coming from Sales and Product.

Fusebit is an extensibility and customization solution you can integrate in days with minimal changes to existing infrastructure. Increase sales and retention, while keeping your engineering team focused on the core product.

A SaaS product can leverage the Fusebit platform to easily enable the crucial integrations and customization capabilities that every mature SaaS product should offer. Traditionally, it has been assumed that these capabilities had to be natively built into a SaaS product, but this is not the case: these capabilities can be externalized as a separate service and embedded into the core SaaS product.

The Fusebit platform enables any SaaS product to host a set of embedded integrations that are tailored to the needs of the users of that SaaS. Integrations are small programs that exchange data between the SaaS product and third-party products or services. The target of the integration can be another SaaS product, an existing system, a legacy service, or pretty much any system that is accessible via HTTP. Another scenario enabled by the Fusebit platform is introducing embedded customizability to a SaaS product. This may be be useful in a scenario where each end customer of a SaaS product has unique requirements (transformations, rules, policies) that are complex enough to require a code-based solution. In this case, the customization code usually calls back into the SaaS product: consider an example where some customer-specific calculated fields are added to an object by the customization code, before the object is stored into SaaS product.

Both of the above scenarios are powered by Fusebit functions: small short-lived stateless services based on Node.js. Functions are written in JavaScript and have access to all public Node.js packages. A function can be triggered by an event in your SaaS (the same point where your code might normally trigger a webhook call), by an event in the integration target system, or at a regular time interval (scheduled/cron execution). The function code can be authored in two ways: via the embeddable Fusebit editor (for less technical users) or via the Fusebit command-line tool (CLI).

Functions are grouped into logical boundaries, where functions within a boundary are guaranteed to execute in isolation of functions in other boundaries. This capability allows the SaaS provider to set up an architecture that optimizes security and reliability for their specific scenario.

Functions and boundaries are managed via the Fusebit HTTP API. For convenience, the Fusebit CLI also offers support for all management operations supported by the API. The HTTP API is secured via a sophisticated authorization model, which determines what operations each user has access to. The authorization model layers on top of your existing methods of identifying users, whether you are using Google, Auth0, or even a custom identity platform.

The documentation provided here allows you to get started quickly and will be a valuable reference as you develop your solution with Fusebit.

Integrator Guide - Integrate Fusebit into your SaaS product

Authoring Guide - Author and manage Fusebit functions

Reference - API reference for the Fusebit platform

  • HTTP API Reference - Learn about the Fusebit HTTP API

  • Editor API Reference - Customize the embedded Fusebit Editor

  • CLI Reference - The Fusebit Command Line Interface (CLI)

So glad to have you onboard. Ready, set, go!

Whatโ€™s Next