<30min to first export
One pilot session
Install one agent, run one signed script, export the audit file. That is usually enough to answer the buy-or-not question.
Prove every signedscript run
Govern PowerShell with signing policy and exportable audit - so MSPs can answer assessors and insurers without RMM log archaeology.
Install one agent, run one signed script, and export the audit file - most teams do it in under thirty minutes.
<30m
Pilot to first audit export
1
Platform for governed scripts
15MB
Lightweight agent target
No credit card · Pilot access within two business days · Enterprise reviewed manually
Try it before you buy
Most teams export their first audit file in under thirty minutes.
Four modules, one platform
Scripts, agents, trust evidence, and optional monitoring.
Scripts
Sign, approve, and run PowerShell
Block unsigned scripts when policy requires it. Every run is recorded with who ran what on which machine.
- PowerShell IDE with approval workflows
- Push/pull file pipeline in script runs
- Platform catalog duplication into tenant libraries
- Execution queue with a clear audit record
- Complex install pipelines when Win32 is the wrong tool
<30 mintypical first signed script + export
Explore script governance
Agents
Lightweight Windows agents
Deploy a small agent that polls outbound. Search and target machines with catalog APIs built for large fleets.
- ~15MB single-file deployment target
- Outbound polling - no inbound firewall holes
- Catalog APIs for 100k+ agents per tenant
15MBagent footprint target
Explore agent management
Trust
Evidence for security reviewers
Download what is built vs. not. Export audit rows from trial and attach them to your questionnaire.
- Shipped and Gap tables on the trust hub
- Downloadable trust pack
- Architecture notes for procurement
1trial session to export audit rows
Download trust materials
Monitoring
Optional probes and NOC views
Add SNMP ingest and NOC dashboards when your SKU includes the Monitoring module.
- Packaged Monitoring module gates
- Probe ingest with rollup retention controls
- Lazy policy trees for fleet-scale operators
Optionalmodule - buy when entitled
Explore monitoring moduleWhat you get from a pilot
Three distinct outcomes - pilot fit, audit export, and fleet scale.
Test on one customer first
1pilot tenant before portfolio rollout
Run a pilot group before you mandate Trustholm fleet-wide.
Compare optionsHand auditors a file
JSON/CSVexportable script run history
Export who ran which signed script on which machine - without digging through RMM logs.
Review security evidenceGrow the fleet safely
100k+agents per tenant via catalog APIs
Server-backed search and pagination - not full-fleet dropdowns.
See platform architectureWhat early evaluators report
Design-partner MSPs and security reviewers validating script governance fit-not certification marketing.
“We reproduced a signed script run and CSV audit export in one pilot session-that export slice is what our cyber insurer actually asked for.”
40+MSP evaluations in progress
<30mMedian time to first audit export in trial
Shipped/GapHonest evidence tables published
69%MSP leaders reporting 2+ breaches in 12 months
Privileged script runs need governance proof
Signing, four-eyes approval, and exportable audit-verify in a trial tenant. No SOC 2 badge claims; honest Shipped/Gap evidence for assessors.
Compliance by region
Pick your jurisdiction hub for framework-specific evidence pages.
Australia
Essential Eight, IRAP/ISM consumer framing, and AU data residency.
United States
NIST CSF / 800-53 consumer mapping and CMMC Level 2 enabler framing.
United Kingdom
Cyber Essentials and NCSC-aligned remote access evidence.
European Union
GDPR processor framing, DORA ICT risk, NIS2 supply-chain evidence, and EU digital sovereignty for MSP script governance.
SOC 2 evidence framing applies across regions · Compare incumbent tools · Trust downloads
Simple, Transparent Pricing
Public bundles from your operator catalog-or contact us for enterprise
Start trial
30-day evaluation with Super Admin review
- Agent seats per bundle
- Signed script orchestration
- Security audit export
- Optional monitoring module
Frequently asked questions
- What does Trustholm do?
We prove which signed scripts ran on which client machines. MSPs use Trustholm to enforce signing policy, run scripts with a clear record, and export audit files for assessors and cyber insurers.
- What makes Trustholm different from NinjaOne or ConnectWise Automate?
We're built for script governance, not full endpoint management. If you need both, check our comparison pages to see if we're a fit.
- Do you hold SOC 2 or ISO certifications?
We're not SOC 2 certified yet. We publish exactly what's built vs. not, mapped to common audit controls, so your security team can verify it themselves.
- How long does deployment take?
Most teams install one agent, run one signed script, and export audit rows in under thirty minutes. Fleet-scale rollouts use paginated catalog APIs -no loading every endpoint into a dropdown.
- Where is data hosted?
Launch region options and subprocessors are on the trust hub. Exact residency for your contract is confirmed during onboarding -not inferred from marketing copy.
- What should a business owner get from a trial?
A working audit export you can show your security reviewer or insurer -before you commit portfolio budget. If script evidence is your bottleneck, one pilot session usually answers the buy-or-not question.
More detail for evaluators
What we do: Block unsigned scripts when your policy requires it. Record who ran what on which machine. Export that history for auditors and insurers -separate from RMM operational logs.
What we are not: We do not hold SOC 2, Essential Eight, CMMC, or other third-party certifications. See the trust hub for what is built vs. not.
Where to go next: Platform overview for modules and architecture. Compare how we fit beside NinjaOne, ConnectWise, and PDQ. Trust downloads for procurement packs. Start a trial on Govern (no credit card); Evidence and Enterprise tiers are reviewed within two business days.