🛡️ AutoCompliance
GDPR + SOC 2 compliance autopilot for small businesses.
Compliance consultants charge $5,000–$50,000. AutoCompliance does the first 80% free, in 10 minutes.
Demo
Watch it work: answer questions, get your grade, fix list, and documents.
Sample report: a company scores 67% (Grade C) with prioritized fixes.
Install
From PyPI (once published):
pip install autocompliance
Local development:
git clone https://github.com/Mahiroyal804/autocompliance.git
cd autocompliance
pip install -e .
Requires Python 3.9+. Zero third-party dependencies — standard library only.
Usage
# Full interactive assessment (40 questions, GDPR + SOC 2)
autocompliance assess --company "Acme Inc" --email privacy@acme.com
# Save to a custom folder, with PDFs
autocompliance assess --company "Acme Inc" --output ./compliance-report --pdf
# GDPR only
autocompliance assess --company "Acme Inc" --frameworks GDPR
# Just generate the document templates (no questions)
autocompliance docs --company "Acme Inc" --pdf
# List all controls
autocompliance controls
What you get after 40 questions
Answer 40 yes/no questions and AutoCompliance generates everything into
./compliance-report/:
- 📊 Compliance grade (A–F) with per-framework scores (GDPR + SOC 2)
- 🎯 Prioritized fix list — critical → high → medium, each with a concrete remedy
- 📄 15 document templates (markdown + optional PDF):
- Privacy Policy, DPA template, RoPA sheet
- SOC 2 readiness checklist, risk register
- Incident response plan, security policy, DSR playbook
- Vendor register, retention schedule, access/change policies
- Backup runbook, LIA & DPIA templates
- 🖼️ Client-ready HTML report — show customers and auditors where you stand
- 💾 Raw JSON of every answer and score (for your records)
Example
$ autocompliance assess --company "Demo Inc" --output ./compliance-report --pdf
AutoCompliance assessment — Demo Inc
GRADE: C (59%)
GDPR: 61%
Top fixes:
[HIGH] Publish a privacy notice
[HIGH] Define one intake channel
[HIGH] Enable TLS everywhere
Report: ./compliance-report/compliance-report.html
30 documents: ./compliance-report/documents
What's inside
| Framework | Controls | Questions |
|---|---|---|
| GDPR | 9 (lawful basis, transparency, DSR, security, breach, RoPA, vendors, minimization, DPIA/DPO) | 22 |
| SOC 2 | 7 (access, change, monitoring, backups, vendors, risk, policies) | 18 |
| Total | 16 | 40 |
Questions live in autocompliance/questions.json (plain JSON — no YAML parser needed,
keeping the package dependency-free).
Development
# Run tests (stdlib unittest, no pytest needed)
python -m unittest discover -s tests
# Build for PyPI
python -m build
# Check the package
twine check dist/*
Roadmap
- Web UI + hosted SaaS version
- Evidence collection (auto-check TLS, DNS, headers)
- ISO 27001 module
- Auditor export pack
Disclaimer
Templates are starting points, not legal advice. Have a lawyer review before relying on them.
License
MIT — make compliance boring. 🛡️
Metadata
Release files for autocompliance 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| autocompliance-0.2.0.tar.gz | 22.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autocompliance-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.4 kB
Release files / autocompliance-0.2.0.tar.gz
| Download URL | autocompliance-0.2.0.tar.gz |
|---|---|
| Size | 22.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ecd1654b1bf81ceab92920e59092670b8393791cffadd8a8f03f67d76eea6451
|
|
BLAKE2b-256 checksum How to use checksums |
d262cb34637761d94e94f7e326ef99e74542d396339f88e408695055f904a8a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / autocompliance-0.2.0-py3-none-any.whl
| Download URL | autocompliance-0.2.0-py3-none-any.whl |
|---|---|
| Size | 28.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1eb5181980d8a44a710ef35663fe984d0ce59b427ee9e373635187a3277acdfa
|
|
BLAKE2b-256 checksum How to use checksums |
70b84ac95486d9bc4b68e3cecacd72eeac0fa357d4d4c1df22521c22e179d583
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for autocompliance 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.