Skip to content

Client sites that survive update day.

strackt keeps your WordPress fleet inventoried, patched against known vulnerabilities, and one click from restore — on servers you own, in the country you chose, with your clients' data staying there.

Get notified when signup opens
We'll email you on September 9.
See pricing

The update loop

Every update is a protected update.

The add-on tools that promise a safe update loop back the site up from inside PHP. strackt checkpoints files and database together, at the filesystem, before anything changes.

1

Inventory, continuously

Without logging into a single wp-admin

Every plugin, theme, and core version on every site, kept current in the background — so the question "what is actually running on that client site?" has an answer before you need it.

2

Matched against real vulnerabilities

You see which update fixes what

Updates are classified against a live vulnerability feed. You can see which update closes a known vulnerability and which one is safe to hold until you have time to look at it.

3

Checkpoint, then update

Files and database, atomically

A checkpoint is taken before anything changes. The update runs, and the site is health-checked afterwards — so a bad release is caught by us rather than by your client.

4

Restore in one click

Seconds, not an evening

A broken update is a one-click restore back to the checkpoint, not an evening of FTP archaeology with a client on the phone.

Getting sites in

Bring sites, not exports of exports. Three ways in, and none of them ask you to rebuild the site by hand at the other end.

  • An archive. A .wpress file, a Duplicator package, or a plain zip plus SQL dump — whatever the previous host gave you.

  • A live pull. Point strackt at the running site and it migrates over a signed channel, with nothing to install on the source host, while the site stays up. (Live pull is in alpha today.)

  • Fresh. A clean WordPress install, managed from day one.

For the whole fleet

Twenty sites is one workflow, not twenty tabs. A twenty-site fleet, all in: around €117.50 a month.

  • Run an update round across the fleet and watch it go site by site — checkpoint, update, verify — instead of opening twenty dashboards on a Friday afternoon.

  • Script anything the interface does not cover with the CLI: strackt wp plugin list --update=available runs against the site you name, checkpointed the same way.

  • Every site keeps its own environment, its own database, and its own restore history. A bad update on one client site is one client site.

twenty sites, all in per month
19 sites billed
€95.00
5 servers, yours
~€22.50
strackt, all in
€117.50
Managed WP hosts
$500–600

The first application is free, so nineteen of the twenty are billed. Managed WordPress hosts charge $25–30 per site. Their update add-ons are cheaper per site, back the sites up from inside PHP, and leave your hosting bill exactly where it was.

The honest boundary. WordPress is the one codebase strackt manages without a Git repository — an operated site, where your themes, plugins, and content are the asset. It is a deliberate exception, not the start of a catalogue of packaged apps: if what you want is to install software other people wrote, Coolify will serve you better.

Bring your first site — it's free.

Import an archive or pull a live site. Your server, your data, our problem.

Get notified when signup opens
We'll email you on September 9.
See pricing

First application free, then €5 per site per month, plus the VPS you own.