Every client site, one way of working.
Keep your snippets in Git, push them to your clients' sites from your own, give designers and clients exactly the access they need, and see who changed what. Unlimited sites on every Agency and Pro unlimited plan.
The trial is the Agency plan with everything in it. No card needed.
Your snippet library, in GitHub or GitLab. Agency plan
Two-way sync: edit on the site or in Git, then sync. Keep a "Shared" folder in one repository and every client site picks it up.
- Readable files: each snippet is a real code file plus a small settings file. Folders become folders.
- Nothing is overwritten silently. A snippet changed on both sides waits for you to pick "Keep this site's" or "Take Git's".
- Code arriving from Git is checked and test-loaded. One that would break a site stays off there.
- One commit per sync, automatic syncs on a schedule, and a webhook so a push reaches the site in seconds.
- GitHub, GitHub Enterprise Server, GitLab.com and self-managed GitLab. The token is stored encrypted and never shown in the browser.
Every client site, from your own. Agency plan
The agency hub connects your clients' sites to yours. Push a snippet to the sites you choose, see which version runs where, and roll back when you need to.
There's no cloud service in between: your site talks to each client's Snipfire over the WordPress REST API. Client sites need Snipfire 0.17 or later, free or Pro, and an administrator's application password.
- Connect a site in a minute Log in to the client site and approve the connection with WordPress's own "Connect with WordPress" screen, or type an application password. It's stored encrypted and never shown or logged.
- Push snippets, checked on arrival Push ticked snippets, a folder or one snippet, and switch them on if you like. Each site checks and test-loads them as it does its own saves.
- Nothing overwritten behind anyone's back If someone changed a copy on a client site since you last pushed it, the hub asks: keep the site's version or overwrite it.
- Where is it running? For each snippet, every site: the same version, an older one or a changed one, and whether it's on, off or has an error. Roll back to an earlier version, switch it off or remove it on one site.
- Health at a glance Versions, snippet counts, errors and safe mode for every site, checked twice a day in the background. Every push is in the activity log of your site and the client's.
$ wp snipfire hub add https://client.example --username=admin
$ wp snipfire hub push 12,14 --sites=all --on
$ wp snipfire hub where 12
$ wp snipfire hub rollback 12 --site=3The right access for each person. Pro
Choose a level for each WordPress role. The server checks every change, so a designer can't paste PHP into an HTML snippet or restore an old PHP version. Administrators (super admins on multisite) always keep full access.
| Level | What they can do | Good for |
|---|---|---|
| No access | Doesn't see snippets at all. | Most roles |
| View only | Sees what's running and the history, changes nothing. | Clients |
| CSS, JS and HTML | Edits styles, scripts and markup on the public site. Never PHP. | Designers, marketers |
| Full | Everything, including PHP, imports and settings. | Developers |
The editor adapts too: read-only snippets say why, PHP is hidden from designers, and only public-site locations are offered.
Who changed what, and when. Pro
Every create, edit, switch, delete and restore, which snippets were switched off after an error, and who changed settings or access. With where each change came from: the editor, the REST API, WP-CLI or automatic.
Search and filter it, open it for one snippet, or read it with WP-CLI. Kept for 12 months.
One snippet for a whole network. Agency plan
On WordPress multisite, super admins write network snippets once in Network Admin, in the same editor, and they run on every site of the network before each site's own snippets.
- The same safety net: syntax checks, a test load of the main site and other sites when you switch one on, and automatic switch-off on every site if it crashes anywhere.
- A "Site of the network" rule runs a snippet only on some sites, or on every site but some.
- Sites see network snippets read-only. Mark one as required, or let people with full Snipfire access on a site switch it off there; the network screen shows which sites did.
- Network safe mode stops every network snippet on every site: a switch on the network screen, WP-CLI, or
SNIPFIRE_NETWORK_SAFE_MODEin wp-config.php. - History and a network activity log, like a site's own snippets.
Working with clients.
The small things that make a client site easier to hand over and look after.
- Show changes before they go live Pro Put a snippet in testing mode and send your client the preview link. Visitors see nothing until you click Go live.
- Each person in their own language The plugin follows each user's profile language, so a Greek client and an English-speaking developer share one site.
-
Move client sites over in bulk
Import and switch over from WPCode, Code Snippets and others with
wp snipfire import-from wpcode --switchin your deploy script. - Unlimited sites, one licence Pro unlimited and Agency cover every client site. Local development sites never count.
- Hand over without lock-in Leaving a client site? Export its snippets as a normal WordPress plugin that runs them without Snipfire.
- Keys out of your code Pro Keep each client's API keys in the encrypted secrets vault instead of in snippets, so they never end up in an export, a Git repository or a screenshot.
- Cloud library Coming soon Save snippets to your own library and pull them onto any site. Until then, Git sync and the agency hub do the job.
Move your snippets over this afternoon.
Importing changes nothing until you switch over, and your old shortcodes keep working.