Replace, don't add.
Every module exists because a separate plugin would have done the same job, worse. One install, one settings tree, one update cycle. We measure success by how many plugins you can delete after switching.
About
TruePlugins builds tools that replace plugins. Not add to them.
We make WordPress admin tools that consolidate, never sprawl. One install, many admin jobs, with site effects documented per command.
WordPress admin became a labyrinth.
To enable Google Analytics, you install a plugin. To compress images, another. To back up the database, another. To run something on a schedule, another. Each one bolts onto the same admin screen, ships unused JavaScript to the front end, and stays even after you've stopped using it.
The individual plugins solve real problems. The sum of them creates new ones: slower admin, slower visitors, more vendor lock-in, more orphaned database tables when you walk away.
We started TruePlugins because that pattern stopped scaling. Our answer is the opposite shape. One plugin where every job is a command, frontend behavior follows the features you enable, and uninstalling actually uninstalls.
Two developers behind TruePlugins.
We are an independent two-person team building WordPress plugins from Lithuania. The same people who write the code answer your support tickets.
What we build for. And against.
Stop clicking. Start commanding.
Keyboard-first by default. Type what you want, press Enter. The mouse should be optional, not required. Every workflow earns its place by how few keystrokes it costs.
Your data stays on your server.
Core administration runs inside WordPress. Licensing, signed updates, and AI use TruePlugins services; optional integrations contact the endpoints you configure.
Walk away clean.
Uninstalling removes its declared owned data while preserving shared or separately owned resources. Review integrations and test after changing themes or hosts. Exportable configuration and declared cleanup boundaries in wp_options.
What TrueCommander isn't.
Defining a tool by what it refuses to be is sometimes the clearest way to explain it.
- The core workspace runs on your WordPress server. Licensing, signed updates, and AI use TruePlugins services; configured integrations can require provider accounts and credentials.
Not a page builder.
The workspace is in wp-admin. Visitor tracking and enabled site-facing commands use frontend hooks, so performance and public output depend on the configuration.
Not a marketplace.
One plugin, ten modules, every command included. No add-on store, no premium tiers gated behind the same install. What you buy is what you get.
Not a wrapper.
Commands use WordPress APIs and bundled libraries. The built-in catalogue covers supported operations; integrations and Custom Commands have their own prerequisites.
One plugin. Ten modules. 100 command variants.
TrueCommander is the first plugin in the catalogue and the focus of every working day. More plugins are planned but unannounced. We'd rather under-promise than ship a half-finished second product.
Every future release follows the same shape: replace a category of plugins, frontend effects documented per command, clean uninstall. If a planned module starts to feel like it belongs in a separate plugin, we split it; if a separate plugin starts to feel like another module, we fold it in.
Try it
Take command in minutes. Decide in 14 days.
Every license includes a 14-day money-back guarantee. Install on a real site, see whether it fits your workflow, refund if it doesn't.