Linchpin for WordPress

Your plugins are fighting. Find out where.

Linchpin reads every plugin on your site, shows you exactly where they collide, duplicate each other and slow it down — then writes the fix as a separate file that survives the next update.

No account, no card, no email. The scan is free forever.

24 plugins.

16 fixable conflicts.

That was one ordinary site, and its owner had no idea. Yours is probably not cleaner.

Plugin conflicts do not announce themselves. They show up as a checkout that fails for one customer, a page builder that stops saving, a site that got slower and nobody knows when. The cause is two plugins declaring the same thing, and nothing in WordPress tells you.

How it works

Three steps, and the order matters.

You see your own site’s findings before anything asks you for a licence. That is deliberate: paying for a diagnosis you have not read is not a decision anyone should be asked to make.

Scan

Every plugin, every symbol, every collision, every duplicated library — with severity, and with the manual remedy written out in full. Free forever, and nothing is redacted to make you upgrade.

Update first

Most findings are already fixed upstream. Linchpin checks what an update would change, assesses the risk plugin by plugin, applies it, and re-scans — so you are never paying to fix something the author already did.

Then fix what is left

One button, one file, next to the specific problem it solves. This is the first place a licence is mentioned, and by then you have read exactly what it would buy.

What you get

The fix is a file you own.

Not a setting inside our plugin, and not an edit to somebody else’s code. A file, on your server, in a folder you can open.

Beside the plugin, never inside it

Fixes live in their own folder, as “plugin children”. Your plugins’ files are never edited — which is why the fix survives the plugin’s next update, and why removing it leaves nothing behind.

wp-content/linchpin-children/
  woocommerce-stripe/
    overlay.php

Checked before it is switched on

Every generated file has to clear the same gates before it is ever enabled:

  • It parses
  • Nothing is declared dynamically
  • Every declaration is guarded
  • It targets the right plugin
  • It stays under 220 lines
  • It survives a sandbox trial

A file that fails any gate is never enabled — and never counted against your quota. We absorb the cost of our own bad output. Charging you for our retry would be the wrong incentive on both sides.

Placeholder — replace with a screenshot of a generated overlay file

Replace with a screenshot of a generated overlay, or a short clip of the fix being written.

And you can always put it back

Everything Linchpin writes goes into a vault with a one-click revert, recorded in a journal on your own disk. Undo works with our servers unreachable — because the changes most worth undoing are the ones that might have broken something.

Trim

You installed ten features. You use one.

The other nine still load on every request — their scripts, their queries, their admin pages. Trim switches off the parts of a plugin you do not use, one feature at a time.

What it deliberately does not do is replace the plugin with a smaller one. That plugin owns your content — its post types, its meta, sometimes its own tables — and a rewrite that has to reimplement a schema exactly is a data-loss bug waiting for its first customer. Trim leaves the plugin, and its data, exactly where they are.

Every switch is reversible, and the feature breakdown itself is free to read on any plan.

Placeholder — replace with a video of Trim switching a plugin feature off

Replace with a short clip of Trim in action.

The diagnosis is free. You pay to have it handled.

Free

The whole diagnosis, permanently.

$0

free forever

  • 1 site
  • Every conflict, duplicate and undeclared dependency
  • Speed cost measured per plugin
  • Every fix written out in plain language
  • 2 plain-English reports a month
Get the free plugin

Enterprise

A portfolio of sites.

$990 per year

  • 25 sites
  • 250 generated fixes a month
  • 50 plain-English reports a month
  • Every site in one view
  • Named support

Agency

More sites than a plan covers.

Tailored

to the number of sites you run

  • 50 sites and up
  • Generated fixes to match how you work
  • Several people on one account
  • Billed to fit, not rounded up to the next tier
  • Priced after a short conversation
Tell us what you run

Payment is handled by Stripe. Your card details never touch this site. Cancel any time from your dashboard.

Boundaries

What Linchpin will never do.

Edit your plugins’ files

Not once, and not as a fallback when something else fails.

Call your site

Your site asks us; we never reach in. Nothing has to expose an endpoint to us — an endpoint we could call is an endpoint someone else could find.

Expire into a broken state

Cancel and the files Linchpin already wrote stay on disk and stay active. Your site has been running with them for months; switching them off because a card expired would break it.

Report silence as health

A check that could not run says so. A scanner that sees nothing and reports nothing is worse than one that fails loudly, because you read reassurance into it.

Questions

The things people ask before buying.

Does it change my plugins?

No. Your plugins’ files are never edited. A fix is written as a separate file in wp-content/linchpin-children/, which is why it keeps working after the plugin updates, and why deleting it leaves the plugin exactly as it was.

What happens if a fix breaks something?

A fix has to pass every gate and survive a sandbox trial before it is enabled at all, so most bad output never reaches your site. If one still causes trouble, one click reverts it — from a journal on your own disk, which works even if our servers are unreachable.

What happens if I cancel?

Every file already written stays on disk and stays active. Only the writing of new ones stops. The full scan, every finding, every manual remedy and the update workflow all remain free, exactly as they are today.

Do you need access to my server?

No. There is no login for us, no SSH key, and no endpoint on your site that we can call. Your site asks us; we never reach in. That is a deliberate design decision, not a limitation we plan to remove.

Does the free scan expire?

No. It is not a trial and nothing degrades after a fortnight. You get the entire diagnosis permanently, including how to fix each finding by hand. What a plan buys is having it written for you.

Will it work on my host?

Linchpin is an ordinary WordPress plugin and needs no special server access, so it runs on shared hosting as readily as on a dedicated box. If a particular check cannot run in your environment, it says so rather than quietly passing.

Start with your own site.

Install it, run the scan, and read what comes back. If nothing on the list matters to you, you have lost ten minutes and paid nothing.

Already have a key? Paste it into the plugin’s Licence tab — that is the only place a key is ever entered.