Build once. Deploy AI across
every user surface.
A Surface is where your AI product meets your users — on your site, in Slack, over SMS, via API, inside AI tools, and more. Reuse the same logic, tools, memory, and workflows across every surface without rebuilding from scratch.
Deploy native AI experiences across customer channels, internal workflows, developer interfaces, and agent ecosystems.
Your users live across channels. Your AI should too.
Most teams treat every channel like a separate product. One build for chat. Another for API. Another for internal workflows. Runtype gives you one system for all of it. Define your agents, workflows, tools, and memory once — then deploy them natively across the surfaces that matter.
Build once
Reuse the same core product across every surface.
Deploy natively
Give users experiences that feel right for each channel.
Expand faster
Launch new surfaces without rebuilding your stack.
One product. Many surfaces.
At the center is your Runtype product: agents, workflows, tools, memory, and evals. From there, deploy to any surface. The interface changes. Your product logic stays consistent.
Choose the right surface for every interaction.
Different users need different entry points. Meet them where they already are — whether that means a customer on your site, a team in Slack, a developer in code, or an agent inside an AI workflow.
Web Chat
Turn any site into an AI product. Launch a native chat experience on your website, storefront, or app for support, discovery, onboarding, and conversion.
Launch web chatSlack
Bring your agent into team workflows. Deploy AI where your team already works for internal support, ops, approvals, and workflow automation.
Launch in SlackConfirmed! Dr. Lee at 3:00 PM today. Reply CHANGE to reschedule.
SMS
Reach users on a high-attention channel. Create fast, direct AI interactions for updates, reminders, support, and lightweight workflows.
Launch over SMSRun AI workflows asynchronously. Let users and systems interact with your product through email-based triage, follow-up, and automation.
Launch with emailSchedule
Automate recurring work. Trigger agents and workflows on a schedule for reports, monitoring, summaries, follow-ups, and routine operations.
Create scheduled workflowsAPI
Make your product programmable. Expose your AI product to developers and systems through a clean programmatic surface.
Use the APIWebhook
Connect to event-driven systems. Trigger actions and workflows when something happens in your stack, without manual orchestration.
Use webhooksMCP
Make your product usable inside AI tools. Expose tools, flows, and agents through MCP so your product can work inside AI assistants and IDEs.
Launch with MCPA2A
Connect your agents to the agent ecosystem. Consume external agents or publish your own so systems can collaborate across boundaries.
Explore A2ANot channel integrations. Product surfaces.
Runtype is not a bundle of disconnected channel integrations. It is one AI product layer that can be deployed across many surfaces. Your prompts, workflows, tools, memory, and business logic stay consistent. The interface changes to fit the surface.
Shared logic
Keep product behavior consistent across every surface.
Native UX
Adapt the experience to the context of each channel.
Faster launches
Start with one surface, then expand without rebuilding.
Centralized control
Manage your AI product from one system instead of stitching together separate tools.
From customer channels to agent ecosystems.
Customer experiences
Launch web chat, SMS, and email surfaces for support, commerce, onboarding, and engagement.
Internal operations
Deploy into Slack and scheduled workflows for team productivity, reporting, and approvals.
Developer access
Expose your product through APIs and webhooks for programmatic access and event-driven automation.
AI-native distribution
Use MCP and A2A to make your product available inside AI tools and connected agent ecosystems.
Start with one surface. Expand to the rest.
Build your product
Define your agents, workflows, tools, and memory.
Choose a surface
Pick the interface your users already use.
Expand over time
Deploy the same product to additional surfaces without rebuilding.
You do not need to launch everything at once. Start with the surface that fits your users today, then deploy to more as your product grows.