fastn

fastn is an embedded integration platform for B2B SaaS companies. Instead of your engineers building each integration a customer asks for, you embed fastn once in your product and your customers connect their own systems from inside it. The site calls it "the integration layer for SaaS." It is written for product, engineering and revenue teams at software vendors, not for a business team that wants to automate its own internal apps. Its pages show the company as fastn, Inc.

What you build and how

The home page frames the idea in 3 steps. First, "you, once," embed the connect UI. The page shows a React snippet that imports a FastnConnectCard component from the @fastn-ai/embed/react package. Second, "your customers, self-serve," connect their stack, with example cards for Salesforce, HubSpot and Snowflake. Third, data flows and the connections are monitored. The company's claim is that "Integration becomes configuration, with zero code per customer."

The platform menu names 4 building blocks.

• Workflows, described as "Visual + code, versioned." You can build in a visual editor and drop into code, and the site says teams that want deeper control "can still drop into code."
• Unified API, described as "One schema across systems."
• MCP Gateway, described as "Governed tool access for agents."
• Integration agents, described as "Agents that build the mapping."

The last of these connects to a feature the home page calls "Describe the integration. We'll wire it." Customers can ask, inside your product, for a system, a workflow or an agent tool, and fastn "assembles the connection." The company says fastn "builds them, monitors them, and keeps them working, on autopilot," and that it handles "auth, mapping, retries, monitoring."

The company contrasts its approach with two generic alternatives, a fixed unified schema that "your customer's custom fields and objects don't fit," and a "flexible black box" you cannot debug. Its answer is "a documented, public surface" with "per-customer field and object mapping," "readable logs and traces, per connection," and the option to "drop into code whenever you want to." Connection health, logs and alerts are shown per customer, inside your product.

The home page sells speed as well: "What took weeks of custom build ships in hours," and once the one-time embed is in place, "build and maintenance trend to zero." For sales teams the pitch is that "One embed lights up the whole connector catalog," so "Do you support X?" stops being a roadmap conversation "and becomes a toggle."

For AI use, the home page promises that your AI agents get "permission-scoped, audited access to every connected system," with "every call logged, bounded, and reversible." A solutions menu covers embedded customer integrations, scoped agent access and a Sales & CRM page about keeping revenue systems in sync.

Connectors. The compare page's menu says "1,000+ connectors," and the home page says the catalog is live with "new connectors ship every week." The home page shows a logo strip including Pipedrive, Slack, NetSuite, Notion, Jira, Google Drive, ServiceNow, Marketo, Gmail, Postgres, Shopify, QuickBooks, Asana, Stripe, Airtable, Dropbox, MongoDB, GitHub, Oracle, SAP, Okta, Databricks, Tableau, Mailchimp, Twilio, Microsoft Teams, Outlook, Workday, Xero, SendGrid, Intercom, Linear and Figma, with Salesforce, HubSpot, Snowflake and Zendesk in the product examples. A banner says "Every CRM your customers run, already connected." It also mentions "bespoke integrations pre-built catalogs break on," meaning the system is meant to handle a customer's unusual setup and not only popular apps.

What your customers experience. They see a connect button, authorize the systems they use, and then see per-connection status. The sample dashboard on the home page shows an uptime figure, syncs per day, auto-healed events and P95 latency, plus a table of connections by tenant with states such as "healthy," "API change absorbed" and "auto-retried · recovered." The end user does not get an app, form or website builder; fastn sits behind your product.

Pricing, claims and customers

Pricing: the home page states "3 connections free · pay as you scale · no sales call required," with "Start free," "Build your first integration free" and "Book a demo" buttons. Paid tiers carry no prices on these pages, though the footer links a Pricing page and a "For startups" page.

Security: the home page states "SOC 2 Type II" in its hero strip and again, as "SOC 2," in the Security menu entry, which also lists RBAC and self-hosting. The benefits list says "SOC 2, granular RBAC, private networking, full observability, self-hosting." The footer carries a HIPAA-BAA link. The security pitch is aimed at the buyer's own review: "Pass security review calmly," with systems "your customers can't afford to get wrong."

Reliability and size: the hero strip says "99.98% uptime," and the page presents it as a company figure. It also says "Trusted by customers and partners" over a logo area.

Company statistics: the page says "1 in 4 enterprise deals stall on integrations," that integrated accounts show "2× retention," that churn "drops by half," and cites a "retention lift for customers using an integration (ProfitWell)." These are marketing claims of the company.

Press: the page lists Forbes ("Composable architecture, shipped faster"), VentureBeat ("AI agents for data integration") and CIOReview ("Top AI-Powered Embedded Integration Platform").

Customer-facing language: the "Integrations" menu entry links a browsable catalog, and a "Use cases" page shows "how teams ship with fastn." The company's own test for whether you need it is this question: "When customer number fifty wants a different field mapping, does that create work for your team or for them?" It also says some teams run fastn for customer-facing integrations next to a separate tool for internal automation, because the two "sit at different layers."

Support: the menu lists "Talk to a human," plus docs with guides, an API reference and SDKs, a blog and a weekly changelog.

Who it suits and who it does not

fastn suits a B2B SaaS company whose customers each run a different stack, where the "Do you support X?" question keeps appearing in sales calls and the integration backlog is eating roadmap time. The company's own test is whether customer number fifty asking for a different field mapping creates work for your team or for them. Teams building AI agents that need scoped access to customer systems are a second audience, through the MCP Gateway.

It is a weaker match for a team that wants to automate its own internal apps, since the product is built around your customers' connections. If nearly all your customers use the same three systems, the case for embedding is weaker. Past the 3 free connections, budgeting needs the pricing page or a call.