Back to blog

PERSONAL, FAMILY, TEAM, ENTERPRISE

Integrations in the pilot: what is truly available today

A transparent map of available, planned, and intentionally paused connectors for pilots.

July 24, 20261 min readFleet architecture and productHow this maps to features

Share this article

integrationssecurityroadmappilot scope

Key pain points addressed

  • Teams plan on integrations that do not exist.

  • Connector capability claims overpromise and create adoption debt.

  • Teams copy a plan that collapses when security checks appear late.

FleetRun intentionally separates what is shipped from what is planned.

Available today (pilot)

  • Google Workspace: read-only core tools, plus approval-gated draft workflows.
  • Slack: public-channel discovery and bounded history reads.
  • Notion: title-based search and constrained read helpers.

Planned or in development

  • Browser automation runtime with strict allowlists and approval checks.
  • Cloud provider command surfaces (AWS, Azure, GCP) with deny-by-default design.
  • Expanded workplace and file connectors under the Integration Specialist model.

That split matters in enterprise pilots because your security and legal teams evaluate readiness from capabilities, not promises. Every pilot claim is tied to a permission gate and an approval boundary.

Related reading

July 23, 2026

From V1 to V2: what changed in FleetRun product operations

A candid comparison of the old and new model: what we kept, removed, and corrected for safer operations.

July 20, 2026

Why personal AI workflows fail without governance

Teams usually start with one assistant and end up with drift. Here are the failure modes and what governance fixes.