OrgX separates default production processors from optional feature-triggered providers. A given workspace usually uses only the subset tied to its enabled plan, connectors, model policy, support path, and automation settings.
Last updated June 24, 2026
Providers normally involved in operating the OrgX application, workspace data plane, authentication, billing, email, model routing, and durable workflow execution.
Core infrastructure
Purpose
Application hosting, server runtime, and production service operations.
Data categories
Application traffic, operational metadata, server logs, and workspace data handled by the running service.
Use trigger
Used when a customer accesses the production OrgX application or agent runtime.
Controls
Access-limited production operations, monitored deployment path, encrypted transport, and controlled administrative access.
Core data plane
Purpose
Managed Postgres, storage, realtime features, and workspace persistence.
Data categories
Workspace records, artifacts, memory, run metadata, audit records, attachments, and account-linked identifiers.
Use trigger
Used for persisted workspace features, exports, auditability, realtime updates, and storage-backed product flows.
Controls
Encryption at rest where supported, row-level security, scoped service access, backups, and migration review.
Core perimeter
Purpose
DNS, CDN, DDoS mitigation, WAF, TLS edge handling, and cache controls.
Data categories
Network metadata, request metadata, client network identifiers, headers, and security event telemetry.
Use trigger
Used when customers, reviewers, browsers, or clients access OrgX public or app surfaces.
Controls
Traffic filtering, rate limiting, TLS enforcement, cache purges, and security event review.
Core identity
Purpose
Hosted authentication, user identity, sessions, account access, and sign-in flows.
Data categories
Account identifiers, verified emails, session metadata, authentication events, and identity provider metadata.
Use trigger
Used when a user signs in, maintains a session, accepts an invite, or authorizes an identity-bound workflow.
Controls
Session isolation, email verification, signed identity handoff, scoped auth callbacks, and account-level controls.
Core workflow runtime
Purpose
Durable task execution, scheduled jobs, background workers, retries, and deployment of task code.
Data categories
Workflow events, task identifiers, run metadata, job payload references, status, retry metadata, and execution logs.
Use trigger
Used for production background jobs and scheduled task execution where Trigger.dev is the active queue backend.
Controls
Scoped payloads, environment-specific signing, retry boundaries, deployment checks, and job status review.
Workflow runtime
Purpose
Event-driven workflows, scheduled jobs, retries, and legacy or transitional background processing.
Data categories
Workflow event names, run identifiers, scoped job payloads, retry metadata, and execution status.
Use trigger
Used where an OrgX workflow is still routed through Inngest or where a feature explicitly uses Inngest execution.
Controls
Signed events, scoped payloads, replay controls, retry limits, and environment-specific configuration.
Billing processor
Purpose
Payments, checkout, billing portal, invoices, tax, receipts, subscriptions, and refunds.
Data categories
Buyer contact details, billing metadata, invoice records, payment status, checkout session data, and subscription records.
Use trigger
Used when a customer starts checkout, manages billing, redeems paid access, receives invoices, or requests a billing change.
Controls
PCI-scoped payment handling, webhook verification, no full payment card storage in OrgX systems.
Email processor
Purpose
Transactional email, invites, account notices, support follow-ups, and customer notifications.
Data categories
Recipient email, sender metadata, template variables, delivery status, bounce events, and message metadata.
Use trigger
Used when OrgX sends account, invite, support, lifecycle, or notification emails.
Controls
Template review, delivery logging, unsubscribe handling where applicable, and payload minimization.
Model provider
Purpose
Model inference for selected agent reasoning, generation, review, classification, and chat workflows.
Data categories
Prompts, task context, uploaded or linked artifact text, generated outputs, and model-routing metadata.
Use trigger
Used when a workspace route, agent, or enabled feature selects OpenAI as the model provider.
Controls
Provider routing policy, prompt minimization, workspace model controls, and no intentional submission of secrets.
Model provider
Purpose
Model inference for selected agent reasoning, generation, review, classification, and code-adjacent workflows.
Data categories
Prompts, task context, uploaded or linked artifact text, generated outputs, and model-routing metadata.
Use trigger
Used when a workspace route, agent, or enabled feature selects Anthropic as the model provider.
Controls
Provider routing policy, prompt minimization, workspace model controls, and no intentional submission of secrets.
Providers that may receive operational, diagnostic, product-analytics, source-control, or release metadata needed to keep OrgX reliable.
Error monitoring
Purpose
Application error capture, stack trace grouping, release health, and incident triage.
Data categories
Error metadata, route context, browser/runtime metadata, stack traces, release identifiers, and limited diagnostic context.
Use trigger
Used when application monitoring is enabled and a client or server error is captured.
Controls
PII minimization, scrubbed diagnostics where practical, retention review, and restricted engineering access.
Product analytics
Purpose
Product analytics, activation funnel measurement, telemetry, feature usage, and reliability diagnostics.
Data categories
Event names, page paths, workspace or account identifiers where configured, feature flags, and interaction metadata.
Use trigger
Used for product analytics where enabled by environment and workspace or surface configuration.
Controls
Consent-aware telemetry paths, event minimization, no payment card data, and no intentional secret capture.
Build and preview operations
Purpose
Deployment previews, build metadata, analytics libraries, edge-compatible tooling, and release operations where configured.
Data categories
Build logs, deployment metadata, preview URLs, route metadata, and limited operational telemetry.
Use trigger
Used for preview, release, analytics, or build workflows that are configured to use Vercel services.
Controls
Environment separation, secret-scrubbing expectations, preview access controls where available, and release review.
Source and workflow operations
Purpose
Source control, pull requests, CI checks, issue links, security review, and customer-authorized repository workflows.
Data categories
Repository metadata, pull request URLs, commit metadata, issue metadata, workflow status, and user-authorized code context.
Use trigger
Used for OrgX release operations and when a customer authorizes GitHub-backed agent or proof workflows.
Controls
Repository permissions, GitHub App or OAuth scopes, branch protections, CI checks, and review gates.
Rate-limit and queue utility
Purpose
Rate limiting, cache, queue, or request coordination utilities where enabled.
Data categories
Request counters, hashed or scoped identifiers, queue metadata, and limited operational state.
Use trigger
Used only for features or environments configured to route through Upstash-backed utilities.
Controls
Scoped keys, short-lived operational data where practical, and no intentional storage of customer secrets.
Providers that are not used for every workspace. They may process customer data only when a user, workspace, feature flag, connector, or automation explicitly uses that capability.
Customer-authorized connector
Purpose
Issue, project, roadmap, and work-graph synchronization.
Data categories
Issue titles, descriptions, project metadata, comments, labels, status, assignee metadata, and linked OrgX work context.
Use trigger
Used only when a workspace authorizes Linear or asks OrgX to operate against Linear data.
Controls
OAuth or API-token scopes, connector revocation, workspace access checks, and connector-specific permission review.
Customer-authorized connector
Purpose
Workspace messaging, notifications, incident updates, and approval or collaboration workflows.
Data categories
Channel identifiers, user identifiers, message content selected by the workflow, timestamps, and delivery metadata.
Use trigger
Used only when a workspace authorizes Slack and configures Slack-backed workflows.
Controls
OAuth scopes, channel selection, approval policies, connector revocation, and message payload minimization.
Customer-authorized connector
Purpose
Document, page, database, and knowledge-base synchronization.
Data categories
Selected pages, database records, titles, properties, comments, and linked OrgX context.
Use trigger
Used only when a workspace authorizes Notion and selects Notion-backed workflows.
Controls
OAuth scopes, page/database permission boundaries, revocation, and workspace access checks.
Customer-authorized connector
Purpose
Gmail, Calendar, Drive, Docs, Sheets, or Slides workflows requested by the user.
Data categories
Selected emails, calendar events, Drive files, document content, spreadsheet ranges, slide content, and related metadata.
Use trigger
Used only when a user authorizes a Google capability and requests a Google-backed workflow.
Controls
OAuth scopes, user consent, revocation, least-privilege connector setup, and workflow-specific data minimization.
Customer-authorized connector
Purpose
Design file inspection, design-to-code workflows, design system review, and asset generation workflows.
Data categories
Selected design files, screenshots, node metadata, component names, annotations, and asset references.
Use trigger
Used only when a user connects Figma or asks OrgX to inspect or update a Figma design.
Controls
OAuth scopes, selected-file access, revocation, and design-workflow review boundaries.
Research provider
Purpose
Web research, page extraction, browser automation, and public web evidence collection.
Data categories
URLs, search targets, public page content, browser-session metadata, and user-supplied research instructions.
Use trigger
Used only when a workflow requests web research, public page capture, or browser-backed evidence gathering.
Controls
Public-source preference, payload minimization, no intentional submission of secrets, and task-scoped use.
Research provider
Purpose
Search, discovery, citation retrieval, and public-source research.
Data categories
Search queries, URLs, public-source snippets, organization names, and research context.
Use trigger
Used only when a feature or agent workflow requests external search or discovery.
Controls
Public-source preference, query minimization, and task-scoped use.
Media generation provider
Purpose
Image, video, or creative asset generation for selected creative workflows.
Data categories
Generation prompts, selected source images or references, output assets, and workflow metadata.
Use trigger
Used only when a user requests media generation through an enabled creative workflow.
Controls
User-directed generation, prompt review, no intentional secret submission, and asset provenance tracking where available.
Media generation provider
Purpose
Voice generation, narration, and audio rendering for selected creative workflows.
Data categories
Script text, voice settings, generated audio, and media workflow metadata.
Use trigger
Used only when a user requests voice or audio generation through an enabled workflow.
Controls
User-directed generation, content review, no intentional secret submission, and workflow-level provenance.
Research and outreach provider
Purpose
Lead research, enrichment, and outbound workflow support where configured.
Data categories
Company names, public contact metadata, search criteria, enrichment results, and campaign metadata.
Use trigger
Used only for customer-authorized or internal GTM workflows that explicitly enable Apollo-backed enrichment.
Controls
Campaign review, no automatic send without configured approval, scoped API credentials, and suppression/dedupe checks.
Advertising and conversion provider
Purpose
Advertising status checks, conversion event review, and campaign diagnostics where configured.
Data categories
Campaign identifiers, ad account metadata, conversion metadata, and diagnostics for configured marketing workflows.
Use trigger
Used only when a customer or internal workflow authorizes Meta advertising or conversion tooling.
Controls
Scoped tokens, campaign approval gates, no payment-card processing by OrgX, and marketing workflow review.
Optional model provider
Purpose
Model inference for selected research, classification, or generation workflows where configured.
Data categories
Prompts, search or research context, generated outputs, and model-routing metadata.
Use trigger
Used only when a workspace or feature explicitly routes a task to an xAI-backed model.
Controls
Provider routing policy, prompt minimization, workspace controls, and no intentional secret submission.
Change notices
Review path