<?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>DEV Community: Jaume Boguñá</title>
    <description>The latest articles on DEV Community by Jaume Boguñá (@jaume_bogu).</description>
    <link>https://dev.to/jaume_bogu</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4169403%2Fc3d0e670-f610-40ee-ba25-098f29fc4d1f.jpg</url>
      <title>DEV Community: Jaume Boguñá</title>
      <link>https://dev.to/jaume_bogu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jaume_bogu"/>
    <language>en</language>
    <item>
      <title>Honeybadger Alternatives for Rails: AppSignal, Scout, and Sentry</title>
      <dc:creator>Jaume Boguñá</dc:creator>
      <pubDate>Fri, 20 Nov 2026 19:26:33 +0000</pubDate>
      <link>https://dev.to/jaume_bogu/honeybadger-alternatives-for-rails-appsignal-scout-and-sentry-18k2</link>
      <guid>https://dev.to/jaume_bogu/honeybadger-alternatives-for-rails-appsignal-scout-and-sentry-18k2</guid>
      <description>&lt;p&gt;AppSignal, Scout, and Sentry are useful Honeybadger alternatives for Rails teams, but the right choice depends on what you want to change. AppSignal is relevant for an application-and-operations workflow, Scout for Rails performance investigation, and Sentry for a product whose incident path crosses multiple application layers.&lt;/p&gt;

&lt;p&gt;Honeybadger itself remains a credible baseline. Its current offering includes Insights and performance dashboards as well as error monitoring. A comparison that treats it as exception-only creates a false reason to migrate.&lt;/p&gt;

&lt;p&gt;Start by identifying the missing capability or workflow problem in the setup you actually run.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check whether the gap is configuration
&lt;/h2&gt;

&lt;p&gt;Honeybadger's &lt;a href="https://docs.honeybadger.io/lib/ruby/insights/" rel="noopener noreferrer"&gt;Ruby Insights documentation&lt;/a&gt; describes capabilities beyond the error SDK. Some operational dashboards require specific configuration and supported versions.&lt;/p&gt;

&lt;p&gt;Before shopping, determine whether the desired data is unavailable or simply not enabled. Turning on the appropriate integration can be less disruptive than moving vendors, especially when the team already trusts its error grouping and alert routing.&lt;/p&gt;

&lt;p&gt;That does not mean every team should stay. It means the alternative should be evaluated against a correctly configured baseline rather than an intentionally incomplete one.&lt;/p&gt;

&lt;p&gt;For example, if the missing signal is Solid Queue depth, Honeybadger already &lt;a href="https://docs.honeybadger.io/guides/dashboards/solid-queue-metrics/" rel="noopener noreferrer"&gt;documents that dashboard&lt;/a&gt; with gem 6.3+ and enabled metrics. That gap may be configuration, not a reason to switch. If you instead need MRI lock-wait measurements, AppSignal's &lt;a href="https://docs.appsignal.com/ruby/integrations/global-vm-lock.md" rel="noopener noreferrer"&gt;GVL integration&lt;/a&gt; is a concrete alternative capability to examine.&lt;/p&gt;

&lt;h2&gt;
  
  
  AppSignal for the application and operating context
&lt;/h2&gt;

&lt;p&gt;AppSignal's &lt;a href="https://docs.appsignal.com/ruby/integrations/rails.md" rel="noopener noreferrer"&gt;Rails integration&lt;/a&gt; is a practical starting point when the desired replacement connects application execution with additional framework and operational signals.&lt;/p&gt;

&lt;p&gt;Use a request that schedules a background task, then inspect a controlled slowdown in that task. Check the execution evidence and any specific worker or resource metrics that motivated the search.&lt;/p&gt;

&lt;p&gt;The limitation is that integration scope varies. A generic Active Job path does not establish every adapter-specific queue metric, and a host chart does not establish memory-allocation attribution.&lt;/p&gt;

&lt;p&gt;Prioritize AppSignal for a specific operational requirement such as GVL waiting, Scout for allocation or query Insights, and Sentry when the incident spans a product already using its other SDKs. These choices give each migration a purpose. “Another vendor has dashboards” does not justify replacing Honeybadger's existing error workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scout for a performance-led replacement
&lt;/h2&gt;

&lt;p&gt;Scout explicitly documents &lt;a href="https://scoutapm.com/docs/features/insights" rel="noopener noreferrer"&gt;N+1, slow-query, and memory insights&lt;/a&gt;. Those are good reasons to evaluate it when recurring Rails performance regressions dominate the team's incidents.&lt;/p&gt;

&lt;p&gt;Give it a known expensive action rather than a synthetic error alone. Ask whether the evidence points to the responsible operation and whether the team can verify the correction under comparable conditions.&lt;/p&gt;

&lt;p&gt;Scout's current offering includes additional signals, so do not assume a performance-led purchase necessarily means abandoning every consolidation goal. Check the selected plan and actual integration requirements.&lt;/p&gt;

&lt;p&gt;Its advantage should be demonstrated in the investigation. A feature name is a useful shortlist criterion, not a substitute for inspecting the resulting evidence.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sentry for a cross-layer incident workflow
&lt;/h2&gt;

&lt;p&gt;Sentry's &lt;a href="https://docs.sentry.io/platforms/ruby/guides/rails/" rel="noopener noreferrer"&gt;Rails documentation&lt;/a&gt; describes error and tracing setup. It is a relevant alternative when developers already use Sentry for browser or other application layers and want to assess a shared investigation path.&lt;/p&gt;

&lt;p&gt;For example, a customer-visible checkout delay may involve frontend behavior, a Rails request, and a downstream service. Evaluate which parts the configured system captures and how developers follow the evidence across them.&lt;/p&gt;

&lt;p&gt;Do not assume every SDK has identical behavior or that tracing is complete without deliberate configuration. Sampling, enabled integrations, and retained data can affect what the investigator sees.&lt;/p&gt;

&lt;p&gt;Sentry can be the right choice when that broader product workflow matters more than a Rails-specific operational arrangement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the replacement pass two tests
&lt;/h2&gt;

&lt;p&gt;First, reproduce the missing investigation. Use a successful slow request or job if performance is the trigger, and verify that the alternative supplies actionable evidence.&lt;/p&gt;

&lt;p&gt;Second, reproduce the existing error workflow. Check grouping, context, ownership, and alert delivery. A new performance view does not justify silently losing the error behavior that Honeybadger already handled well.&lt;/p&gt;

&lt;p&gt;Compare total cost using the same workload and retained signals. Include migration work and any tools you would keep. Do not rank prices by mismatched request, event, or span allowances.&lt;/p&gt;

&lt;p&gt;Choose two finalists and keep the trial narrow. If AppSignal is one, start with the application path that exposes the current gap and the alerts that must survive migration.&lt;/p&gt;

&lt;p&gt;Move when the improvement is concrete. Keep Honeybadger when configuration closes the gap or the alternatives do not justify rebuilding a working incident process.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQs
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is Honeybadger only an error tracker?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Its current documentation includes Insights and performance dashboards. Evaluate the enabled setup before deciding to replace it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which alternative should we try first?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Use the switching reason: AppSignal for the relevant application and operational workflow, Scout for performance insights, or Sentry for a cross-layer investigation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can we migrate without changing alert behavior?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Do not assume exact parity. Validate required delivery, grouping, and ownership before retiring the existing integration.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>softwareengineering</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Rails Server Monitoring on Hatchbox: Is AppSignal Enough for Your Setup?</title>
      <dc:creator>Jaume Boguñá</dc:creator>
      <pubDate>Thu, 19 Nov 2026 15:03:14 +0000</pubDate>
      <link>https://dev.to/jaume_bogu/rails-server-monitoring-on-hatchbox-is-appsignal-enough-for-your-setup-2naf</link>
      <guid>https://dev.to/jaume_bogu/rails-server-monitoring-on-hatchbox-is-appsignal-enough-for-your-setup-2naf</guid>
      <description>&lt;p&gt;AppSignal can be enough for a Hatchbox-hosted Rails application's monitoring if its configured application, host, and process signals cover your requirements. It is not a substitute for server administration, backup recovery, or every infrastructure-management task.&lt;/p&gt;

&lt;p&gt;Hatchbox and AppSignal have complementary roles. Hatchbox manages deployment to your servers; AppSignal supplies monitoring capabilities for the application and its operating environment. Evaluate the combined workflow rather than ranking the deployment service against the monitor.&lt;/p&gt;

&lt;p&gt;The practical buying question is whether a developer can detect and explain the failures that matter on your particular server setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define what “server monitoring” means for your team
&lt;/h2&gt;

&lt;p&gt;A Rails team may use that phrase to mean CPU and memory charts, process liveness, application exceptions, or all three. These are separate requirements.&lt;/p&gt;

&lt;p&gt;Start with a short failure inventory. Include a slow request, a stopped worker, a full or constrained resource, and a scheduled task that never finishes. Identify who receives each alert and what action they should take.&lt;/p&gt;

&lt;p&gt;Decide what each alert must establish: a host metric can show resource pressure, a task completion signal can prove the expected work reached its success boundary, and a request trace can show time spent in application operations. You need all three only if all three are part of your operating responsibility. This gives “enough monitoring” a concrete meaning.&lt;/p&gt;

&lt;p&gt;Buying enough monitoring means covering those boundaries deliberately, not finding a product page that uses the same umbrella term.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the AppSignal and Hatchbox combination offers
&lt;/h2&gt;

