What is this machine’s configuration right now?
There is no single place to look.
PINMAN 2 · BUSINESS & IT
A versioned memory for the Windows machine that matters.
Track selected configuration across files, the Windows Registry, Windows settings, and device settings. See what changed, recover a specific setting, or apply a defined configuration across applications—on one Windows PC, standalone or beside the fleet tools you already run.
The evaluation begins with a time-limited Pro trial, a sandbox project that doubles as a tutorial and demo, and a focused Getting Started guide. Pinman is a platform: downloadable kits carry the domain knowledge, so it is not limited to any one kind of machine.
THE CONFIGURATION PROBLEM
Four ordinary questions that are strangely hard to answer.
On a real working machine, configuration is scattered across application files, databases, the Windows Registry, and settings exposed only through Windows or device APIs.
What changed since it was working?
An application rewrote its configuration, an update changed a value, or someone made a one-off adjustment—and nothing recorded the complete result.
How do I put back just the thing that broke?
Without rebuilding the machine or overwriting unrelated changes that are still correct.
How do I move between valid configurations?
Without reopening several applications and recreating the same coordinated changes by hand.
HOW PINMAN WORKS
Define what matters. Then work at the level of individual settings.
A Schema defines the specific files, Registry areas, Windows settings, and device settings Pinman may inspect or change. Pinman does not attempt to track the entire PC.
Each tracked Item has its own current value, Capture history, and before/after comparison. The point is not merely to report that a file changed, but to show which selected value changed.
CAPTURE
Record a point in time.
A Checkpoint records current values and change; a Savepoint also preserves the tracked file data needed for recovery.
COMPARE
Detect relevant drift.
Compare the live Machine with a Capture or intended Profile.
RECOVER
Return only what is needed.
Recover tracked settings or file data from a Savepoint without rebuilding the machine or restoring an entire system image.
APPLY
Coordinate a declared configuration.
Apply a Profile across the selected files and settings it covers while leaving unrelated configuration untouched.
Use the Pinman UI directly, or work through CLI, REST, and MCP interfaces for scripts, automation, and AI agents. Role-based logins separate day-to-day operation (Operator Mode) from configuration work (Technician Mode).
DAY 2 CONFIGURATION WORK
Understand what the machine became, then change it deliberately.
What changed after that update?
A dedicated Windows PC behaves differently after an application, driver, or operating-system update. Compare the live Machine with an earlier Capture, identify the selected values that changed, preserve intentional changes, and correct only the configuration that drifted.
Move between defined operating modes.
One machine may have several valid configurations for different displays, hardware arrangements, application modes, or performance requirements. Profiles coordinate the selected changes across applications without a whole-machine restore.
PINMAN + AI
Give an agent legible state and bounded authority.
Configuration that is normally scattered across opaque formats becomes a structured, queryable view with selected state, Capture history, Journal context, and intended Profiles.
The Schema defines the locations Pinman may inspect or change. The installed tier defines which operations are available. Changes follow named operations that can be captured, compared, verified, and recorded rather than unrestricted system access.
- 01Read the selected current state.
- 02Compare it with an earlier Capture or intended Profile.
- 03Pinpoint relevant drift and explain a correction.
- 04Create a recovery point where the operation requires one.
- 05Apply the permitted change and verify the result.
Pinman does not ship an AI model or agent. It supplies the UI, CLI, REST, and MCP surfaces through which your tools work.
By collecting selected PC state and change history over time, your organization can build a longitudinal dataset for grounding or training internal AI models on its own infrastructure.
ALONGSIDE THE TOOLS YOU ALREADY RUN
Pinman works at the individual-machine, per-setting layer.
Endpoint and configuration-management tools deploy and enforce policy, applications, updates, and baselines across managed devices. Pinman works on what an individual machine actually became: selected setting history, drift, recovery, and deliberate configuration changes.
| Category | Familiar examples | What that category is for | What Pinman adds |
|---|---|---|---|
| Backup and restore | Veeam, Acronis | Recover files or whole-system images | A per-setting view of selected configuration and selective recovery |
| Drift and compliance monitoring | Tripwire, Qualys | Report deviation from a standard | Capture, compare, recover, and apply through the same selected model |
| Endpoint and configuration management | Group Policy, Configuration Manager/SCCM, Intune | Deploy and enforce baselines across managed devices | Versioned history and deliberate changes deep within one machine, including application and vendor settings |
Backup and restore
Veeam, Acronis
- What that category is for
- Recover files or whole-system images
- What Pinman adds
- A per-setting view of selected configuration and selective recovery
Drift and compliance monitoring
Tripwire, Qualys
- What that category is for
- Report deviation from a standard
- What Pinman adds
- Capture, compare, recover, and apply through the same selected model
Endpoint and configuration management
Group Policy, Configuration Manager/SCCM, Intune
- What that category is for
- Deploy and enforce baselines across managed devices
- What Pinman adds
- Versioned history and deliberate changes deep within one machine, including application and vendor settings
Pinman complements these categories. It does not replace them wholesale.
ALONGSIDE EXISTING TOOLING
Keep the fleet tools you already use.
Fleet tools continue to own policy and baseline management. Pinman adds per-machine Capture, drift, recovery, and operator or agent access.
STANDALONE
No central control plane required.
For one or a few highly individual machines, Pinman supplies the configuration history, Profiles, recovery, and UI without a central control plane to deploy.
A WORKING EVALUATION, NOT AN EMPTY INSTALL
Learn Pinman in a sandbox project, then evaluate it on your own configuration.
The sandbox project runs the real Pinman on your real machine — a guided tutorial and a safe place to experiment, with nothing outside it touched.
- A sandbox project for learning and demos — safe to break, easy to reset.
- A focused Getting Started guide.
- Every Pro capability for the time-limited evaluation period.
- A local, offline-capable installation suitable for machines that do not maintain an internet connection.
Design and implementation help is available.
Support and consulting services are available to help design and implement how Pinman can be used in your organization.
Discuss your organization →CLEAR EXPECTATIONS
Built for an individual machine—not a new control plane.
- Not fleet management or centralized policy enforcement.
- Not provisioning or multi-host orchestration.
- Not metrics, uptime, or performance monitoring.
- Not a bundled AI model or agent.
- Not whole-machine disaster recovery.
License
Pro is a one-time, non-subscription license covering up to three of your own machines (Windows PCs), with offline use and license recovery. Free during the beta.
Closed beta
Every Pro capability is available during the closed beta. Beta access ends when Pinman 2.0 is released.