molecule-ai[bot] c40b237c32 docs(marketing): Phase 30 launch — content blog posts, DevRel assets, and execution suite

Rebuilt from original PR #1276. All Phase 30 launch content restored:
- 5 blog posts (Remote Workspaces, Chrome DevTools MCP, Container vs Remote, Secure by Design)
- 4 guides (Remote Workspaces, FAQ, same-origin canvas, quickstart audio)
- Community copy: Discord/Slack announcements, HN launch guide
- Social copy: Phase 30 (4 X versions + LinkedIn), Chrome DevTools MCP
- Sales: landing copy, battlecards, one-pager, objection handlers
- Press release draft
- Demos: AGENTS.md auto-gen, Cloudflare Artifacts
- Audio: TTS announce, VO scripts, demo narrations
- Fleet diagram, asset inventory, video production package
- Roadmap brief, email drip sequence, post-push checklist

Closes GH#1126

2026-04-21 06:22:27 +00:00

2.6 KiB

Raw Blame History

Phase 30 — Remote Workspaces: Landing Page Copy

Cycle: Marketing work cycle — offline content prep Status: Draft for Marketing Lead review Placement: Primary CTA section and benefit blocks on the Phase 30 landing page

Hero Section

Headline: Agents that run where you need them.

Subheadline: Remote Workspaces let your AI agents operate on any machine — your laptop, a data-center VM, a customer environment — while staying fully managed in Molecule AI Canvas.

Primary CTA Block

Button: Start with Remote Workspaces →

Microcopy below button: No credit card. 5-minute setup. Runs on any machine with outbound HTTPS.

Benefit Block 1 — "Your environment. Your agents."

Headline: Works where your data lives.

Body: Remote Workspaces run on-premises or in your own cloud account. No data leaves your infrastructure — the platform only coordinates the agent. Ideal for regulated environments, on-prem workloads, and data-locality requirements.

Benefit Block 2 — "One Canvas. Every runtime."

Headline: Mixed fleets without compromise.

Body: Run container workspaces for ephemeral tasks and remote workspaces for persistent, environment-specific agents — all visible in the same Canvas. A2A coordination works across runtimes without code changes.

Benefit Block 3 — "Enterprise controls, everywhere."

Headline: Same governance, any infrastructure.

Body: MCP plugin allowlists, org-scoped API keys, workspace audit logs, and session-tier access controls apply to remote workspaces identically. The remote runtime is a transport — not a separate security model.

For [Company] and [Company], data residency isn't optional. Remote Workspaces keep agent compute on your infrastructure — while Canvas keeps you in control.

Bottom CTA

Headline: Ready to expand your fleet?

Body: Remote Workspaces are in GA. Self-serve setup in minutes. Talk to us if you need a custom enterprise deployment.

Button: Talk to Sales | View the Docs

X/LinkedIn Short-form Variant

Option A (technical audience):

Your agents. Your infra. Remote Workspaces are GA — run AI agents on any machine while Canvas keeps them coordinated. MCP governance travels with the agent. → [docs link]

Option B (buyer audience):

Phase 30 is live: Remote Workspaces let your AI agents run where your data lives — on-prem, in your cloud, anywhere. One Canvas. Mixed fleet. Enterprise controls. → [link]

Needs Marketing Lead review for brand voice consistency and competitive callouts.

2.6 KiB Raw Blame History