&lt;p&gt;AppSignal's &lt;a href="https://www.appsignal.com/hatchbox" rel="noopener noreferrer"&gt;Hatchbox page&lt;/a&gt; describes their integration and the combination of application, host, and process monitoring. Use that as an entry point, then verify the relevant configuration in your actual deployment.&lt;/p&gt;

&lt;p&gt;Its &lt;a href="https://docs.appsignal.com/metrics/host-metrics.md" rel="noopener noreferrer"&gt;host metrics documentation&lt;/a&gt; explains the resource-measurement surface. Check supported collection for the operating environment and confirm that host identification remains useful when several applications share a server.&lt;/p&gt;

&lt;p&gt;If your deployment uses containers, AppSignal's &lt;a href="https://docs.appsignal.com/metrics/host-metrics/containers.md" rel="noopener noreferrer"&gt;container metrics guide&lt;/a&gt; requires configured CPU and memory limits for accurate reporting. Its CPU measurement can exceed 100% because each virtual core contributes up to 100%. Confirm that interpretation before treating a multi-core graph as evidence of overload.&lt;/p&gt;

&lt;p&gt;This is a concrete benefit for teams that want application and resource evidence available during the same incident. It is still necessary to verify the source and meaning of each chart.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test a stopped worker separately from a slow worker
&lt;/h2&gt;

&lt;p&gt;Consider a Rails export worker. In one incident it stops running. In another it continues running but each export takes much longer.&lt;/p&gt;

&lt;p&gt;Those cases require different evidence. AppSignal's &lt;a href="https://docs.appsignal.com/check-ins/create.md" rel="noopener noreferrer"&gt;check-in documentation&lt;/a&gt; describes heartbeat and scheduled checks. Appropriate application instrumentation supplies execution evidence for the slow-worker case.&lt;/p&gt;

&lt;p&gt;Configure the success condition carefully. A heartbeat emitted by a supervisor or unrelated process does not necessarily prove that the export work is being performed. A completion check can be more appropriate for a scheduled business task.&lt;/p&gt;

&lt;p&gt;In a safe test, stop the intended signaling path and confirm the alert. Then restore it and run a controlled slow execution. Verify that the team can distinguish absence from slow work rather than receiving an unexplained generic warning.&lt;/p&gt;

&lt;p&gt;This is a stronger purchase test than checking that the host dashboard contains a green line.&lt;/p&gt;

&lt;h2&gt;
  
  
  Know what the purchase does not operate for you
&lt;/h2&gt;

&lt;p&gt;Monitoring can show that a backup task failed to report completion. It does not establish that a stored backup can be restored successfully. Keep restoration testing and server maintenance as explicit operational responsibilities.&lt;/p&gt;

&lt;p&gt;Similarly, detecting high memory use does not automatically choose a new server size or repair an application leak. The value lies in the evidence that supports the next engineering decision.&lt;/p&gt;

&lt;p&gt;A separate infrastructure tool may still be justified if the organization needs requirements beyond the application and host signals demonstrated in the trial. Keeping it is reasonable when it serves a clearly defined role.&lt;/p&gt;

&lt;p&gt;Compare &lt;a href="https://www.appsignal.com/plans" rel="noopener noreferrer"&gt;AppSignal's current plans&lt;/a&gt; with the complete retained setup. Include application activity, logs, and any other required service. Do not count hypothetical hosting savings as a guaranteed benefit of monitoring.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical recommendation
&lt;/h2&gt;

&lt;p&gt;Evaluate AppSignal first if you want monitoring that fits the Rails applications deployed through Hatchbox and you prefer a shared application-and-host investigation workflow.&lt;/p&gt;

&lt;p&gt;Use one server and one representative application. Verify a request failure, a slow background task, a missing check-in, and resource measurements with known meaning. Ask another developer to follow each alert into the relevant evidence.&lt;/p&gt;

&lt;p&gt;Choose it as the primary monitor if those tests satisfy the actual requirements. Add or retain specialist tooling for any remaining operational responsibility, and document that boundary so the team does not mistake a healthy dashboard for complete server assurance.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQs
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does AppSignal replace Hatchbox?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. Deployment management and monitoring are complementary roles in this setup.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does a successful backup check prove restorability?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. It proves the configured signal arrived. A restoration exercise is a separate requirement.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can AppSignal be the only monitoring subscription?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Possibly, if the configured signals meet the team's needs. Verify the required failure cases before retiring another service.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>productivity</category>
      <category>coding</category>
    </item>
    <item>
      <title>Best AI Testing Tools for Vercel and Netlify Preview Deployments in 2027</title>
      <dc:creator>Jaume Boguñá</dc:creator>
      <pubDate>Tue, 17 Nov 2026 19:16:13 +0000</pubDate>
      <link>https://dev.to/jaume_bogu/best-ai-testing-tools-for-vercel-and-netlify-preview-deployments-in-2027-1dab</link>
      <guid>https://dev.to/jaume_bogu/best-ai-testing-tools-for-vercel-and-netlify-preview-deployments-in-2027-1dab</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmyuqc2al0eoc5isyuyek.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmyuqc2al0eoc5isyuyek.png" alt="cover image" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Vercel and Netlify already give every pull request a running copy of your app. The question this guide answers is what tests that copy before merge, and how each tool gets past preview protection and back onto the PR.&lt;/p&gt;

&lt;p&gt;On most teams the preview link gets a quick click from the reviewer, and that click is the whole test. At the volume coding agents produce, even the click often gets skipped.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is preview deployment testing?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Preview deployment testing runs end-to-end tests against the temporary deployment that Vercel or Netlify builds for each pull request, then reports the result back on that pull request before merge.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Both platforms do the hard part. &lt;a href="https://vercel.com/docs/git/vercel-for-github" rel="noopener noreferrer"&gt;Vercel for GitHub&lt;/a&gt; deploys every push and makes the latest commit of each PR available at a unique preview URL, posted as a comment on the PR. Netlify builds a &lt;a href="https://docs.netlify.com/deploy/deploy-types/deploy-previews/" rel="noopener noreferrer"&gt;Deploy Preview&lt;/a&gt; for each pull request at an address such as &lt;code&gt;deploy-preview-42--mysitename.netlify.app&lt;/code&gt;. A testing tool has three jobs left: know when that preview is ready, get through whatever protects it, and put a verdict where the reviewer will see it.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Vercel and Netlify give every PR a live preview. Most teams look at it; few test it.&lt;/li&gt;
&lt;li&gt;A tool has to wait for the preview to finish, pick up its URL from GitHub, get past preview protection and report on the PR.&lt;/li&gt;
&lt;li&gt;Vercel previews are often behind Standard Protection, and Protection Bypass for Automation is the supported way in. Netlify has no equivalent, so private previews need a password scoped to previews or a public project.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://qa.tech/product/pr-testing" rel="noopener noreferrer"&gt;QA.tech's PR testing&lt;/a&gt; detects Vercel and Netlify previews automatically and posts a verdict as a required GitHub check. Checkly, Meticulous and Playwright in GitHub Actions each cover a narrower slice.&lt;/li&gt;
&lt;li&gt;Vercel's Deployment Checks gate production promotion, not the PR. Treat them as a second gate.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How testing tools hook into Vercel and Netlify previews
&lt;/h2&gt;

&lt;p&gt;Every tool here follows the same chain; they differ in how much of it you build yourself.&lt;/p&gt;

&lt;p&gt;PR opens → platform builds the preview → deploy record reaches success → tool reads the preview URL → bypass gets it past protection → tests run → verdict lands on the PR&lt;/p&gt;

&lt;h2&gt;
  
  
  Waiting for the preview and finding its URL
&lt;/h2&gt;

&lt;p&gt;Vercel tells GitHub about each deployment through the &lt;code&gt;deployment_status&lt;/code&gt; webhook event, which a GitHub Actions workflow can trigger on, reading the address from &lt;code&gt;environment_url&lt;/code&gt;. Vercel's docs now encourage &lt;a href="https://vercel.com/docs/git/vercel-for-github#repository-dispatch-events" rel="noopener noreferrer"&gt;migrating to &lt;code&gt;repository_dispatch&lt;/code&gt; events&lt;/a&gt; such as &lt;code&gt;vercel.deployment.success&lt;/code&gt;, whose payload carries the deployment URL. One catch: those dispatch events only trigger a workflow that exists on the default branch.&lt;/p&gt;

&lt;p&gt;Netlify reports through &lt;a href="https://docs.netlify.com/deploy/deploy-notifications/" rel="noopener noreferrer"&gt;deploy notifications&lt;/a&gt;. GitHub commit statuses, PR comments and commit checks are on by default for new GitHub-connected sites, and a successful commit status links to the Deploy Preview. An outgoing webhook on "Deploy succeeded" is the other route.&lt;/p&gt;

&lt;p&gt;Readiness is the subtle part: in a monorepo, a test that starts on the first green deploy can hit an app whose API is still building.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting past protected previews
&lt;/h2&gt;

&lt;p&gt;On Vercel, &lt;a href="https://vercel.com/docs/deployment-protection" rel="noopener noreferrer"&gt;Standard Protection&lt;/a&gt; protects every deployment except production domains, so a preview link opened by a test runner meets a login wall. &lt;a href="https://vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation" rel="noopener noreferrer"&gt;Protection Bypass for Automation&lt;/a&gt;, available on all plans, issues a secret you send as the &lt;code&gt;x-vercel-protection-bypass&lt;/code&gt; header. Browser tests add &lt;code&gt;x-vercel-set-bypass-cookie: true&lt;/code&gt; so later page requests keep the bypass. You can create several named secrets per project, one per tool. Regenerating or deleting a secret invalidates previous deployments, so plan a redeploy when you rotate.&lt;/p&gt;

