For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
  • Evals
    • What are Evals?
    • Running an Eval
  • Schedules
    • What are Schedules?
  • Logs
    • What are Logs?
  • Integrations
    • Connecting AI model providers
  • Settings
    • What's in Settings?
    • Available AI models
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
Dashboard
LogoLogo
On this page
  • How Products work
  • Example: Customer Support Product
  • Next steps
Products & Surfaces

What are Products?

Was this page helpful?
Previous

What are Surfaces?

Next
Built with

Products are the home for your AI Capabilities — your Flows and Agents — and the Surfaces that make them available to the world. Think of a Product as the bridge between what you’ve built and how people use it.

How Products work

A Product bundles related AI Capabilities together and deploys them through one or more Surfaces. Instead of deploying each Flow or Agent individually, you group them into a Product and choose how users interact with them.

Every Product has two key parts:

  • Capabilities — The Flows and Agents you want to make available. Each Capability gets a name and optional description, making it easy to organize what your Product can do.
  • Surfaces — The channels through which users access your Capabilities. Runtype supports messaging channels like Slack and Email, so you can connect directly to the platforms your users already rely on.

Each Surface has its own status (draft, active, or paused) and environment (development or production), so you can test safely before going live.

Example: Customer Support Product

Maya runs support for a SaaS company and wants to automate common workflows without losing the human touch on complex issues. She creates a Customer Support Product with three Capabilities:

  • FAQ answering Flow — Handles common questions using her documentation as context
  • Ticket routing Agent — Analyzes incoming requests and assigns them to the right team based on topic and sentiment
  • Documentation search Flow — Retrieves relevant help articles when questions go beyond the FAQ

Her customers reach out through different channels, so she adds Surfaces to the same Product:

  • Chat Widget — Embedded on her website for instant answers
  • REST API — Powers the support interface in her mobile app
  • Email channel — Receives support requests and delivers answers directly via email

She sets each Surface to active in the production environment, and her team starts seeing results right away — faster response times and fewer repetitive tickets in the queue. Later, she adds a sentiment analysis Capability to flag frustrated customers for immediate escalation, all within the same Product.

A single Flow or Agent can be added as a Capability in multiple Products. For example, a “summarize text” Flow might be part of your Customer Support Product, your Content Creation Product, and your Research Assistant Product.

Next steps

  • Creating a Product
  • What are Surfaces?
  • Quickstart: From Flow to Live Surface