One pipeline, every tier of your stack
Sarcio's economics are simple: the verification engine is written once, and each runtime costs only a thin adapter. That's how one approved patch fixes a Node API, a Laravel app, a Spring Boot service, and a WordPress site at the same time.
Browser tier
The widget and the frameworks it understands.
Reporter + DOM patching
A single ~6KB script tag adds in-page bug reporting (console, network, and screenshot context) and the DOM patch applier. Framework-agnostic — if it renders HTML, it works.
React
Module patches swap components live with state preserved via real React Fast Refresh — a form mid-completion stays mid-completion while the buggy logic underneath it is replaced.
Angular
A dedicated builder plugin covers both JIT and AOT production builds; patched components are re-created live with their state carried over automatically.
Vanilla JS & Web Workers
No framework required: the vanilla runtime re-runs transitive dependents after a swap, and web workers apply patches forwarded over a verified bridge from the main thread.
Vite
A build plugin emits the module registry your app needs for live swaps — one line in your Vite config.
webpack
The webpack plugin produces byte-identical output to the Vite one, so mixed-tooling teams get identical behavior.
Server tier
Four runtimes, one self-hosted sidecar.
Server patches are enforced by a single static Go binary you run next to your app — Kubernetes sidecar, Docker Compose service, deb/rpm with a hardened systemd unit, or a bare binary. Your app gets a thin shim that consults it and fails closed.
Run the sidecar as
Kubernetes sidecar
Docker Compose
deb / rpm + systemd
Bare binary
Node.js
One npm middleware with adapters for Express, Fastify, Koa, Hono, and raw node:http. Server-side module patches roll out across clusters behind a sticky canary router.
PHP
A Composer package with Laravel middleware and a Symfony listener over one shared core, built for PHP-FPM's process model — plus an opcache-aware fast path for whole-file fixes.
Java
A servlet Filter and a Spring Boot starter on a pure-JDK core — no agents, no bytecode manipulation, nothing exotic to clear with your platform team.
WordPress
One plugin covers both tiers: the reporter widget on the page and server-side patching of REST, admin-ajax, and page loads. Installs as a zip — no Composer required on the host.
Deploy anywhere
The sidecar ships as multi-arch containers, deb/rpm packages, and signed static binaries, with an N/N-1 protocol version policy so upgrades never require a lockstep migration.
Outbound-only
The sidecar pulls signed patches from the control plane — nothing connects into your network, and no credentials sit on the app socket.
Workflow
Your forge, your tracker, your CI.
GitHub · GitLab · Bitbucket
The permanent-fix PR/MR opens on whichever forge hosts the repo, using your workspace's own credential — validated by API preflight before any clone.
Jira
The patch lifecycle mirrors into your tracker: a fix ticket on draft, comments at each milestone, commit messages following your convention so links resolve, and a transition when the fix merges.
Your own CI/CD
Opt a site into remote builds and module patches build inside your pipeline instead of Sarcio's — only the validated, checksummed artifact comes back, authenticated by a narrowly-scoped API token. GitHub Actions, GitLab CI, and Bitbucket Pipelines out of the box.
If it's in your stack, it's probably covered.
Start with the widget on one site — add tiers as you need them.
Create a workspace