&lt;p&gt;Netlify is stricter. Under &lt;a href="https://docs.netlify.com/manage/security/secure-access-to-sites/project-visibility/" rel="noopener noreferrer"&gt;project visibility&lt;/a&gt;, teams created on or after 28 July 2026 start new projects private, and previews stay private unless you change their visibility. Private means Netlify team login. Netlify documents no automation bypass, so a test runner has two options: a shared &lt;a href="https://docs.netlify.com/manage/security/secure-access-to-sites/password-protection/" rel="noopener noreferrer"&gt;password with "Previews only" scope&lt;/a&gt; (Pro plans on credit-based pricing), or public previews.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the verdict lands
&lt;/h2&gt;

&lt;p&gt;A result that lives only in a vendor dashboard gets ignored. It belongs in a GitHub check that branch protection can require, plus a PR comment that explains a failure. &lt;a href="https://vercel.com/docs/deployment-checks" rel="noopener noreferrer"&gt;Vercel's Deployment Checks&lt;/a&gt; are a different gate: they hold a production deployment back from your custom domains until required GitHub checks pass. They protect the release after merge, which makes them a good second gate, not a substitute for testing the PR.&lt;/p&gt;

&lt;h2&gt;
  
  
  How we picked
&lt;/h2&gt;

&lt;p&gt;Each tool had to integrate with Vercel or Netlify previews on its own live documentation, checked on 11 November 2026. We scored:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Trigger:&lt;/strong&gt; does it start when the preview is ready, without polling scripts?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Protection:&lt;/strong&gt; does it document a way past Vercel and Netlify preview protection?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verdict:&lt;/strong&gt; does the result land on the PR as a check that can block the merge?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What it proves:&lt;/strong&gt; does it test a user journey, a page load, or a visual difference?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Upkeep:&lt;/strong&gt; who fixes the tests when an agent redesigns the page?&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The best AI testing tools for Vercel and Netlify preview deployments
&lt;/h2&gt;

&lt;h2&gt;
  
  
  QA.tech
&lt;/h2&gt;

&lt;p&gt;QA.tech is an AI testing platform whose QA agents test the running app toward a user goal, such as "complete checkout with a saved card", and post a verdict on the pull request.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it hooks in&lt;/strong&gt;. Install the &lt;a href="https://docs.qa.tech/configuration/github-app" rel="noopener noreferrer"&gt;GitHub App&lt;/a&gt; and Vercel or Netlify previews are detected automatically from the deployment records those platforms write to GitHub. QA.tech &lt;a href="https://docs.qa.tech/configuration/github-deployments" rel="noopener noreferrer"&gt;waits until every deploy record on the PR head commit is successful&lt;/a&gt;, and commit statuses whose name contains "deploy", "deployment" or "vercel" also count as gates. That closes the monorepo race: the review doesn't start on the frontend while the API preview is still pending.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Protection&lt;/strong&gt;. For Vercel, you paste the bypass secret once into the application's &lt;a href="https://docs.qa.tech/configuration/vercel-preview-protection" rel="noopener noreferrer"&gt;preview defaults&lt;/a&gt; as custom headers for &lt;code&gt;*.vercel.app&lt;/code&gt;, and QA.tech copies them onto every new preview environment. The secret stays in headers, never in the URL. For Netlify, the &lt;a href="https://docs.qa.tech/configuration/netlify-protection" rel="noopener noreferrer"&gt;Netlify protection guide&lt;/a&gt; says plainly that there is no automation bypass: use a password scoped to previews, stored in QA.tech with a login test the others depend on, or make previews public.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verdict&lt;/strong&gt;. Once the preview is up, the QA agents look at what the PR changed, run the tests that already cover it, write tests for anything new and post the result. The verdict appears as a "QA.tech / PR Review" check that &lt;a href="https://docs.qa.tech/pr-testing/github" rel="noopener noreferrer"&gt;can be required in branch protection&lt;/a&gt;, plus a comment on the PR. It is anchored to the diff, so failures already on main are reported separately, and a run that never exercised the change returns "unverified" instead of a false green. Each failure includes screenshots and a video of the run, the network and console logs, and the agent's reasoning at each step.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reality check&lt;/strong&gt;. The agent works toward the goal on whatever page it finds, so a moved discount field doesn't break the test, but people still review the findings and decide which flows to pin as explicit, blocking steps. Before a PR exists, the &lt;a href="https://qa.tech/product/mcp" rel="noopener noreferrer"&gt;MCP server&lt;/a&gt; lets Claude Code, Cursor or Codex run the same tests against a local dev server. Projects without previews can run the review after merge against staging. The free trial covers web and PR testing, and Starter is $89 a month (as of November 2026).&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fits&lt;/strong&gt;: teams on Vercel or Netlify who want every agent-written PR tested on its preview, with the verdict as a required check.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Checkly (Vercel integration)
&lt;/h2&gt;

&lt;p&gt;Checkly runs Playwright-based browser checks and API checks, and its &lt;a href="https://www.checklyhq.com/docs/integrations/ci-cd/vercel/overview/" rel="noopener noreferrer"&gt;Vercel integration&lt;/a&gt; runs linked checks whenever a preview deploys, while they keep running on a schedule against production.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it hooks in&lt;/strong&gt;. Checkly links its checks to Vercel's Checks API, so results show in both tools, and "you can block your Vercel deployments if any of your checks fail or if the web vitals degrade." For other hosts, Checkly listens for &lt;a href="https://www.checklyhq.com/docs/integrations/ci-cd/github/deployments/" rel="noopener noreferrer"&gt;successful GitHub deployment events&lt;/a&gt; and passes the preview address to browser checks as &lt;code&gt;ENVIRONMENT_URL&lt;/code&gt;. Its docs don't mention Netlify by name.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Protection&lt;/strong&gt;. Checkly's &lt;a href="https://www.checklyhq.com/docs/integrations/ci-cd/vercel/deployment-protection/" rel="noopener noreferrer"&gt;deployment protection guide&lt;/a&gt; uses Vercel's bypass secret in the request header.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reality check&lt;/strong&gt;. Checkly itself recommends its CLI in your CI pipeline over the connected integration, which lacks private locations and client certificates. You write and maintain the Playwright scripts. The Hobby plan needs no card (as of November 2026).&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fits&lt;/strong&gt;: Vercel teams that already script Playwright and want the same checks on previews and in production.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Meticulous
&lt;/h2&gt;

&lt;p&gt;Meticulous records real sessions from your app and replays them against each PR's preview, before and after the change, to catch visual differences.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it hooks in&lt;/strong&gt;. Per its &lt;a href="https://app.meticulous.ai/docs/cloud-replay" rel="noopener noreferrer"&gt;cloud replay docs&lt;/a&gt;, you install the Meticulous Vercel integration and link the project. Netlify works through a webhook on preview deploys, set up with Meticulous support.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verdict&lt;/strong&gt;. On GitHub it comments on the PR with the changes it found, and the check can be made blocking, so nobody merges a visual difference without acknowledging it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reality check&lt;/strong&gt;. The &lt;a href="https://www.meticulous.ai/" rel="noopener noreferrer"&gt;homepage&lt;/a&gt; promises "Never write, fix or maintain a test again." Coverage depends on a recorder script running in your local, staging and preview environments, and a replay shows what changed on screen, leaving a person to judge whether the change was intended. The docs reviewed don't cover protected previews. Getting started goes through a demo booking.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fits&lt;/strong&gt;: frontend-heavy web apps where unintended visual change is the main risk.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Playwright in GitHub Actions
&lt;/h2&gt;

