They said SaaS was dead. They were half right.

Software isn't dead. It's going headless.

The platform for the full headless stack. One TypeScript project becomes your product's ChatGPT app, Claude connector, MCP server, skills, plugins, CLI, and minified UI widgets — governed end to end, on every surface where work now starts.

The useful body of a product — its APIs, workflows, data, and transactions — needs governed agent access. The dashboard stops being the only front door.
Why now

Every SaaS company needs to stay usable where work now starts.

Customers are moving work into ChatGPT, Claude, Codex, Claude Code, Gemini, Copilot, and internal agents. The dashboard does not disappear, but it stops being the only front door.

Agents are where work starts

Users increasingly ask agents to do the work, not just explain where to click. Buying, support, and operations begin inside the agent.

Software must stay reachable

If your product is not usable inside your customers' agents, the agent owns the relationship — and the dashboard becomes a back office.

The plumbing is standardizing

MCP, now under Linux Foundation governance: 176M+ npm downloads of the official SDK in the past month; 41% of surveyed software orgs run it in production; 17,000+ public servers. And MCP is one mechanism — skills, plugins, and CLIs ride the same shift.

Sources: npm registry, @modelcontextprotocol/sdk, Jul 2026 · Stacklok, State of MCP in Software 2026 (n=100) · Zuplo, The State of MCP.
The problem

Going headless is easy to demo. Making it production-grade is the tax.

The repeated plumbing

Auth, identity, credential brokering, BYO identity provider, rate limiting, policy, audit, environments, secrets, hosting, logs, and host compatibility.

The customer pain

SaaS teams know their products must be callable by agents, but rebuilding this platform layer per app turns a weekend prototype into a quarters-long infrastructure project.

Only 12% of surveyed software orgs have reached broad production with MCP; 59% are still evaluating or piloting — a gap Stacklok calls a governance problem, not a technology problem. That blockage is the product.
Source: Stacklok, State of MCP in Software 2026.
What we learned

The first wave taught us where headless distribution actually lives.

Demand is real

Our first platform launched as Product Hunt's #1 Product of the Day (Jan 2025), shipped ~60 customer ChatGPT apps, and served 57K+ tool calls in its first six months.

Surfaces belong to the customer

OpenAI clarified that a platform cannot submit customer apps from its own org — each business publishes from its own. We now help customers ship under their own orgs, where they fully own the app-store relationship.

B2B distribution has no gatekeeper

A business rolling software out to its own employees on ChatGPT or Claude needs no app-store approval — and an agent can live inside the product itself. The same Noodle Seed backend powers every path.

The new platform generalizes that lesson: every surface — store-listed app, workspace connector, or in-product agent — is customer-owned and governed from day one.

Product

One TypeScript project turns your product's body into every headless surface.

Minified UI widgets give users just the information or action the task needs, and the AI arbitrates across your product's capabilities. MCP, skills, plugins, CLI — mechanisms, not the anchor.

Author

Model tools, resources, prompts, minified UI widgets, connectors, auth, and customer actions in TypeScript.

Operate

The runtime handles auth, identity, credential brokering, policy, audit, secrets, rate limits, logs, and environments.

Distribute

Ship as MCP server, ChatGPT app, Claude connector, skills, plugins, and CLI — into ChatGPT, Claude, coding agents, or an agent embedded in your own product.

brightdesk - deploy
$ noodle init brightdesk
initialized TypeScript project
$ noodle dev
local MCP: 127.0.0.1:7000/o/local/brightdesk/dev/mcp
$ noodle deploy
live: cloud.noodleseed.dev/o/brightdesk/support/mcp
# no OAuth server, no Dockerfile, no governance rebuild
Business

Open-core adoption with paid cloud, usage, and governance.

Primary wedge

Software and SaaS companies whose customers ask for ChatGPT apps, Claude connectors, coding-agent plugins, and governed MCP access — across commerce, healthcare, fintech, and developer tools.

Revenue model

Open-core: an Apache-2.0 engine core with commercial cloud and governance modules. Free $0 → Pro $30/mo → Scale $300/mo → Enterprise custom, usage pooled per billing account.

Enterprise features

Advanced auth, BYO identity provider, policy, audit, environments, security posture, and governance.

The ladder lands free and expands with governed usage — Pro and Scale self-serve, Enterprise scoped per agreement. The public open-source repo launch is a near-term milestone this round funds.

Wedge

Hosting is commoditizing. Governance is the wedge.

Internal build

Teams can build the demo. They still need a production runtime for identity, governance, operations, and distribution.

MCP clouds and SDKs

Alpic ($6M pre-seed) and Manufact ($6.3M seed) validate the server-side lane — and Salesforce, ServiceNow, Databricks, and AWS are bundling plain hosting into their platforms. Hosting alone is not the business.

Noodle Seed

The deepest built asset is governance — auth, credential brokering, policy, audit, tenancy — paired with agent-native TypeScript generation and structured compile errors as the repair loop.

Agent governance and auth are venture-validated wedges: Runlayer has raised $42M and Arcade.dev $72M on that layer alone. We pair the wedge with generation and multi-surface distribution.
Sources: TechCrunch, Nov 2025 & Fortune, Jun 2026 (Runlayer) · BusinessWire, Mar 2025 & Jun 2026 (Arcade) · VentureBeat, Feb 2026 (Manufact) · Partech, Sep 2025 (Alpic).
Team

A small team that ships platform infrastructure at agent speed.

Fahd Rafi — co-founder

Ex-Google, ex-Microsoft. MS Computer Science; business education at Oxford.

fahd@noodleseed.com
linkedin.com/in/fahdrafi

Asad Iqbal — co-founder

Former VP at Drone Technologies.

10 people, 7 builders

A compact team spanning compiler, runtime, security, cloud infrastructure, and product.

The proof is the build: compiler, governed runtime, hosted cloud, console, and CLI — first commit to production in under 60 days, 2,700+ merged changes, engineered with an AI-native, multi-agent development process behind machine-enforced quality gates. We build the way our customers will.
Seed round

Raising $6M Seed, $4.8M remaining.

The platform is built and live. This round buys the traction: the first 10–20 external businesses with live traffic and the self-serve launch loop — 24 months of runway, with milestones landing at month 18 and a 6-month buffer for the Series A process.

Where we are today

  • Hosted cloud, CLI, console, and the governance runtime are live at noodleseed.dev.
  • Pre-revenue: first-platform customers are migrating now; the first external businesses with live traffic are what this round funds.
  • Public open-core launch is the next milestone out.

18-month milestones

  • $1M ARR — the AI-infrastructure Series A gate — through a mixed self-serve, SaaS, enterprise, and partner-led model.
  • 10M cumulative tool calls across deployed agent-native surfaces.
  • Public open-core launch and adoption, plus capability and distribution partnerships.
~55% product + engineering~30% GTM + partnerships~15% infra, security, compliance, legal, ops