Straight answers before you start.

Keep delivery detail in Jira. PMCW gives one PM a separate place for selected commitments, meeting decisions, risks, review readiness, and follow-up context across the project. Your team can keep using its existing tools.

No Jira connector or automatic synchronisation is provided in the current public product. Coexistence means you select and maintain the management context you need; it does not mean connected accounts or two-way updates.

No. Keep operational detail, schedules, documents, and authoritative records in the appropriate company system. PMCW is a separate project-control workspace alongside them.

Keep only the control context that helps you make a decision or follow up. Record selected actions, owners, dates, decisions, and evidence gaps. Use document references or explicit exports where supported rather than copying every source record. Changes in another system do not update PMCW automatically.

No. PMCW is useful to one PM without organisation-wide adoption. You can share explicit reports and exports; there is no collaborative editing of the active workspace.

PMCW holds your selected project-control picture: commitments, meetings, risks, milestones, and review context. Detailed delivery records, enterprise schedules, and official documents remain authoritative in their existing systems.

The Windows pilot package uses %LOCALAPPDATA%\PM Control Workbench\user_db\live\workspace-authoritative.sqlite. A supplied universal package uses user_db inside its extracted folder. Follow the instructions for your exact package. Keep active storage on a fixed local drive outside synchronised, network, removable, or linked locations.

No. PMCW does not host your project workspace and does not require an additional vendor-hosted project-data workspace. Online identity and licensing are separate services. You or your organisation may deliberately share exports or store backup copies elsewhere.

Sign-in uses identity and session information. Activation sends device name, platform, device public key and hash, pseudonymous OS/hardware/user-scope fingerprints, release identity, and request identifiers, timestamps and proof. New permanent licences need no recurring refresh. Legacy time-limited refresh sends device/release identifiers and cryptographic proof. These requests contain no project records or attachments. The privacy notice explains website logs and account records.

The account and licensing services do not receive the workspace. Support has no automatic workspace-access or support-bundle upload feature. Prefer reviewed diagnostics or a synthetic example; share project material only through an explicitly approved support process and with the required organisational permission.

The supported pilot runtime has no supported telemetry or automatic crash-report upload. Local diagnostics and account/licensing service events are separate. Browser, operating-system, endpoint-security, and backup-provider activity remain outside the application boundary.

Use verified local snapshots and Backup Explorer restore. The optional backup mirror copies snapshots to an approved protected folder; it never becomes the active database. Backups, attachments, and exports may contain sensitive project information and need your organisation’s access and retention controls.

Only as an organisation-approved recovery-copy destination, separate from active storage. The backup mirror supports a chosen writable folder, but PMCW does not certify a particular OneDrive tenant, network share, or sync policy. Have IT and pilot support validate the destination and recovery procedure. Never synchronise the live database.

This site claims no SOC 2, ISO 27001, sector-specific compliance, or independent security certification. Local storage does not establish compliance. PMCW does not claim application-level encryption at rest; account permissions, disk encryption, endpoint policy, and protection of shared files remain organisational responsibilities.

No PMCW project server or collaborative backend needs to be deployed. The package runs a local browser interface through a loopback service on your computer. Identity and licensing use separate online services.

The current public line is 0.9.9 for Windows. Mac and Linux instructions apply only to a supplied universal package containing those runtimes. Use the release-specific compatibility instructions; the website does not promise support for every OS version or company policy.

The standard supplied entry needs no administrator launch. Use a writable fixed local folder and the bundled runtime. Your organisation still needs to approve execution, storage, and dependencies. Stop and contact IT or pilot support if application controls block the package.

The workspace interface uses the local loopback address. Initial activation and replacement-device issuance use HTTPS at pmcontrolworkbench.com and its configured sign-in provider. IT must approve the necessary network access; the installation guide describes the boundary. Fresh activation needs a connected computer.

Yes. Create a request on the work computer, obtain a signed .lic response on a permitted connected computer, then import it on the original device. Offline use follows the issued licence rules. File exchange cannot issue a new licence during a service-wide outage.

Use the complete approved package and follow the update guide. Back up and stop the runtime before switching versions. Pilot upgrades are supervised and side by side; no public automatic updater is claimed. Eligible account downloads follow your licence’s update rights.

Installation & activation describes the explicitly selected, IT-approved Python entry for supported packages, interpreter compatibility, licence-verification dependency, and launch commands. Python being installed alone is not sufficient. This path does not override organisational application controls.

€149 once, excluding applicable tax, for the full released product assigned to one named professional. No subscription, renewal or maintenance fee. Professional and commercial use is permitted.

Contact us with organisation procurement and deployment requirements. No public organisation price matrix or self-service company offer is published. Purchasing is not currently open.

Yes. The Individual licence permits professional and commercial project-management use under their licence terms. Your employer’s procurement, IT, confidentiality, and data-handling rules still apply. Single-PM adoption does not require personal payment.

An Individual licence remains assigned to its named professional under its terms and device rules. Your employer’s procurement rules still apply. The licence does not grant rights over employer or client information.

No. Employer and client project information remains governed by the organisation that owns or controls it. Any retention, export, handoff, or transfer needs the appropriate authority; owning a software licence supplies none of that authority.

The full trial lasts 30 days, needs no card and never converts automatically. After its signed expiry, normal editing pauses. Existing work remains readable, searchable, exportable, backed up and recoverable.

Save a verified snapshot, inspect it in Backup Explorer, and use Restore selected backup. The runtime creates a verified safety backup and checks the selected snapshot and restore. Rolling retention is bounded. A live SQLite file copy is not the supported restore method.

Permanent use of the eligible major release line, including maintenance releases in that line. Launch family 1 includes pre-1.0 and 1.x. Future major upgrades are separate purchases. Future releases and features are not promised.

A valid installed one-time licence is verified locally and remains valid during service outages or retirement, without recurring online checks. Initial and replacement-device issuance require the service. Keep your licence backup, protected device identity, project backups and approved package.

Documentation, structured bug reporting, and best-effort written installation/licensing troubleshooting. No SLA, calls, consulting, training, custom development, feature delivery or status-reporting entitlement. Suggestions create no obligation to implement or schedule them.

No voluntary money-back guarantee is offered. Use the full 30-day trial to evaluate the product. Statutory consumer rights remain unaffected; see Withdrawal and consumer rights.