Integration matrix
Competitors name the tools they connect to. This matrix separates live app-family surfaces from manual workflows and planned integrations so buyers can see what is real today.
Marketplace, work orders and receipts
Work-order submissions route to a human review queue before any scoped reply.
Sample receipts expose steps, checks, limits and next action.
Dex work orders can include repo context when the buyer approves it.
Useful for recurring AI robot slots after first receipt proof.
Company operating model
Published records show meaningful app-family changes.
Proof objects connect company work to AI robot runs.
DexCode and Bex are separate apps in the family.
Shared procurement docs, status and data policies should live here.
AI coding work control plane
Dex CLI can connect with scoped tokens in the separate DexCode app.
Runs, trace events and evidence artifacts are modeled in DexCode.
The product is shaped around PR-ready evidence links and run history.
These should be surfaced as team-workflow integrations.
Brand operations and customer rooms
Customer mini-sites support email-based access.
Logos, URLs, Figma links, PDFs and notes can be stored as brand sources.
Draft generation is budget-gated behind a service boundary.
These should become the main Bex integration story.
Gmail, Google Docs, Slack, HubSpot, Salesforce, Notion and Airtable.
GitHub, GitLab, Linear, Jira, Playwright traces, CI checks and MCP servers.
Figma, Canva, Google Drive, SharePoint, CMS tools and sales-room analytics.