Spectersync Local FAQ — desktop app and open-source edition, answered plainly

Prefer not to install anything? The hosted webapp runs the same engine in your browser — subscribe now for 500 free credits when your workspace opens. This page is about the desktop and open-source editions that run on your own Mac.

Plain answers about Spectersync Local. If a question you have isn’t here, email me and I’ll answer it — and probably add it to the page.

The local app

What does the local app actually do?

It runs the Spectersync engine entirely on your own Mac. It pulls your Shopify, WordPress, Ghost, or Webflow content into a folder of plain .md files on disk, watches that folder for changes, and pushes your edits back — with a dry-run preview and conflict detection before anything ships. Once the folder is populated you point any tool at it: a markdown editor like Obsidian or VS Code, an AI agent like Claude Code or Cursor, or a one-off script. Spectersync handles the round-trip. For the full mechanics — file watching, sync queues, conflict handling — see how the local app works.

How is this different from the hosted webapp?

Same engine, different place to run it. The webapp runs in your browser, opens your content as clean content you review and publish from there, and runs AI as recipes that spend credits. The local editions run on your Mac, keep your content as files on your own disk, and let you bring whatever editor, AI tool, or script you already use — there are no credits, because the AI is whatever you point at the folder. Most people should start with the webapp; the local editions are for those who specifically want the engine on their own hardware.

What are the system requirements?

The desktop app runs on macOS 13 (Ventura) or later, on both Intel and Apple Silicon Macs. Windows and Linux aren’t supported by the desktop app today. The full per-platform pull/push surface lives on the Capabilities matrix, and the deep desktop mechanics are in how the local app works.

Core vs DIY

What’s the difference between Spectersync Core and DIY?

Same engine — the difference is everything around it:

Core is the signed, notarized macOS app: it launches cleanly with no Gatekeeper warnings, updates itself in place, and comes with priority email support straight to the builder. $99/year.
DIY is the AGPLv3 open-source project: source you build and run yourself, free forever. No signed installer, no in-app updates, no priority support — exactly what Core buys.

See Spectersync Core and Spectersync DIY for the full breakdown, or the local pricing page to compare them side by side.

Is DIY really free?

Yes — free forever. Inspect it, fork it, build it yourself, and run your own local sync on as many machines as you like. It’s the same engine under the Core app; Core just packages, signs, updates, and supports it. The open-source project is on GitHub.

Licensing and activation

How does activation work?

When you buy Core you get a license key. The app checks it with the store once on first activation, and occasionally afterward to confirm the license is still valid. That exchange sends your license key and a hashed machine identifier — never your content, your site URLs, or any telemetry on what you’re syncing.

How many Macs can one license run on?

Two — for example a desktop and a laptop. If you replace a machine, deactivate the old one and activate the new one; no separate purchase. For more than two machines, email me and we’ll work it out.

Can I try it before I buy Core?

Yes — run the free DIY edition first. It’s the same pull/edit/push engine, so you can prove out the full workflow on your own sites before deciding whether you want it signed, auto-updating, and supported. Note that Spectersync Core is non-refundable, so trying the free engine first is the right move.

Privacy

What leaves my Mac?

Two things, and that’s it:

CMS traffic — direct HTTPS calls from your Mac to your CMS’s admin endpoint (Shopify Admin API, WordPress REST API, Ghost Admin API, Webflow API). Nothing is proxied through our servers.
License check — once on first activation and occasionally after, sending a license key and a hashed machine ID. No content, no site URLs, no usage telemetry.

Your post bodies, drafts, frontmatter, and folder structure never touch our servers. Credentials live in the macOS Keychain, encrypted by the OS. For the per-platform detail, see is my Ghost content private.

Still deciding?

If you don’t specifically need the engine on your own hardware, the hosted webapp is the fastest way in — nothing to install, and 500 free credits when your workspace opens. Subscribe now →