WillItSurvive
YC Winter 2026 · United States

Bubble Lab

AI-native workflow automation: turns Slack requests into code (Pearl)

Losing its protection
Assessed 27 July 2026 · Evidence as of 27 July 2026
The structural protection is eroding.
On the recordSince 27 July 2026 · Checkable from 12-18 months (est. 2027) · Every call on the record Checkpoint: Slack, HubSpot Breeze, and Jira native automation reaching ops-ready maturity
The call

A two-person team is betting code ownership beats per-task billing, while frontier labs and Slack itself build the same natural-language automation.

Bubble Lab lets you write automation workflows by describing them in plain English instead of coding them by hand. The problem: Zapier and Make already do this for millions of people, n8n has 60 times more open-source users, and big platforms like Slack and HubSpot are building their own automation tools directly into their software. Bubble Lab's main advantage is that you own the code you create, not Zapier's pay-per-task model, but that claim has not been tested with real customers yet. The company's biggest threat is not a smarter AI but rather Slack and HubSpot finishing their native tools in the next 12 to 18 months, which would give customers what they need without ever leaving those platforms.

Why
01
AI pressure: Claude and OpenAI agentic code generation. Claude and OpenAI already ship agentic code generation, the same natural-language-to-workflow-code trick Pearl sells. Could AI do the core job? Yes, likely.
02
Bigger players: Slack, HubSpot Breeze, and Jira Atlassian Intelligence native automation. Slack, HubSpot, and Jira are building native workflow automation into the same apps Pearl connects to. Could a giant copy it? Yes, easily.
03
What protects it. Open-core pitch of owning workflow code instead of renting per-task automation, unproven with no confirmed customer lock-in yet.
What would change this call
Slack, HubSpot Breeze, or Jira Atlassian Intelligence ship native AI-workflow automation within 12-18 months. Would show platform encroachment closing Bubble Lab's addressable market.
Bubble Lab's GitHub repo reopens to contributions or stays closed past mid-2026. Would show whether the weakened open-source moat is being rebuilt or abandoned.
A named, non-vendor-sourced customer describes running Pearl in production 90+ days. Would show real workflow lock-in rather than trial usage.
Key numbers
  • GitHub repo has ~1,096 stars vs n8n's far larger base (2026-07-01)
  • Two-person team per YC jobs listing (2026-07-01)
  • Raised $500K-$1M including YC's standard check (2025-12-08)
Named risks
  • Platform encroachment: Slack, HubSpot, Jira building native automation that could replace need for Pearl. Severity: high
  • Open-source moat weakening after GitHub repo closed to contributions on 2026-01-20. Severity: medium
  • No disclosed revenue or confirmed customers as of 2026-07-01, only 2-person team. Severity: high
  • Core NL-to-code capability assessed as moderately replicable by competitors in 3-6 months. Severity: medium
  • Company mid-pivot between original community-OS pitch and current Slack ops product, unclear positioning. Severity: medium
Rivals, as read in July 2026
RivalDirectionEvidence
n8nlosing ton8n has ~197.6k GitHub stars vs Bubble Lab's ~1,096 as of 2026-07
SlackcontestingSlack building native automation layer that could shrink Bubble Lab's market, noted 2026-07-01
HubSpotcontestingHubSpot Breeze cited as native automation encroaching on Pearl's use case, 2026-07-01
JiracontestingAtlassian Intelligence cited as native automation threat, 2026-07-01
Zapier/Makegaining onCalled legacy and pre-LLM architected by 2026-07-01 analysis, though still dominant incumbents
Questions people ask
Is Bubble Lab profitable in 2026?
No. As of July 2026, Bubble Lab discloses no revenue figures and is described as being in early customer validation mode with only a 2-person team, running on $500K to $1M in pre-seed funding from YC and Hat-trick Capital (as of 2025-12-08).
Could AI replace Bubble Lab's product?
Bubble Lab's own product, Pearl, is itself an AI layer converting natural language to workflow code. A July 2026 analysis rates its technical build as 'Moderately Replicable' in 3-6 months by a capable team, and frontier labs or Slack/HubSpot/Jira could embed similar capability natively.
Who is Bubble Lab's biggest competitor?
n8n, the open-source workflow automation platform, is cited as Bubble Lab's closest technical peer as of 2026-07-01. n8n's GitHub community (197.6k stars as of 2026-07-22) is roughly 60 to 100 times larger than Bubble Lab's (~1,096 stars, same date).
Who owns and founded Bubble Lab?
Bubble Lab was founded in 2025 by Selina Li (CEO) and Zach Zhong, both Cornell Tech MEng graduates who previously built nutrition app Gymii.ai. It is backed by Y Combinator (W26 batch) and Hat-trick Capital, per a 2025-12-08 report.
What does Bubble Lab's product Pearl actually do?
Pearl is a Slack-native AI ops assistant, launched via YC on 2026-02-24, that converts natural-language requests into visual workflows and production-ready TypeScript code, connecting to Notion, Jira, HubSpot, Stripe, and Google Workspace.
Has Bubble Lab raised any funding?
Yes. As of 2025-12-08, Bubble Lab had raised roughly $500,000 to $1M including Y Combinator's standard investment, backed by YC and Hat-trick Capital. No priced valuation or later round has been publicly disclosed as of mid-2026.
Timeline
  • 2026-07-01Analysis describes Bubble Lab as 2-person team, ~1,096 GitHub stars, 180 forks, pre-revenue
  • 2026-04-29GitHub repo confirmed Apache-2.0 licensed, self-hostable, contributions closed since Jan 2026
  • 2026-02-24Launch YC post introduces Pearl, Slack-native AI ops automation product
  • 2026-01-20Bubble Lab GitHub repo posts notice ending code contributions and pull requests
  • 2025-12-08Caplight reports total funding of $500K-$1M, backers YC and Hat-trick Capital
  • 2025-12-01GitHub repo shows about 590 stars and 51 forks
  • 2025-05-15Profile confirms founders Selina Li and Zach Zhong, Cornell Tech, prior app Gymii.ai
Revision history
27 July 2026
First assessed. Losing its protection. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources