Why Prismatic?

What is Prismatic?

Prismatic is a dev-first integration platform that makes it easier for B2B software companies to build, deploy, and support integrations for their customers.

It addresses the hardest integration pain points so software teams can spend less time on integrations and more time on core product innovation.

Prismatic is a solution for the real world. It is designed to handle messy, complex integration scenarios and work with existing development and deployment toolchains. It is flexible and extensible, and can be used to build bespoke and vertical-specific integrations between applications of all kinds, SaaS or legacy, with or without a modern API, regardless of protocol or data format.

Who uses Prismatic?

Short answer

B2B (business-to-business) software companies, meaning software companies that provide applications used by businesses. It's a good fit for products/teams at any stage, including early stage SaaS, established SaaS, and legacy or on-prem systems.

Long answer

There are plenty of integration platforms on the market that help individuals or small teams automate their own workflows, or help IT teams build integrations between applications used within the business. However, these typically aren't fitting solutions for B2B software teams that need to provide integrations to their customers.

Prismatic addresses the specific challenges that come with providing integrations to business customers, including:

  • The need to integrate applications of all kinds (including vertical-specific apps that nobody outside your industry has heard of).
  • The need to use all kinds of protocols and data formats (the real world isn't full of pristine REST APIs) and to handle all kinds of non-standard integration scenarios (whatever additional twists customers or third-party vendors throw your way).
  • The need to deploy integrations to one or more customers, with customer-specific configurations.
  • The need to support multiple versions of an integration in production and roll out version upgrades.
  • The need to get customers and third-party vendors on the same page about what will be built and how, and iterate quickly when specs inevitably change.
  • The needs inherent to working in a professional development environment: for integrations to be discoverable and maintainable, for new tools to integrate with your existing toolchain, for everything to be scriptable, and so on.

Not just for devs

Prismatic was built with developers at the forefront, but is also a solution for the whole organization. Providing integration tools and data to non-dev teams - like onboarding, support and sales - helps those groups do their jobs more easily, with the bonus of reducing integration burden on dev teams.

Features

Prismatic aims to help teams spend less time building, deploying, and supporting integrations - or working on integration tooling, for that matter - so we designed to be a complete toolkit with everything built in. Here's a quick list of its top features:

  • Integration designer: Create integrations ranging from simple and standard to complex and bespoke, all in one place. Testing is built in so you can iterate quickly.
  • Customer deployment management: Cleanly handle the complexities of customer deployment, customer-specific configuration, and versioning.
  • Logging, monitoring, and alerting: Easily get a view of everything happening with your integrations and get notified when something goes wrong.
  • Component catalog: Write less repetitive boilerplate. Assemble integrations using pre-built components to handle the vast majority of your integrations' logic and connect to common third-party applications.
  • Custom component library: Write your own reusable custom components to handle any integration scenario.
  • No infrastructure: Don't spend time standing up and maintaining infrastructure. Your integrations run in Prismatic's purpose-built environment.
  • Embeddable customer portal: Empower customers with tools to manage their own integrations, like logging, monitoring, alerting, documentation, and an integration app store.
  • Dev friendly: Everything was designed to be be flexible, extensible, and integrate with your existing systems for source control, CI/CD, unit testing, and more. The API, CLI, and libraries let you interact with the platform in whatever way is most efficient for you.
Last updated on