<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Sven March</title>
    <description>The latest articles on Forem by Sven March (@sven_mrz_dfc2d01f06d7f20).</description>
    <link>https://forem.com/sven_mrz_dfc2d01f06d7f20</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3886186%2Fd7534396-70be-4b77-bb6e-5631d8b24860.png</url>
      <title>Forem: Sven March</title>
      <link>https://forem.com/sven_mrz_dfc2d01f06d7f20</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/sven_mrz_dfc2d01f06d7f20"/>
    <language>en</language>
    <item>
      <title>Low-Code Is Obsolete: AI Changed Data Integration</title>
      <dc:creator>Sven March</dc:creator>
      <pubDate>Tue, 21 Apr 2026 14:48:58 +0000</pubDate>
      <link>https://forem.com/sven_mrz_dfc2d01f06d7f20/low-code-is-obsolete-ai-changed-data-integration-44m5</link>
      <guid>https://forem.com/sven_mrz_dfc2d01f06d7f20/low-code-is-obsolete-ai-changed-data-integration-44m5</guid>
      <description>&lt;p&gt;For a decade, low-code iPaaS platforms promised speed: drag-and-drop flows, prebuilt connectors, faster delivery. And they delivered—at least initially.&lt;/p&gt;

&lt;p&gt;But they also created a hidden problem:&lt;br&gt;
your most critical data flows live inside proprietary tools you don’t really own.&lt;/p&gt;

&lt;p&gt;Mappings become diagrams. Logic becomes metadata. Behavior becomes hard to version, test, or migrate. Over time, speed turns into integration debt.&lt;/p&gt;

&lt;p&gt;AI changes that equation.&lt;/p&gt;

&lt;p&gt;Today, AI can generate connector logic, transformations, retries, and tests directly from intent. The original reason for low-code—“coding integrations is too slow and expensive”—is no longer true.&lt;/p&gt;

&lt;p&gt;The goal is not no-code.&lt;br&gt;
The goal is code you didn’t have to write—but still own.&lt;/p&gt;

&lt;p&gt;Instead of drawing flows, teams can now generate real, reviewable, production-grade code and run integrations like any other software system.&lt;/p&gt;

&lt;p&gt;The New Model: From Integration Projects to Integration Operations&lt;/p&gt;

&lt;p&gt;Modern integration is no longer about building flows—it’s about operating a lifecycle.&lt;/p&gt;

&lt;p&gt;A simple shift happens:&lt;/p&gt;

&lt;p&gt;You describe the outcome (sync orders, enrich data, connect APIs)&lt;br&gt;
AI generates the implementation&lt;br&gt;
Engineers review and deploy it&lt;br&gt;
AI monitors and maintains it over time&lt;/p&gt;

&lt;p&gt;This is the move from low-code workflows → AI-managed integration systems.&lt;/p&gt;

&lt;p&gt;And it solves the real problem:&lt;/p&gt;

&lt;p&gt;Not connectivity.&lt;br&gt;
But the ongoing cost, fragility, and maintenance burden of integrations.&lt;/p&gt;

&lt;p&gt;That’s exactly where platforms like Plumbed.io focus:&lt;/p&gt;

&lt;p&gt;Build integrations from a prompt&lt;br&gt;
Run them as production-grade systems&lt;br&gt;
Detect and fix failures automatically&lt;br&gt;
Reduce integration cost and time-to-market&lt;/p&gt;

&lt;p&gt;Instead of:&lt;/p&gt;

&lt;p&gt;“How fast can I build this flow?”&lt;/p&gt;

&lt;p&gt;The better question becomes:&lt;/p&gt;

&lt;p&gt;“What do I own when this integration is running in production?”&lt;/p&gt;

&lt;p&gt;If the answer is still “a diagram inside a vendor tool,”&lt;br&gt;
low-code hasn’t solved your problem—it just delayed it.&lt;br&gt;
At &lt;a href="https://www.plumbed.io/" rel="noopener noreferrer"&gt;Plumbed &lt;/a&gt;we provide full control of you integrations: &lt;/p&gt;

</description>
      <category>ai</category>
      <category>lowcode</category>
    </item>
    <item>
      <title>Introducing Plumbed, self-healing integrations in days, not months</title>
      <dc:creator>Sven March</dc:creator>
      <pubDate>Sat, 18 Apr 2026 14:38:49 +0000</pubDate>
      <link>https://forem.com/sven_mrz_dfc2d01f06d7f20/introducing-plumbed-self-healing-integrations-in-days-not-months-1mm5</link>
      <guid>https://forem.com/sven_mrz_dfc2d01f06d7f20/introducing-plumbed-self-healing-integrations-in-days-not-months-1mm5</guid>
      <description>&lt;p&gt;If you’ve ever shipped a “finished” integration only to spend the next months babysitting it, you already know the real cost isn’t the build, it’s the uptime.&lt;/p&gt;

&lt;p&gt;At &lt;strong&gt;Plumbed.io&lt;/strong&gt;, we’re building an AI-native integration platform that takes ownership of the full lifecycle: from prompt-driven setup to monitoring, self-healing, and continuous updates when APIs change.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Plumbed does
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Build integrations in days, not months&lt;/strong&gt; via a conversational, prompt-driven workflow&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automated mapping and transformation&lt;/strong&gt; for real-world data (ETL)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Self-healing operations&lt;/strong&gt;: monitoring, proactive error handling, and quick reruns/fixes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Governed AI + human-in-the-loop&lt;/strong&gt; for production control and visibility&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flexible deployment&lt;/strong&gt;: managed cloud or on-prem/custom infrastructure&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Where we’re focused
&lt;/h3&gt;

&lt;p&gt;We work on practical integration challenges, like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;launching new commerce/marketplace channels faster,&lt;/li&gt;
&lt;li&gt;connecting partner-operated stores to HQ systems (APIs, CSVs, scheduled exports),&lt;/li&gt;
&lt;li&gt;turning messy store data into stable analytics pipelines.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If this sounds like your world, take a look:&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://www.plumbed.io" rel="noopener noreferrer"&gt;https://www.plumbed.io&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Happy to answer questions in the comments or compare notes on integration ops and maintenance.&lt;/p&gt;

</description>
      <category>integration</category>
      <category>api</category>
      <category>devops</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