&lt;p&gt;The do-it-yourself route: a workflow that triggers on &lt;code&gt;deployment_status&lt;/code&gt; (or Vercel's &lt;code&gt;repository_dispatch&lt;/code&gt;), checks for a successful state and runs &lt;code&gt;npx playwright test&lt;/code&gt; with the preview address as the base URL. Vercel's &lt;a href="https://vercel.com/docs/git/vercel-for-github#migrating-from-deployment_status" rel="noopener noreferrer"&gt;GitHub docs&lt;/a&gt; show both versions, and its bypass page includes a Playwright config that sends both headers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reality check&lt;/strong&gt;. You own every piece: the readiness logic, unique job names (Vercel warns that duplicate names across workflows race with branch protection), the secrets and every selector. When a coding agent rebuilds the onboarding flow, someone rewrites the scripts.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fits&lt;/strong&gt;: teams with test engineers who want full control and already maintain a Playwright suite.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The platform baseline: Vercel and Netlify's own tools
&lt;/h2&gt;

&lt;p&gt;None of these tests a user journey, but they come with the platform and are worth switching on.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Vercel Deployment Checks&lt;/strong&gt; hold production promotion until selected GitHub checks pass on the merged commit, so a test failure can also stop the release.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vercel Comments&lt;/strong&gt; let reviewers leave feedback on &lt;a href="https://vercel.com/docs/git/vercel-for-github" rel="noopener noreferrer"&gt;preview deployments made from GitHub PRs&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Netlify Drawer&lt;/strong&gt; lets your team comment, take screenshots and video and check mobile responsiveness on a &lt;a href="https://docs.netlify.com/deploy/review-deploys/netlify-drawer-for-feedback/overview/" rel="noopener noreferrer"&gt;Deploy Preview&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Netlify's Lighthouse plugin&lt;/strong&gt; &lt;a href="https://docs.netlify.com/manage/monitoring/lighthouse/" rel="noopener noreferrer"&gt;audits performance, SEO and accessibility&lt;/a&gt; and puts scores in the PR's deploy comment. It doesn't support paths behind a login, so it can't reach the checkout.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fits&lt;/strong&gt;: every team, as the floor under PR testing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Setup checklist for testing Vercel and Netlify previews
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Bypass secret&lt;/strong&gt;. On Vercel, create a named Protection Bypass for Automation secret per tool, send it as a header and add &lt;code&gt;x-vercel-set-bypass-cookie: true&lt;/code&gt; for browser tests. Store it as a secret, never in a URL, and redeploy after rotating. On Netlify, choose a previews-only password or public previews before you connect a tool.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Readiness gate&lt;/strong&gt;. Start tests only when every deploy for the PR head commit is green. Don't add your own deployment records on top of a platform integration that already reports success, and point records at the PR head SHA, not the merge commit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Required checks&lt;/strong&gt;. Make the PR testing check required in branch protection. For the release, add the GitHub check that runs on the merged commit to Vercel Deployment Checks, so production promotion waits for it too. Give every job a unique name. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A short pinned set&lt;/strong&gt;. Pin sign-up, login, checkout and billing as blocking flows; let dynamic and exploratory tests report on everything else.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  AI testing tools for Vercel and Netlify previews compared
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Vercel previews&lt;/th&gt;
&lt;th&gt;Netlify previews&lt;/th&gt;
&lt;th&gt;Protected previews&lt;/th&gt;
&lt;th&gt;Verdict on the PR&lt;/th&gt;
&lt;th&gt;Who maintains tests&lt;/th&gt;
&lt;th&gt;How you start (Nov 2026)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;QA.tech&lt;/td&gt;
&lt;td&gt;Detected automatically&lt;/td&gt;
&lt;td&gt;Detected automatically&lt;/td&gt;
&lt;td&gt;Bypass headers copied to every preview; Netlify password or public&lt;/td&gt;
&lt;td&gt;Required "QA.tech / PR Review" check plus comment, diff-anchored&lt;/td&gt;
&lt;td&gt;QA agents follow the goal; you pin critical flows&lt;/td&gt;
&lt;td&gt;Free trial; self-serve Starter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Checkly&lt;/td&gt;
&lt;td&gt;Connected integration or CLI&lt;/td&gt;
&lt;td&gt;Not documented&lt;/td&gt;
&lt;td&gt;Bypass header in your scripts&lt;/td&gt;
&lt;td&gt;Vercel checks; optional PR comment from GitHub deployment runs&lt;/td&gt;
&lt;td&gt;Your team (Playwright)&lt;/td&gt;
&lt;td&gt;Free Hobby plan, no card&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Meticulous&lt;/td&gt;
&lt;td&gt;Vercel integration&lt;/td&gt;
&lt;td&gt;Webhook, set up with support&lt;/td&gt;
&lt;td&gt;Not documented&lt;/td&gt;
&lt;td&gt;PR comment; blocking check optional&lt;/td&gt;
&lt;td&gt;Generated from recorded sessions&lt;/td&gt;
&lt;td&gt;Demo first&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Playwright in Actions&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;deployment_status&lt;/code&gt; or &lt;code&gt;repository_dispatch&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Commit status or webhook&lt;/td&gt;
&lt;td&gt;Bypass header in config&lt;/td&gt;
&lt;td&gt;Whatever check you build&lt;/td&gt;
&lt;td&gt;Your team&lt;/td&gt;
&lt;td&gt;Your own GitHub Actions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Platform tools&lt;/td&gt;
&lt;td&gt;Deployment Checks, Comments&lt;/td&gt;
&lt;td&gt;Drawer, Lighthouse plugin&lt;/td&gt;
&lt;td&gt;Not applicable&lt;/td&gt;
&lt;td&gt;Production gate; scores in comment&lt;/td&gt;
&lt;td&gt;Not applicable&lt;/td&gt;
&lt;td&gt;Included&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How to choose a testing tool for preview deployments
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Start from what escapes&lt;/strong&gt;. If agents ship broken journeys, such as a sign-up that loops after email confirmation, you need a tool that walks the journey on the preview. If the risk is unintended visual change, Meticulous fits. If it's a slow or broken page load, Checkly or Lighthouse.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check protection first&lt;/strong&gt;. Open a preview in a private window. If you meet a login, confirm the tool's documented way through before connecting it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ask how a skipped change is reported&lt;/strong&gt;. A pass on a preview where the changed code never ran proves nothing; ask vendors how they mark that case.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Count the upkeep&lt;/strong&gt;. Scripted suites, yours or a vendor's, need someone to fix them after every redesign. Be wary of "self-healing" as the answer: QA.tech's piece on &lt;a href="https://qa.tech/blog/self-healing-tests-misconceptions" rel="noopener noreferrer"&gt;self-healing misconceptions&lt;/a&gt; covers how a wrong repair can stay green.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it on live previews&lt;/strong&gt;. QA.tech and Checkly can both be started without a sales call. Connect one and leave it running on a week of real PRs before you decide.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;How do I run tests on Vercel preview deployments?&lt;/strong&gt;&lt;br&gt;
Trigger on the event Vercel sends to GitHub, &lt;code&gt;deployment_status&lt;/code&gt; or &lt;code&gt;repository_dispatch&lt;/code&gt; with &lt;code&gt;vercel.deployment.success&lt;/code&gt;, and use the URL it carries as your base URL. Tools like QA.tech and Checkly handle the trigger for you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do I bypass Vercel deployment protection for automated tests?&lt;/strong&gt;&lt;br&gt;
Turn on Protection Bypass for Automation in the project's Deployment Protection settings, available on all plans, and send the secret in the &lt;code&gt;x-vercel-protection-bypass&lt;/code&gt; header. Browser tests also send &lt;code&gt;x-vercel-set-bypass-cookie: true&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can automated tests access private Netlify Deploy Previews?&lt;/strong&gt;&lt;br&gt;
Not easily: private previews sit behind Netlify team login, and Netlify documents no automation bypass. Set a shared password with "Previews only" scope (Pro) and have your tool enter it, or make previews public.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do Vercel Deployment Checks test pull requests?&lt;/strong&gt;&lt;br&gt;
No. They hold a production deployment back from your domains until selected GitHub checks pass. Pair them with a required PR testing check, so testing gates both the merge and the release.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does Netlify's Lighthouse plugin replace end-to-end testing?&lt;/strong&gt;&lt;br&gt;
No. It scores performance, SEO and accessibility on pages it can reach, not behind a login, and won't tell you whether checkout still completes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's the best AI testing tool for Vercel and Netlify previews?&lt;/strong&gt;&lt;br&gt;
For testing user journeys on every preview with a required verdict on the PR, QA.tech detects both platforms automatically and applies your Vercel bypass secret to every preview once you set it. Checkly suits teams that script Playwright on Vercel, and Meticulous suits visual regression on frontend apps.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>devops</category>
      <category>automation</category>
    </item>
    <item>
      <title>Airbyte Pricing vs Estuary Pricing for High-Volume CDC</title>
      <dc:creator>Jaume Boguñá</dc:creator>
      <pubDate>Fri, 06 Nov 2026 16:38:52 +0000</pubDate>
      <link>https://dev.to/jaume_bogu/airbyte-pricing-vs-estuary-pricing-for-high-volume-cdc-3fen</link>
      <guid>https://dev.to/jaume_bogu/airbyte-pricing-vs-estuary-pricing-for-high-volume-cdc-3fen</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftte57lf5hmygv1nv0m3i.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftte57lf5hmygv1nv0m3i.png" alt="cover" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://airbyte.com/pricing" rel="noopener noreferrer"&gt;Airbyte&lt;/a&gt; sells pay-per-use plans on Standard and Plus, and capacity-based plans on Pro and Enterprise Flex. &lt;a href="https://estuary.dev/pricing/" rel="noopener noreferrer"&gt;Estuary&lt;/a&gt; charges per gigabyte and per connector instance, and counts each gigabyte twice, once on capture and once on delivery.&lt;/p&gt;

&lt;h2&gt;
  
  
  Airbyte vs Estuary: High-Volume Pricing at a Glance
&lt;/h2&gt;

&lt;p&gt;At high volume, the two meters pull apart, and the entry price tells you little. Two inputs decide which bill is larger: how many destinations one source feeds, and how fresh the slowest consumer needs its data. &lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-credits" rel="noopener noreferrer"&gt;Airbyte&lt;/a&gt;'s credit table meters 1 GB of database data at 4 credits. Estuary's Cloud plan counts that gigabyte twice at $0.50 each time, as of October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Airbyte vs Estuary Pricing Models Explained
&lt;/h2&gt;

&lt;p&gt;Airbyte positions Standard and Plus for smaller teams with predictable data volumes. &lt;a href="https://airbyte.com/pricing" rel="noopener noreferrer"&gt;Airbyte's pricing page&lt;/a&gt; pitches its enterprise plans at large organizations with higher data volumes, priced on compute capacity. Those plans carry no charges based on data volume. Once a team consumes &lt;a href="https://airbyte.com/pricing" rel="noopener noreferrer"&gt;40 or more credits a month&lt;/a&gt;, Airbyte says Plus is typically more affordable than Standard.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-credits" rel="noopener noreferrer"&gt;Airbyte's billing documentation&lt;/a&gt; says the volume it measures is likely a larger representation of your data than a direct query would show. A Full Refresh sync of an API or custom source charges for every row synced. Airbyte Cloud starts with a trial of &lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-credits" rel="noopener noreferrer"&gt;14 days or 400 trial credits&lt;/a&gt;, whichever comes first.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://estuary.dev/pricing/" rel="noopener noreferrer"&gt;Estuary's pricing page&lt;/a&gt; lists the Cloud plan at &lt;a href="https://docs.estuary.dev/getting-started/pricing/" rel="noopener noreferrer"&gt;$0.50 per GB&lt;/a&gt; of data plus $100 per connector instance a month, as of October 2026. Estuary counts data each time it is captured and again each time it is delivered, including data produced by transformations. A derivation is not a connector instance, but the data it produces still counts as volume.&lt;/p&gt;

&lt;p&gt;An Estuary connector instance is one configured source or one configured destination, prorated by the hour. A single capture can pull from many tables and still count as one instance. A Postgres to Snowflake pipeline with 500 tables therefore uses 2 connector instances.&lt;/p&gt;

&lt;p&gt;Every GB captured and every GB delivered to a destination carries the same charge. Each active connector instance adds a flat fee. The same page lists a free tier of 10 GB a month and 2 connector instances with no credit card required. A third active source or destination exceeds the free tier. Instances three to six cost $100 a month as of October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Airbyte vs Estuary Pricing Comparison
&lt;/h2&gt;

&lt;p&gt;Every rate in the table is as of October 2026.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Vendor&lt;/th&gt;
&lt;th&gt;Metered unit&lt;/th&gt;
&lt;th&gt;Published rate (as of October 2026)&lt;/th&gt;
&lt;th&gt;Connector or connection fee&lt;/th&gt;
&lt;th&gt;Entry cost&lt;/th&gt;
&lt;th&gt;Latency floor&lt;/th&gt;
&lt;th&gt;High-volume terms&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;&lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-data-workers" rel="noopener noreferrer"&gt;Airbyte&lt;/a&gt;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Pay-per-use on Standard and Plus; capacity on Pro and Enterprise Flex&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-credits" rel="noopener noreferrer"&gt;4 credits per GB of database data&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;14-day or 400-credit trial&lt;/td&gt;
&lt;td&gt;&lt;a href="https://airbyte.com/pricing" rel="noopener noreferrer"&gt;5-minute scheduled syncs on Pro and Enterprise Flex&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Capacity enforced per region; &lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-data-workers" rel="noopener noreferrer"&gt;premium rate for on-demand overflow&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Estuary&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;GB captured and GB delivered&lt;/td&gt;
&lt;td&gt;&lt;a href="https://estuary.dev/pricing/" rel="noopener noreferrer"&gt;$0.50 per GB captured and per GB delivered&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://estuary.dev/pricing/" rel="noopener noreferrer"&gt;$100 per connector instance a month, $50 after the sixth&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;10 GB and 2 connector instances a month, free&lt;/td&gt;
&lt;td&gt;Sub-second to slower schedules, set per destination&lt;/td&gt;
&lt;td&gt;Committed-use discounts on annual plans; custom Enterprise terms&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Read the connector fee and the high-volume terms first, because that is where the bills separate. Every cell in the table comes from a vendor pricing or documentation page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Airbyte vs Estuary: Sync Frequency and Latency
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://docs.airbyte.com/platform/understanding-airbyte/cdc" rel="noopener noreferrer"&gt;Airbyte's CDC documentation&lt;/a&gt; says Airbyte does not treat CDC sources as infinite streaming sources. &lt;a href="https://airbyte.com/pricing" rel="noopener noreferrer"&gt;Airbyte’s shortest scheduled sync interval&lt;/a&gt; is 1 hour on Standard, 15 minutes on Plus, and 5 minutes on Pro and Enterprise Flex.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.airbyte.com/integrations/sources/postgres" rel="noopener noreferrer"&gt;Airbyte&lt;/a&gt; uses logical replication of the Postgres write-ahead log to incrementally capture deletes. &lt;a href="https://docs.airbyte.com/integrations/sources/postgres" rel="noopener noreferrer"&gt;Airbyte's Postgres connector documentation&lt;/a&gt; recommends that method for databases larger than 500 GB. &lt;a href="https://docs.airbyte.com/platform/understanding-airbyte/cdc" rel="noopener noreferrer"&gt;Incremental CDC also needs&lt;/a&gt; primary keys on most sources, so a table without one is not a CDC candidate.&lt;/p&gt;

&lt;p&gt;Estuary charges no extra for millisecond latency or batch delivery. Delivery latency is set per destination, from sub-second to slower schedules. A single source can feed a dashboard at sub-second latency and an archive on a slower schedule.&lt;/p&gt;

&lt;p&gt;Airbyte's fastest plan still runs on a &lt;a href="https://airbyte.com/pricing" rel="noopener noreferrer"&gt;5-minute schedule&lt;/a&gt;, while Estuary sets delivery latency per destination.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Airbyte and Estuary Costs Scale with Multiple Destinations
&lt;/h2&gt;

&lt;p&gt;In &lt;a href="https://docs.airbyte.com/platform/move-data/add-connection" rel="noopener noreferrer"&gt;Airbyte&lt;/a&gt;, a connection pairs a source with a destination and syncs data from the source to the destination.&lt;/p&gt;

&lt;p&gt;Estuary supports one-to-many replication, so a single source can feed several destinations at once. Each active source or destination counts as one connector instance, prorated by the hour.&lt;/p&gt;

&lt;p&gt;Suppose a Postgres source produces 1 TB of changes a month, and both Snowflake and a search index need the full dataset. Airbyte uses two connections, each of which reads the same changes from Postgres. That doubles the source reads and metered volume compared with syncing to one destination: 2,000 GB in total, or 8,000 credits at &lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud" rel="noopener noreferrer"&gt;4 credits per GB&lt;/a&gt;. On &lt;a href="https://github.com/airbytehq/airbyte/blob/master/docs/release_notes/cloud/readme.md#september-15-2026" rel="noopener noreferrer"&gt;Airbyte Standard&lt;/a&gt;, that comes to $39,995 a month: $20 for the plan, including 5 credits, plus $5 for each of the remaining 7,995 credits. This estimate is specific to Standard; Plus packages and capacity-based plans are priced differently. Airbyte Docs&lt;/p&gt;

&lt;p&gt;Estuary captures the changes from Postgres once and delivers them to both destinations. Assuming 1,000 GB captured and 1,000 GB processed for each destination, Estuary bills 3,000 GB. At &lt;a href="https://docs.estuary.dev/getting-started/pricing/" rel="noopener noreferrer"&gt;Estuary’s Cloud rates&lt;/a&gt;, that comes to $1,800 a month: $1,500 for data and $300 for one source and two destination connectors running for the full month.&lt;/p&gt;

&lt;p&gt;A fan-out to three destinations is three connections on Airbyte and four connector instances on Estuary.&lt;/p&gt;

&lt;h2&gt;
  
  
  What high-volume CDC pricing comes to at scale
&lt;/h2&gt;

&lt;p&gt;Suppose the source changes 1 TB a month into one destination. Estuary's meter counts 2 TB, once on capture and once on delivery, before the instance fee. Airbyte's bill for the same change depends on which plan runs the sync and which region runs it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-data-workers" rel="noopener noreferrer"&gt;Airbyte's data worker documentation&lt;/a&gt; says each region gets its own allocation, so one region can be full while another has headroom. When committed capacity is exhausted, syncs queue by default. Connections with &lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-data-workers" rel="noopener noreferrer"&gt;on-demand capacity&lt;/a&gt; enabled can run immediately at a premium rate.&lt;/p&gt;

&lt;p&gt;On the credit plans, running out does not stop a sync: Airbyte keeps it running and bills in arrears. Once credit usage passes $10,000 in a billing period, Airbyte charges the saved payment method automatically, as of October 2026.&lt;/p&gt;

&lt;p&gt;Enterprise Flex adds in-boundary and hybrid deployment, including a model with an Airbyte-managed control plane.&lt;/p&gt;

&lt;p&gt;Estuary discounts committed usage on annual plans. Its Enterprise terms are custom and keyed to data volume, connector instances, deployment model, contract length, and support needs. Private and BYOC deployments require an annual or multi-year Enterprise contract.&lt;/p&gt;

&lt;p&gt;Airbyte removes the volume charge inside committed capacity and prices the overflow at a premium. On Standard and Plus, the same terabyte meters at &lt;a href="https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/manage-credits" rel="noopener noreferrer"&gt;4 credits&lt;/a&gt;. Enterprise Flex meter data workers instead. Estuary's Cloud rate is $0.50 per GB as of October 2026, and its annual plans carry volume discounts on committed usage.&lt;/p&gt;

&lt;h2&gt;
  
  
  Airbyte vs Estuary pricing: which one to pick
&lt;/h2&gt;

&lt;p&gt;Pick Estuary if one source has to feed several destinations, or if any consumer needs changes within seconds.&lt;/p&gt;

&lt;p&gt;Pick Airbyte if every consumer tolerates a scheduled sync. Standard and Plus suit smaller teams with predictable volumes. Pro and Enterprise Flex fit large organizations that would rather buy compute capacity than gigabytes.&lt;/p&gt;

&lt;p&gt;Either way, price the pipeline on the metered units and the destination count, not the entry price. Count the destinations, decide how fresh the slowest consumer needs its data, and read the rate for the plan you would run. Compare a credit rate against a per-GB rate counted twice, and an instance fee against a connection model.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;Airbyte's rate card is in credits and Estuary's in dollars.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Airbyte free?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Airbyte Open Source, the self-hosted edition, is free to use, but you cover the infrastructure costs and the engineering time needed to run and maintain it. Airbyte Cloud starts with a trial that lasts 14 days or 400 trial credits, whichever comes first. Standard and Plus are pay-per-use plans for smaller teams with predictable data volumes. Airbyte says Plus is typically more affordable than Standard at 40 or more credits a month. Pro and Enterprise Flex are capacity-based plans that use data workers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How much does a gigabyte of database data cost on Airbyte?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Airbyte's credit table meters 1 GB of database data at 4 credits, as of October 2026. Its docs say that form is likely larger than what a direct query returns. The page states the rate in credits instead of dollars, so you need your plan's credit price to finish the math.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does Airbyte charge for full refreshes?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes, for Full Refresh syncs of API and custom sources. Every row synced is charged, so re-reading a whole table bills the full row count again. Database sources are metered by volume instead. Each GB of database data costs 4 credits, as of October 2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Estuary cheaper than Airbyte for high-volume CDC?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It depends on the meter and the destination count, not on a single headline rate. Estuary's own example bills 100 GB a month from Postgres to Snowflake as 200 GB of data and 2 connector instances. That comes to $300 a month as of October 2026. On Airbyte, 1 GB of database data is 4 credits. Airbyte charges per credit on some plans and by capacity on Pro and Enterprise Flex.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What counts as an Estuary connector instance?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Every active source or destination counts as one connector instance, prorated by the hour. The table count does not change that. A single capture can pull from many tables and still count as one instance. A Postgres to Snowflake pipeline with 500 tables uses 2 connector instances. The data produced by transformations still counts toward your volume.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can you run either tool in your own cloud account?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Airbyte's Enterprise Flex adds in-boundary and hybrid deployment, including a model with an Airbyte-managed control plane. Estuary's private and BYOC deployments require an annual or multi-year Enterprise contract. Both enterprise options require a contract.&lt;/p&gt;

</description>
      <category>dataengineering</category>
      <category>etl</category>
      <category>cloud</category>
      <category>database</category>
    </item>
    <item>
      <title>How to Replace Expensive LLM Calls in Financial Document Processing</title>
      <dc:creator>Jaume Boguñá</dc:creator>
      <pubDate>Mon, 12 Oct 2026 13:49:20 +0000</pubDate>
      <link>https://dev.to/jaume_bogu/how-to-replace-expensive-llm-calls-in-financial-document-processing-625</link>
      <guid>https://dev.to/jaume_bogu/how-to-replace-expensive-llm-calls-in-financial-document-processing-625</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Inventory LLM calls by task, volume and variance. Move high-volume, fixed-output tasks such as PDF page classification, entity tagging, OCR and relevance judging to specialist models on Superlinked Inference Engine: one API for OCR, extraction, embeddings and reranking, on SIE Cloud or self-hosted on your own GPUs. Shadow-run against a gold set, then route by confidence.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Open the usage breakdown for a pipeline that ingests PDF annual reports and client decks, and one line stands out. It is not the analyst chat, and it is not the summary of the chairman's letter. It is a page classifier, asking a frontier model "is this the income statement?" on each page of each PDF that comes in. Each call is cheap and nearly identical to the last. There are a great many of them. The model answering has read most of the public internet, and it is being paid to recognise a table heading it could find with its eyes closed.&lt;/p&gt;

&lt;p&gt;For US filers on EDGAR, that call should not exist at all. Each XBRL filing ships a &lt;code&gt;FilingSummary.xml&lt;/code&gt; and a set of rendered R files that name every statement, and the presentation linkbase orders the line items within each one. The statement map is free. The classifier earns its keep only where no such metadata exists: foreign annual reports published as PDFs, investor decks, data-room uploads and scanned exhibits.&lt;/p&gt;

&lt;p&gt;That is the typical shape of an expensive document pipeline: a general model doing high-volume, low-variance work because it was the fastest thing to wire up during the prototype. The fix is to move that work onto specialist models on SIE, one task at a time, with evidence that the replacement holds up on your documents.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 0: Take the cheap discounts before migrating anything
&lt;/h2&gt;

&lt;p&gt;Before you move a single task, check two things with your current provider.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt caching.&lt;/strong&gt; Classification and extraction prompts are mostly fixed text: the instructions, the label set, the output schema and a few examples, followed by a short page. Put the fixed part first and keep it byte-identical across calls, and the major hosted providers bill the cached prefix at a reduced rate. On a prompt that is 90% boilerplate, record that discounted rate, then inventory what still belongs on specialist models.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Batch pricing.&lt;/strong&gt; Most of this work is not interactive. A quarter's worth of PDFs does not need answers within a second. OpenAI's Batch API and its equivalents at other providers charge about half the synchronous price in exchange for a completion window of up to a day.&lt;/p&gt;

&lt;p&gt;Also check the obvious: whether you are sending pages that never needed a model, such as EDGAR statements already named in the R files, or cover pages and blank separators a simple rule can drop. Measure the bill after these changes. Everything below is worth doing only on what is left.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Inventory the calls by task, volume and variance
&lt;/h2&gt;

&lt;p&gt;You cannot choose what to move until you can see what you are calling. Tag every LLM request with a task name, then pull a month of logs and build a table. The volumes below are invented, to show the shape rather than any real pipeline:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;strong&gt;Task&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Monthly calls (illustrative)&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Output shape&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Input variance&lt;/strong&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;PDF page classification (which statement is this?)&lt;/td&gt;
&lt;td&gt;2,000,000&lt;/td&gt;
&lt;td&gt;one label from a fixed set&lt;/td&gt;
&lt;td&gt;low&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Entity tagging (company, auditor, dates)&lt;/td&gt;
&lt;td&gt;600,000&lt;/td&gt;
&lt;td&gt;spans with labels&lt;/td&gt;
&lt;td&gt;low&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Table field extraction (revenue, net income, EPS)&lt;/td&gt;
&lt;td&gt;400,000&lt;/td&gt;
&lt;td&gt;fixed JSON schema&lt;/td&gt;
&lt;td&gt;medium&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LLM relevance judging on retrieved chunks&lt;/td&gt;
&lt;td&gt;300,000&lt;/td&gt;
&lt;td&gt;a score or yes/no&lt;/td&gt;
&lt;td&gt;low&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analyst Q&amp;amp;A across several filings&lt;/td&gt;
&lt;td&gt;20,000&lt;/td&gt;
&lt;td&gt;free text&lt;/td&gt;
&lt;td&gt;high&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Summaries of management discussion&lt;/td&gt;
&lt;td&gt;15,000&lt;/td&gt;
&lt;td&gt;free text&lt;/td&gt;
&lt;td&gt;high&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The pattern usually holds even when the numbers differ: the highest-volume tasks tend to have the smallest output space, which is the work specialist models on SIE take.&lt;/p&gt;

&lt;p&gt;Record variance honestly. A task with low variance sees inputs that look alike and produces outputs from a small, fixed space. A task with high variance sees new layouts, open questions or reasoning across several tables and several filings.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Pick candidates with fixed outputs you can check
&lt;/h2&gt;

&lt;p&gt;A task is a good candidate when all three hold:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;fixed output:&lt;/strong&gt; the answer comes from a closed label set or a fixed schema&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;high volume:&lt;/strong&gt; it runs many times a month on similar inputs&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;mechanically checkable:&lt;/strong&gt; you can score the output against a label without a person reading prose&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;PDF page classification, entity tagging, relevance judging and table field extraction are the tasks to move onto specialist models on SIE.&lt;/p&gt;

&lt;p&gt;Map each candidate to the kind of specialist model that fits it: a small generative model or a trained classifier for page types, a zero-shot entity model such as GLiNER2 or NuNER_Zero for entity tagging, a cross-encoder reranker in place of an LLM asked "is this chunk relevant?", and a document model plus a structured-output model for table fields. The reranker swap is often the easiest win. A cross-encoder returns a calibrated score per query-chunk pair, which is what the LLM judge was being prompted to imitate.&lt;/p&gt;

&lt;p&gt;Start with the task that has the highest volume and the simplest output. In a PDF-heavy pipeline, that is usually page classification.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Build the evaluation set first
&lt;/h2&gt;

&lt;p&gt;Do not move a task without a gold set for it. For field extraction, the companion guide in this series on evaluating extraction accuracy covers the method in detail: seed labels from XBRL facts where filings have them, add hand-labelled PDF pages, and score value, scale, unit, sign, period and entity separately. For classification and tagging, a few hundred labelled pages or passages per class is a sensible start. For relevance judging, take a sample of real queries and have a person grade the retrieved chunks.&lt;/p&gt;

&lt;p&gt;Include the pages that currently cause trouble: statements split across two pages, restated comparatives, a segment note that looks like a primary statement. A replacement has to hold on those pages, not only on the clean ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Shadow-run the specialist
&lt;/h2&gt;

&lt;p&gt;Run the specialist model on SIE in parallel with the current model, without using the specialist output yet. Log both answers per request. After a week or two, you have three comparisons:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;both models against the gold set&lt;/li&gt;
&lt;li&gt;the specialist against the current model on live traffic, where no label exists&lt;/li&gt;
&lt;li&gt;latency and failure rates for both&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Disagreements on live traffic are the most valuable output of the shadow run. Sample them, label them, and add them to the gold set. They show you where to tighten the schema or swap the model ID on the same SIE client.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Route by confidence
&lt;/h2&gt;

&lt;p&gt;Few cutovers need to be all or nothing. Most specialist models give you a confidence signal: a classifier score, a reranker score, an entity model's span confidence, or a structured-output model returning null for a missing field. Use it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;high confidence: take the specialist's answer&lt;/li&gt;
&lt;li&gt;low confidence or null: route to review&lt;/li&gt;
&lt;li&gt;log every review, with the input, so those cases become the next gold-set rows&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Tune the threshold on the gold set to hit the accuracy you need, and watch what fraction of traffic goes to review. If that rate is high, narrow the task or try the next catalog model on the same SIE client.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Cut over and keep monitoring
&lt;/h2&gt;

&lt;p&gt;When the specialist meets its accuracy threshold and the fallback rate is stable, make it the default path. Then keep watching:&lt;/p&gt;

&lt;p&gt;☐ weekly accuracy on a rotating sample of production traffic, labelled by a person&lt;/p&gt;

&lt;p&gt;☐ fallback rate per task, with an alert when it moves&lt;/p&gt;

&lt;p&gt;☐ a rerun of the gold set on any model, prompt or parser change&lt;/p&gt;

&lt;p&gt;☐ a check after each reporting season, since new layouts arrive in batches&lt;/p&gt;

&lt;p&gt;Budget for the migration costs too. If the move also changes how you retrieve, for example a new embedding model alongside the new reranker, that means re-embedding and reindexing the corpus. Any new model means a new evaluation cycle. These are one-off costs, but they are real, and they belong in the plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where SIE fits
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpopwer3znicouovewmo1.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpopwer3znicouovewmo1.webp" alt="superlinked homepage" width="800" height="360"&gt;&lt;/a&gt;&lt;/p&gt;
Superlinked homepage, featuring the SIE inference engine.



&lt;p&gt;Once you have carved tasks off the frontier model, they need somewhere to run. Moving four tasks to four vendors trades one bill for four integrations. SIE, from &lt;a href="https://superlinked.com/" rel="noopener noreferrer"&gt;Superlinked&lt;/a&gt;, serves them behind one API: reranking, entity extraction, OCR, document-to-Markdown and structured output, alongside embeddings. You can use it as a managed service on SIE Cloud, self-host it in your own VPC, or run it locally. On SIE Cloud, per the Cloud pricing page (verified 2026-09-30), GLiNER2 Large is listed at $0.186 per million input tokens for entity extraction, Qwen3-Reranker-0.6B at $6.63 per million pairs (a top-50 rerank is 50 pairs, so about $0.0003 per query), LightOnOCR-2-1B at $2 per 1,000 pages, and Qwen3.8-27B (FP8), which backs doc field extraction, at $0.72 per million tokens in and out. Treat those as the unit prices in your inventory.&lt;/p&gt;

&lt;p&gt;For tasks that already run through the OpenAI SDK, the Cloud page shows a migration pattern that only changes the base URL. For a priced Cloud shadow run, use Qwen3.8-27B (FP8) through the native SDK's chat call. Once its labels agree with your current model, a smaller catalog model such as GLiNER2's classification task is a strong production path on the same API. A shadow page classifier looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;sie_sdk&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;SIEClient&lt;/span&gt;

&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;SIEClient&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"sk-sie-…"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"https://api.superlinked.com"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;shadow&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;chat_completions&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="s2"&gt;"Qwen/Qwen3.8-27B-FP8"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;page_classification_messages&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;max_completion_tokens&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;16&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;label&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;shadow&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"choices"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"content"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Entity tagging uses the native SDK's &lt;code&gt;extract&lt;/code&gt; call with a label list, and relevance judging uses &lt;code&gt;score&lt;/code&gt;, as the &lt;a href="https://superlinked.com/docs" rel="noopener noreferrer"&gt;SIE docs&lt;/a&gt; show. The engine is open source under Apache 2.0 (&lt;a href="https://github.com/superlinked/sie" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;), so a task you move to Cloud can move to a self-hosted cluster later with the same model IDs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Honest take:&lt;/strong&gt; SIE is the destination for the tasks you move off a general model: OCR, extraction, embeddings and reranking behind one API. On SIE Cloud, Superlinked runs the GPUs and you pay per token, pair or page, with GLiNER2, the Qwen3 rerankers, LightOnOCR-2-1B and Qwen3.8-27B (FP8) on the price list. Self-host the same Apache 2.0 engine on your own GPUs, and a task you shadowed on Cloud moves to your cluster with the same model IDs. The weights are open and pinned. Page classification, entity tagging and relevance judging share that client with document conversion and field extraction, so four tasks stay on one vendor.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQs
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Which call should we move first?
&lt;/h3&gt;

&lt;p&gt;The one with the highest volume and the simplest output that free metadata does not already answer. For EDGAR filings, check first whether the R files and presentation linkbase make page classification unnecessary. For PDF annual reports and decks, page classification is usually first: a small, fixed label set, high volume, and errors that break something visibly downstream. Score table field extraction on a field-level gold set, then run that extractor on the same SIE client.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why not just turn on caching and batch and stop there?
&lt;/h3&gt;

&lt;p&gt;Run Step 0 so the inventory reflects discounted rates. Page classification, entity tagging and relevance judging are still high-volume, fixed-output work, and SIE serves those specialist models behind one API, on Cloud or on your own GPUs. The per-call prices on SIE Cloud are what you set next to the current bill.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does this just move the operational burden onto us?
&lt;/h3&gt;

&lt;p&gt;On SIE Cloud, Superlinked runs the GPUs. Self-hosting the same Apache 2.0 engine on your own Kubernetes cluster, as the &lt;a href="https://superlinked.com/docs/deployment" rel="noopener noreferrer"&gt;deployment guide&lt;/a&gt; describes, keeps documents and model IDs in your environment. Running locally suits development. Evaluation and routing stay in your code either way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pay the frontier price only for frontier work
&lt;/h2&gt;

&lt;p&gt;The expensive part of most document pipelines is easy work done at volume. Use EDGAR metadata where it exists, inventory what is left, build the gold set, shadow-run, and route by confidence. SIE is where those specialist tasks run: one API, open weights, Cloud or your own GPUs. &lt;a href="https://superlinked.com/serverless" rel="noopener noreferrer"&gt;SIE Cloud&lt;/a&gt; prices each one per token, pair or page, so you can put those figures next to your current bill.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>programming</category>
    </item>
    <item>
      <title>Fivetran vs Estuary for Real-Time ETL</title>
      <dc:creator>Jaume Boguñá</dc:creator>
      <pubDate>Wed, 07 Oct 2026 17:20:10 +0000</pubDate>
      <link>https://dev.to/jaume_bogu/fivetran-vs-estuary-for-real-time-etl-4ecj</link>
      <guid>https://dev.to/jaume_bogu/fivetran-vs-estuary-for-real-time-etl-4ecj</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Quick answer&lt;/strong&gt;: Estuary is the better tool for real-time ETL when a consumer needs database changes in seconds: it streams log-based CDC continuously, sub-100 ms in streaming mode per its figure, with a batch schedule you set per destination. Fivetran's managed product is scheduled ELT with a one-minute floor on its two top plans. Pick Fivetran when every consumer can wait for the next sync and your sources are long-tail SaaS.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The phrase "real-time" means something different at every tier of every pricing page, and the two tools in this comparison define it about as differently as two vendors can.&lt;/p&gt;

&lt;p&gt;Fivetran's real-time is a sync frequency: the fastest cadence its managed product publishes is one minute, available on two plans, excluded for its Lite connectors and a long list of advertising sources. Estuary's real-time is a mode: change events flow from a database log to a destination as they happen, and "batch" is a schedule you attach to a destination that does not need them that fast.&lt;/p&gt;

&lt;p&gt;A team comparing the two usually has one question underneath the search query: whether its slowest acceptable latency is minutes or seconds, and whether it wants to pay for the difference by the row or by the gigabyte.&lt;/p&gt;

&lt;p&gt;What Fivetran does better is conceded early, because the catalog argument is not close, and the rest of the words go to the axis the title names. The sibling piece on Airbyte covers the open-core comparison; the decision guide on batch versus real-time explains how to sort your own consumers before you read either.&lt;/p&gt;

&lt;h2&gt;
  
  
  Estuary
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuh1den54gzog8flevfxe.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuh1den54gzog8flevfxe.png" alt="estuary_landing" width="799" height="388"&gt;&lt;/a&gt;&lt;/p&gt;
estuary_landing



&lt;p&gt;&lt;a href="https://estuary.dev/" rel="noopener noreferrer"&gt;Estuary&lt;/a&gt; is a managed data-movement platform that unifies log-based change data capture, streaming, and batch in one system. A capture reads a source and writes documents into a collection, which lives as JSON files in your own S3, GCS, or Azure bucket once you configure a storage mapping. A materialization reads that collection and writes it to a destination at whatever latency you set: as fast as possible, or on a schedule. The pricing model is per gigabyte plus per connector instance, with a free tier of ten gigabytes a month and two connector instances, and a Cloud tier at fifty cents per gigabyte plus one hundred dollars per connector instance per month for the first six and fifty for each after that. The CDC connectors for PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB are log-based and, per the documentation, in-house and purpose-built; MySQL captures are watermarkless by default, so the connector needs no write access to the source.&lt;/p&gt;

&lt;p&gt;Two facts frame the comparison. Estuary's latency claim is sub-100 milliseconds in streaming mode, the vendor's own figure with no published methodology, and the same pipeline delivers on a batch schedule to a destination that prefers it, at no extra charge per the &lt;a href="https://estuary.dev/pricing/" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;. And Estuary is not open source: the runtime is under the Business Source License 1.1 with an Apache 2.0 change date in 2029, while its connectors are Apache 2.0 or MIT. The vendor's own word is open-core.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Honest take&lt;/strong&gt;: The case for Estuary here is narrow and real. When a fraud model, a support tool, or an agent needs a database change within seconds, Fivetran's one-minute floor is a ceiling, and a continuous capture with a per-destination schedule is what you want.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fivetran
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fz37xu5231li0dqhuv5me.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fz37xu5231li0dqhuv5me.png" alt="fivetran_landing" width="799" height="388"&gt;&lt;/a&gt;&lt;/p&gt;
fivetran_landing



&lt;p&gt;Fivetran's managed platform is commercial and proprietary: you operate nothing, and the bill is measured in Monthly Active Rows, the number of distinct rows synced per connection in a calendar month, counted once however often a row changes. A Free plan covers 500,000 MAR; Standard, Enterprise, and Business Critical are priced through an estimator, and every paid-plan connection between one and one million MAR carries a five-dollar base charge, per Fivetran's pricing guide. Fivetran also documents two ways to bring it inside your network: a Hybrid Deployment agent on Enterprise and Business Critical, and HVR 6, which its documentation describes as a self-hosted version of Fivetran.&lt;/p&gt;

&lt;p&gt;The connector count is where Fivetran's site disagrees with itself, with 700-plus on the pricing page and 750-plus on the connectors page, and either number dwarfs the field. Since the merger with dbt Labs closed on 1 June 2026, transformations and the dbt ecosystem sit under the same roof, and activations, the reverse-ETL product, are on the same bill. For databases, Fivetran reads logs: PostgreSQL logical replication, the MySQL binary log, SQL Server CDC, MongoDB change streams, and on-premises HVA agents for Oracle, SQL Server, Db2 for i, and SAP ERP. What the managed product does not offer is streaming delivery. Syncs run on a schedule from one minute to twenty-four hours, and the one-minute option needs an Enterprise or Business Critical plan. The exception is HVR 6, whose documentation describes a capture process that continuously acquires changes at the source; it is licensed software you install and operate, which is a real path to low latency and also the reason it sits outside a comparison of managed services. The managed product is built for the warehouse-first team that measures freshness in minutes and counts its sources in the hundreds.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "real-time" costs on each
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Fivetran&lt;/th&gt;
&lt;th&gt;Estuary&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Fastest delivery&lt;/td&gt;
&lt;td&gt;1-minute scheduled sync, Enterprise and Business Critical only&lt;/td&gt;
&lt;td&gt;Sub-100 ms in streaming mode, per Estuary&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Default database cadence&lt;/td&gt;
&lt;td&gt;Every 15 minutes&lt;/td&gt;
&lt;td&gt;Capture is continuous; warehouse materializations default to a 30-minute sync you can set to zero or any schedule&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pricing unit&lt;/td&gt;
&lt;td&gt;Monthly Active Rows per connection, plus a $5 base per paid-plan connection under 1M MAR&lt;/td&gt;
&lt;td&gt;Gigabytes sourced, transformed, and delivered, plus $100 per connector instance&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Free tier&lt;/td&gt;
&lt;td&gt;500,000 MAR&lt;/td&gt;
&lt;td&gt;10 GB per month, 2 connector instances&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Durable change log&lt;/td&gt;
&lt;td&gt;None; changes are processed in transit and land in your destination&lt;/td&gt;
&lt;td&gt;Your own cloud bucket, once a storage mapping is configured&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deployment inside your network&lt;/td&gt;
&lt;td&gt;Hybrid agent (Enterprise+), HVR 6 self-hosted&lt;/td&gt;
&lt;td&gt;Private or BYOC data plane (Enterprise, annual contract)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The table hides a subtlety about speed on both sides. Fivetran's own documentation for its Oracle agent says that choosing a one-minute sync frequency does not guarantee that the sync completes within one minute; a one-minute schedule is an interval between starts, and a large table or a slow API can stretch the gap. Estuary's streaming mode has no interval: the connector tails the log continuously, and a materialization set to sync as fast as possible commits transactions as they arrive. But its warehouse materializations default to a 30-minute sync schedule, per the documentation, so a team that never changes that default has bought a slower warehouse than Fivetran's fifteen minutes. The difference between the two, for a consumer that needs seconds, is that one can be set to zero and the other cannot.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the bill diverges
&lt;/h2&gt;

&lt;p&gt;Fivetran counts a row once per month no matter how many times it changes. Estuary meters the bytes that move. Those two rules point in opposite directions depending on the shape of your data. A table of a million customer records, each updated dozens of times a day, is a million MAR on Fivetran and many gigabytes of change events on Estuary; here the per-row model favours Fivetran. A wide event table with hundreds of millions of new rows a month is hundreds of millions of MAR on Fivetran and, at fifty cents a gigabyte, a bill you can compute from the row size on Estuary; here the per-gigabyte model favours Estuary. Estuary's compare pages describe its cost as two to five times lower than the alternatives, and that figure is the vendor's own, with no methodology published, so treat it as a claim to check against your own tables rather than a fact.&lt;/p&gt;

&lt;p&gt;The per-connector-instance fee cuts the other way. Twenty small SaaS sources on Estuary cost twenty instances a month before a byte moves, at one hundred dollars each for the first six and fifty thereafter. Twenty small SaaS sources on Fivetran are twenty five-dollar base charges plus their MAR. For a long tail of low-volume connectors, Fivetran is cheaper, and the honest recommendation is to run those there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which tool fits which consumer
&lt;/h2&gt;

&lt;p&gt;Sort the things that read your data by how long they can wait. Nightly reports, the finance close, and model training sets tolerate hours; a scheduled sync serves them well on either tool, and Fivetran's catalog breadth and dbt integration make it the default for a warehouse-first team. A support console that shows an order the moment it is placed, a fraud check, a search index, or an agent that acts on a customer record cannot wait for the next sync, and those consumers are the reason to look at Estuary at all. Teams with both kinds of consumer tend to want one pipeline, capturing each change once into their own bucket and delivering it fast to the consumers that need speed and on a schedule to the ones that do not. Estuary's &lt;a href="https://estuary.dev/deployment-options/" rel="noopener noreferrer"&gt;deployment options&lt;/a&gt; matter here too: a Private or BYOC data plane keeps that bucket and the processing inside your cloud, though both are Enterprise, annual-contract features.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;As a head of data on Fivetran Standard, what does moving to Estuary actually change?&lt;/strong&gt;&lt;br&gt;
Standard syncs every fifteen minutes. Moving buys you continuous capture from your databases, a schedule you can set per destination rather than per plan, and a change log that lives in your own bucket so a new destination backfills from it without re-reading the source. It costs you Fivetran's long-tail catalog, its dbt-native transformations, and the once-per-month row counting that makes high-churn tables cheap, plus a migration: a fresh snapshot of each moved table, a second schema in the warehouse while both run, and dbt sources repointed. Estuary's catalog covers the mainstream SaaS sources, Salesforce, HubSpot, and NetSuite among them; the gap is the long tail, and the practical path many teams take is to move the database sources that feed operational consumers and leave the rest where they are.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;As the analyst who owns the data bill, is MAR or per-gigabyte cheaper for us?&lt;/strong&gt;&lt;br&gt;
It depends on the shape of your largest tables, not on the vendors. Count the distinct rows that change per month and multiply by the bytes each change carries. Tables with many updates to few rows favour Fivetran's model; tables with many new rows favour Estuary's. Add Estuary's per-instance fee for every connector you would run and Fivetran's five-dollar base charge per paid-plan connection. Fivetran publishes a pricing estimator and worked list-price examples rather than a per-MAR rate; Estuary publishes its per-gigabyte rate and a calculator on its &lt;a href="https://estuary.dev/pricing/" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; page. Volume discounts on either side are a sales conversation, so run the arithmetic on your own numbers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;As a data engineer, can we keep Fivetran for SaaS sources and add Estuary for CDC?&lt;/strong&gt;&lt;br&gt;
Yes, and it is a common arrangement. Fivetran keeps the connectors Estuary does not have and the transformation layer your analysts already use. Estuary takes the databases whose changes have operational consumers, delivers them in streaming mode where needed, and materializes to the same warehouse on a schedule for analytics. The two tools do not conflict at the destination; they land in different schemas. What you should avoid is capturing the same database twice, once per tool, because that means two replication slots, twice the decoding load on the primary, and a bill on both sides.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which one should you pick
&lt;/h2&gt;

&lt;p&gt;Pick Estuary when at least one consumer needs a database change in seconds, when you want the change log in your own bucket, or when the same capture must feed a fast consumer and a scheduled one without two pipelines; its &lt;a href="https://estuary.dev/product/" rel="noopener noreferrer"&gt;product overview&lt;/a&gt; is the place to start. If you have both kinds of consumer, that last case is yours, and it is the one in which Estuary is the better tool.&lt;/p&gt;

</description>
      <category>dataengineering</category>
      <category>softwaredevelopment</category>
      <category>etl</category>
      <category>estuary</category>
    </item>
  </channel>
</rss>
