Skip to main content

Custom Domains

Feature Availability

The custom domains feature is available to customers on specific pricing plans. Refer to your pricing plan or contract, or contact the Prismatic support team for more information.

You can configure access to the Prismatic platform to operate through a custom domain that you control. For example, you might want to white-label Prismatic so your team members and customers access https://integrations.your-company.com instead of https://app.prismatic.io.

To configure a custom domain, please contact our support team, and specify the subdomain (like https://integrations.your-company.com) you would like to use. Setup is a three-step process:

  1. We'll create an SOA record for that subdomain and provide you with a list of four nameservers.

  2. After we prepare those records, you'll need to create an NS record pointing to the list of nameservers we provided. Note: Some DNS providers represent nameserver lists as separate NS records (one server per record), while others use single NS records with multiple values.

    Verify that your NS records propagate correctly by entering your custom subdomain in a tool like DNS Checker or by using the dig command:

    dig NS integrations.your-company.com +short

  3. After you create the NS records, notify the Prismatic support team so we can finalize the setup on our end. We'll verify the DNS records and issue an SSL certificate for your domain. We'll also create several A and CNAME records for web app access, webhook invocation, OAuth 2.0 callbacks, MCP, and on-prem agent connectivity:

    • https://integrations.your-company.com - web app and embedded URL
    • https://hooks.integrations.your-company.com - webhooks
    • https://oauth2.integrations.your-company.com - OAuth 2.0 callback
    • https://mcp.integrations.your-company.com - MCP endpoint for agent flows
    • https://onprem.integrations.your-company.com - on-prem agent connectivity

    Note: Prismatic will handle all additional DNS records for these services; you don't need to create any.

Once your domain is white-labeled, your OAuth 2.0 applications can use https://oauth2.integrations.your-company.com/callback as a callback URL.

Webhook and OAuth 2.0 URLs are derived from the URL you visit

Once a subdomain is configured, you can access your tenant through either the custom domain or the default Prismatic domain. Custom domains are not tenant-specific. If you have production and development tenants, both tenants can use the custom domain you establish.

  • If you access or embed Prismatic via https://app.prismatic.io, you will see webhook and OAuth URLs with the Prismatic domain.
  • If you access or embed Prismatic via your custom domain like https://integrations.your-company.com, you will see webhook and OAuth URLs with your custom domain.