Pricing & connected service

The commercial boundary is where the work runs:

The complete local workbench is free. There is no local feature gate, site cap, scan cap, history cap, or information-depth gate.
The connected service is the commercial product. It operates SiteCMD on hosted infrastructure after deploys and between local sessions.

Connected-service access is comped during the founder beta. Public prices and included quantities are intentionally unset until observed usage supports the pricing pass.

The complete free local workbench

Every local product capability is included:

The desktop app, dashboard, Issues workflow, projects, environments, and integrations
Every Web Scan and Code Scan check, including the deep axe-core browser pass
Unlimited local sites, scans, and retained history
Full issue detail, captured evidence, confidence, source excerpts, and complete fix guidance
Cross-source correlation and the single SiteCMD Score
AI fix prompts, local verification, regression tracking, and issue lifecycle controls
The complete local MCP server for supported AI coding tools
The standalone CLI for local automation and CI pipelines
Reports, exports, schedules, desktop notifications, and the audit log

Free is not a trial or a restricted preview. It is the full local product and it does not expire.

What the connected service adds

The connected service handles jobs that must continue while your laptop is closed or that need a shared hosted baseline:

Watch production deploys and scan the deployed site afterward
Run scheduled hosted scans between deploys
Compare results against the hosted baseline and track verified fixes
Alert on new findings and regressions by email or webhook
Return CI gate verdicts based on new findings rather than inherited debt
Deliver hosted reports
Deliver maintained check and advisory intelligence

It does not turn local information on. The same finding contract, evidence, and fix context already exist in the free local workbench. You are paying for continuous hosted operation and delivery.

Founder-beta access

Founder-beta access is comped and intentionally hands-on. Use the contact form to request access. The beta is where SiteCMD measures reliability, per-site operating cost, scan behavior, and which connected workflows create enough value to support a durable offer.

No public dollar price or site allowance is published during this measurement window. Those numbers would be guesses rather than product truth.

How paid plans are intended to work

After the pricing pass:

The billable unit will be a connected production site.
Plans are intended to be flat bundles, not usage-metered billing.
There will be no metered overages.
Prices and included quantities will be published before anyone is asked to buy.

Local projects are not billable units. A staging environment, source folder, scan, issue, MCP request, or report does not become a meter.

Existing licenses

If you already hold a SiteCMD license, the Account screen continues to activate, refresh, deactivate, and link to billing self-service for that license. Existing purchases keep the commercial terms shown at purchase.

License state may still appear in the desktop app because it identifies an existing subscription and authorizes connected-service or maintained-catalog credentials. It does not redact or disable local product capabilities.

See License & billing for existing-license recovery and management.

Data boundary

The local workbench stores project data, scan history, issue state, and findings on your machine. The connected service remains off until you explicitly connect a site.

For a connected site, SiteCMD sends the production URL, selected route scope, release identifiers, scan findings, and the delivery information required for the hosted workflow. It does not upload your source repository. Private source analysis runs locally or inside your own CI environment.

See Privacy & data for the field-level breakdown.