juro-deploy installs the Juro agent container into your own infrastructure. It runs a private, non-custodial scan for GDPR, DPDP, and DORA obligation markers — entirely inside your VPC or local machine. No scan data or infrastructure state leaves your environment.
One-liner install
curl -sSL https://jurocompliant.com/install.sh | sudo bash
The script downloads the juro-deploy CLI binary for your platform (Linux x64, macOS arm64, macOS x64), verifies the download, and installs it to /usr/local/bin. On Linux, Docker Engine and the Compose v2 plugin are installed automatically if not already present.
What do I need before installing juro-deploy?
- Docker — Engine 24+ (Linux) or Docker Desktop (macOS). The installer handles Docker Engine on Amazon Linux, Ubuntu, and Debian automatically.
- AWS credentials with a read-only IAM policy — scoped to the services you want to scan (S3, RDS, CloudTrail, CloudWatch Logs, Config). See the prerequisites checklist for the exact policy document.
- Supported platforms: Linux x86_64, macOS arm64, macOS x86_64.
After install
Frequently asked questions
What does juro-deploy install?
juro-deploy installs the juro-deploy CLI binary. The agent container image is pulled when you run juro-deploy init. The agent runs inside your own infrastructure — Docker on your EC2 instance or local machine — and performs GDPR, DPDP, and DORA scanning without sending your data or infrastructure state to external servers.
What are the prerequisites for juro-deploy?
You need Docker (Engine 24+ or Docker Desktop) and AWS credentials with a read-only IAM policy scoped to the services you want to scan. See the prerequisites checklist at jurocompliant.com/checklist for the exact IAM permissions required.
Does juro-deploy send data outside my infrastructure?
No infrastructure data or PII leaves your environment. The scanner runs locally inside your Docker container. The only outbound call happens automatically after every scan, to Juro's notary endpoint for counter-signing. It sends five fields: engagement_slug_hash, bundle_sha256, ruleset_sha, agent_version, and scanned_at. It does not send infrastructure state, scan findings, configuration, or credentials.
Not sure where to start?
Run the Tier 1 surface scan first — no account, no install. It scans your domain's public-facing posture against GDPR, DPDP, and DORA obligation markers and produces a finding report with specific rule citations.
Scan your domain — jurocompliant.com →