RegWatch Private VPC - AI Compliance Monitoring on EKS
Dynamiq · Cybersecurity & IT
Certification per AWS Marketplace.
Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
RegWatch Private VPC is the self-managed edition of RegWatch's AI-agent-driven regulatory-compliance monitoring platform. It deploys into your own AWS account on Amazon EKS using a Helm chart, so the platform runs inside your VPC under your security and compliance controls.
WHAT RUNS WHERE
Show the rest of the publisher’s description (24 more lines)
In your cluster / account (the data plane):
- api - the application API (FastAPI).
- worker - runs the AI monitoring, triage, and analysis jobs.
- scheduler - enqueues monitoring cycles on a schedule.
- web - the user interface.
- PostgreSQL 16 with the pgvector extension (your RDS/Aurora or in-cluster), Redis, and object storage (Amazon S3) for evidence and reports.
Leaves your account (disclosed external dependency):
- The worker calls the Anthropic API (Claude) for agent reasoning and an embeddings provider for retrieval. These are required for the AI features; the deployment is not air-gapped. You control egress via your own network policy and allow-list.
CAPABILITIES (identical to the hosted edition)
- Monitor regulatory sources grouped into watchlists, with AI source recommendations.
- Triage findings by relevance and urgency with de-duplication and custom exclusion rules.
- Business-impact analysis and recommended actions on every alert.
- One-click conversion of alerts into structured obligations with owner, deadline, risk level, checklist, and linked evidence.
- Deadline dashboards, configurable PDF reports, and a compliance assistant over your own data.
SECURITY & ARCHITECTURE
- Strict per-organization isolation enforced at the database layer via PostgreSQL row-level security.
- SAML single sign-on and role-based access control with fine-grained permissions.
- Full audit logging of changes; encryption in transit and at rest; evidence retained under your controls.
- Stateless, horizontally scalable services; the worker scales with load (bounded by model API rate limits, not cluster CPU).
DEPLOYMENT
Install with standard Helm commands against your EKS cluster. You provide connection details for PostgreSQL (with pgvector), Redis, an S3 bucket, and API keys for the model and embeddings providers via Helm values and Kubernetes secrets. Database schema is created and upgraded automatically via migrations. Full prerequisites and step-by-step instructions are provided in the usage instructions and accompanying documentation.
COMMERCIALS & SUPPORT
Private VPC is offered as an annual contract. Multi-year terms, custom scope, and enterprise support are arranged through AWS Marketplace private offers. Support is provided by the RegWatch team with an assigned account manager.
This listing is for the self-managed edition. For the fully hosted multi-tenant service, see the "RegWatch - AI Regulatory Compliance Monitoring" SaaS listing.
Highlights
Highlighted by the publisher on AWS Marketplace.
Runs in your VPC: the entire data plane deploys to your Amazon EKS cluster via Helm - your network, your KMS keys, your retention. Regulatory data and evidence stay in your account.
The same AI compliance product: agentic monitoring, business-impact analysis, and one-click structured obligations with owner, deadline, and evidence.
Enterprise controls: SAML SSO, PostgreSQL row-level multi-tenant isolation, full audit logging, and encryption in transit and at rest.
Preview
5 images
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Plans and pricing as listed
1 listed- Units
Refund terms
As stated by the publisher on AWS Marketplace.
All charges are non-refundable except where required by law. If you believe there has been a billing error, or you have exceptional circumstances, contact support@regwatch.io within 30 days of the charge and we will review your request in good faith. Cancellations take effect at the end of the current contract term; no partial-term refunds are provided. For private offers, the refund terms stated in the offer apply.
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.