Instead of VComply PolicyOps
Stop renting VComply PolicyOps. Own your policy register.
We build your version around your review process, map your VComply records and run it for you. Policy owners see what needs a decision and which acknowledgements are still missing.
VComply publishes a module starting price of $1,000 a month, equivalent to $12,000 a year. That is a module starting figure, not a quote for your PolicyOps setup. The page does not specify the dollar currency.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription covers
Policy administration sits inside a wider subscription
VComply prices modules separately from a custom Enterprise offer. Compare the parts your policy coordinator actually uses before choosing what to keep.
A module starting price
The public starting figure is $1,000 a month. VComply invoices annually and states a minimum contract period of twelve months.
Unlimited users, one listed admin seat
The Pro offer lists unlimited users and one admin seat. This is not a per-employee price comparison.
The policy version register
PolicyOps keeps version history around the text your organisation has written. The question for your own version is which copy is effective today.
Approval and acknowledgement records
PolicyOps provides approval routing and acknowledgement tracking. The free base records independent decisions and externally collected acknowledgement evidence.
Review schedules and follow-up
PolicyOps includes review scheduling. Your own review list can combine overdue policies, inactive owners and unresolved exceptions.
The wider suite and custom setup
Enterprise pricing is quoted separately. Scope policy administration on its own, then decide which employee access and connections your team needs.
Your own policy desk
Decisions stay with the version they belong to
Versions
One effective copy with a clear decision trail
The policy coordinator can see what is approved, what is still a draft and what has been superseded.
- check Named owner and next review date for every policy
- check An independent reviewer for each approved version
- check Approved text locked against accidental edits
- check A replacement version takes effect while the previous version stays in history
Acknowledgements
A new version means a new acknowledgement
Keep evidence attached to the wording a person actually received, with outstanding work visible by department.
- check Assignments refer to a specific effective version
- check External acknowledgement evidence recorded with an operator name
- check Overdue days shown for every outstanding assignment
- check Previous acknowledgements stay in history when the policy changes
Monday review
Join the evidence gaps before chasing people
Read the review calendar, acknowledgement backlog and exception list together. The demo answers ten cross-record questions today.
- check Overdue reviews alongside missing acknowledgements
- check Expired exceptions held by people with outstanding actions
- check Safety changes missing consultation evidence
- check Inactive policy owners and personal-record retention reviews
Paperwork
Produce the review pack in your own name
Your records produce the policy pack and acknowledgement register, with your branding and evidence references.
- check Current policy text, version and effective date
- check Recorded reviewer decisions beside their evidence
- check Acknowledgement history separated by version
- check Local review drafts and read-only reports for the coordinator
Make it yours
Design your own VComply PolicyOps replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from VComply PolicyOps. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your VComply PolicyOps data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Policy Management for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Policy Management for Claude Code
Connected to your own database
Which policies need a review this month?
POL-3
- Me ow
- Supplier approval
- Ner ve
- Alex Ward
- View_on re
- 2026-09-27
- View_days
- -20
POL-1
- Me ow
- Warehouse safety
- Ner ve
- Maya Chen
- Rsion re
- 1.0
- View_on re
- 2026-10-09
- View_days
- -8
POL-2
- Me ow
- Personal information retention
- Ner ve
- Alex Hart
- Rsion re
- 2.0
- View_on re
- 2026-10-31
- View_days
- 14
| Source_id na | Me ow | Ner ve | Rsion re | View_on re | View_days |
|---|---|---|---|---|---|
| POL-3 | Supplier approval | Alex Ward | 2026-09-27 | -20 | |
| POL-1 | Warehouse safety | Maya Chen | 1.0 | 2026-10-09 | -8 |
| POL-2 | Personal information retention | Alex Hart | 2.0 | 2026-10-31 | 14 |
Ask it anything
Ten questions for your policy review
Each answer below comes from the working demo. These combine your records for a specific review, without claiming that VComply cannot build an equivalent report.
Switching
How to switch from VComply PolicyOps
A move like this usually involves exporting and mapping your records, checking them against the import preview, then running both registers side by side before you switch.
- 1
Export the records you need
Ask your VComply PolicyOps administrator what exports are available. Export the people, policies, versions or revisions, approvals and exceptions you want to bring across. Export acknowledgement history and original policy documents too if you need to retain them, since those stay archived separately. If VComply does not specify an export format, use what your account allows, usually CSV or Excel, and check the options with VComply.
- 2
Map records and preview the import
Match the exported columns to the fields used by the new register, then prepare the records in the format its import accepts. There is no verified universal VComply export layout, so mapping is required. Start with a test run using the import preview before loading anything for real. The import accepts mapped CSV records for people, policies, revisions, approvals and exceptions.
- 3
Check and reconcile flagged records
Review the preview and any validation issues before committing the import. Check that records link to the right people, policies and versions, and reconcile missing or changed information against your VComply records. The import preserves source IDs and refuses changed records rather than overwriting historical evidence. Imported revisions remain drafts until you check them and make them effective.
- 4
Run both registers side by side
Keep VComply PolicyOps available while you check the new register against it for a short period. Compare the policies, owners, versions, decisions, review dates and exceptions you rely on, and confirm that the records and evidence you need are present. Use this period to resolve gaps or mapping mistakes before making the new register your working record.
- 5
Switch off VComply PolicyOps
Once you have checked the imported records and are comfortable using the new register for your policy administration, plan the handover and stop using VComply PolicyOps for that work. Keep the original documents and historic acknowledgement evidence archived separately. Do not treat the new register as a replacement for wider VComply risk, audit or employee workflows unless those have been scoped too.
Where the real effort goes
The main work is usually mapping your own fields and rules to the new register, then reconciling the records and deciding how much history to bring across. Original documents and historic acknowledgement evidence remain archived separately. If you have Enterprise DNA install and run it, they handle the mapping and migration work with you, including checking the exports and reconciling the import.
Not ready for a call?
Get your VComply PolicyOps switch plan by email
We will send you the step-by-step plan for moving your business off VComply PolicyOps, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your VComply PolicyOps switch plan is on its way.
Rather talk it through? Book a call arrow_forwardChoose your level of help
Do it yourself, customise it, or have us run it
Open source
Do it yourself
Free, open source
- 1 Clone the repo and run npm install, npm test and npm run demo
- 2 Open it in Claude Code, Codex, OpenCode or Cursor
- 3 Map your VComply exports to the supported CSV staging files and preview import vcomply
- 4 Reconcile the records, then import and read /weekly-review
Built around your business
We customise it
One setup fee, then a retainer
- check Your policy categories, review rules and evidence requirements
- check Your VComply exports mapped, checked and brought across
- check An employee screen or a different stack if you need one
- check Document editing, access and distribution connections scoped for your team
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed in a database your organisation owns
- check Your policy review and document routines maintained
- check Agreed access, backups and connections operated for you
- check Run through Omni by Enterprise DNA with someone responsible for the system
Questions
Instead of VComply PolicyOps, answered
Does this replace the whole VComply suite? expand_more
The free base covers policy administration: versions, independent decisions, review dates, exceptions and externally evidenced acknowledgements. We scope the wider risk, audit and employee workflows around what your organisation actually uses. It is not a claim of full suite equivalence.
Can you bring our existing policies and history across? expand_more
We first check which exports your administrator can obtain. The free version imports mapped records for people, policies, versions, approvals and exceptions. Original documents and historic acknowledgement evidence stay archived separately. Mapping and reconciliation come before the import. Your custom scope can extend coverage to the other records you need.
Can employees read and acknowledge policies themselves? expand_more
The free base is a workspace for a policy coordinator who records external acknowledgement evidence. Enterprise DNA can build employee access, authenticated acknowledgements and distribution into your version. We agree those requirements before installation.
Does a clear review list prove we comply with the law? expand_more
No. It identifies missing records and evidence under the configured checks. Reviewers still decide whether the policy is suitable, consultation was meaningful and retention is lawful. A recorded name is an operator label, not proof of an electronic signature.
What do we pay Enterprise DNA? expand_more
One setup fee, then a retainer agreed for your version and ongoing operation. The free base has no software licence fee. Installation, migration, employee access and ongoing support are scoped around your needs.
Make the next policy review a decision, not a chase
Spend 30 minutes with Sam looking at your current policy register, what VComply costs you and the evidence your reviewers need. We will map the version Enterprise DNA can build and run for you.
Policy Management for Claude Code is free and open source, published by Enterprise DNA.
Done paying for VComply PolicyOps?
Get your version built