Blog
Headless Configuration Is Now Generally Available
News & Updates

Headless Configuration Is Now Generally Available: Own the Integration Setup Experience in Your Product

Headless configuration is now generally available. Take full control of integration setup in your product with your own UI while Prismatic handles the logic.
Oct 27, 2026
Amrit Singh
Amrit SinghSenior Product Marketing Manager
Headless Configuration Is Now Generally Available
Key takeaways
  • Headless configuration gives you full control over the integration setup experience. Your product owns the marketplace, connect flow, and configuration pages, and Prismatic handles configuration state, validation, connections, dynamic data lookups, server functions, versioning, and lifecycle management underneath.
  • Extend your product with Prismatic-powered experiences built on your own UI. Today the headless SDK covers marketplace listings, connections, and configuration. Executions, logs, and other resources will follow.
  • Building your own UI is faster than ever with AI. Coding agents can quickly scaffold configuration pages and marketplaces, and Prismatic Skills give your agent the context it needs to build on the headless SDK.

Headless configuration is generally available today. You can now build the integration setup experience directly into your product with your own components, layout, and navigation. You decide how setup looks and works, and your customers configure integrations without leaving your product.

Your product handles the presentation. Prismatic handles everything behind the scenes: configuration state, validation, connections, dynamic data lookups, server functions, versioning, and lifecycle management.

We opened early access earlier this month. Thanks to everyone who built with it and is sending us feedback. The docs are live if you want to skip ahead.

Own the configuration experience

Presentation modes for configuration screenshot

Some teams want full control over how integration setup looks and behaves. Headless configuration gives you that: a setup experience that follows your design system, sits inside your navigation, respects your permissions model, and uses patterns your customers already know.

You can also build setup flows a standard form can't easily handle: conditional configs, data mapping, remote search, lists that only exist after connecting, and shared settings for individual users.

State management, validation, connection handling, and versioning make integrations reliable, and nobody wants to rebuild them to build their own setup experience. Headless configuration splits the job in two: the integration defines what needs configuring, and your product decides how your customers do it. Hosted means Prismatic renders the UI. Headless means your product does it. Our new headless SDK is what makes this possible.

Building custom UI is faster than it has ever been. A coding agent can scaffold a configuration page or a marketplace quickly, and that changes the math on owning the UI yourself. The headless SDK works well for that. Your team or your agent writes the front end, and Prismatic supplies the schema, server functions, and state underneath. Prismatic Skills give your agent the context to build with it.

The SDK that drives the configuration experience

Our new headless SDK (we call it Solis) provides the client-side primitives for building Prismatic-powered experiences. Your front end reads the configuration schema, calls server functions, and saves values. It doesn’t touch credentials or deployments, because Prismatic handles those for you.

Headless configuration is what the SDK unlocks today: marketplace listings, connections, and configuration in your own UI. Executions, logs, and other integration resources will follow, and everything you build on the SDK now carries forward as it grows.

Build the experience your customers need

Here's the shape of a headless integration:

  1. Define the integration behavior in Prismatic. Your code-native integration defines the configuration schema, connections, server functions, and runtime behavior in TypeScript, next to the rest of your integration code.
  2. Build the experience in your product. The headless SDK provides the schema, the server functions, and the save actions. You render the marketplace, the connect flow, and the config pages with your own components, layout, and navigation.
  3. Let Prismatic handle the plumbing. Prismatic manages state, validation, data lookups, connection handling, deployment, and versioning. Credentials stay on Prismatic, and your product only sees what a server function returns.

Follow Get Started with Headless Config to run a complete example end to end.

What you can build

One-click connect screenshot

A connect button beside the feature it powers. Some integrations don't need a marketplace page. A single "Connect your Outlook calendar" or “Connect your Slack” button next to the feature it powers can authenticate the account and set up the integration in place. You decide where the button lives and what happens after the click, and Prismatic creates the connection, the instance, and the deployment behind it. Build a one-click connect list. ​

Headless configuration screenshot

A fully custom marketplace and config flow. Put a catalog inside your existing navigation and design system, with your own browse, search, and connect experiences. Then build configuration pages a standard form can't express, like field mapping with a live preview, remote lookups as the user types, and steps that only appear once an earlier value is known. Prismatic keeps the state, validation, and versioning behind every page. Build a custom marketplace.

Is headless configuration right for you?

Hosted configuration gives you a working setup experience with no front-end work, and it's the right starting point for most teams. Headless configuration is for teams that want to own the setup UI themselves: your own layout, navigation, and interaction patterns, and configuration logic that goes beyond what a form can express. You'll need a code-native integration and front-end developers to build it.

Two things to keep in mind:

  1. Your product needs a custom marketplace or an equivalent experience, because the hosted marketplace can't support a headless configuration.
  2. Hosted configuration isn't changing. It's still the right choice when you'd rather not build a front end, and your marketplace can list hosted and headless integrations side by side.

Get started with headless configuration

Help shape what comes next

The headless SDK covers marketplace listings, connections, and configuration today, and we’re working out which experiences to make headless next. If there's a Prismatic experience you'd like to build into your product, let us know.

Share headless experience feedback

Get a Demo

Ready to make your product extensible?

Join teams from Fortune 500s to high-growth startups that turned integrations into a growth driver and made their products the foundation that customers build on.