◈ Oracle PL/SQL · Regulatory compliance

Know which code breaks when regulations change.

Shadow analyzes your entire Oracle PL/SQL codebase against any legal amendment — detecting impact, generating fix patches, and routing approvals. In under 30 seconds.

Start free → See sample output
93%
Cost reduction
3,819%
Annual ROI
< 30s
Analysis time
JP · SG
Jurisdictions
The problem

Regulatory changes break Oracle code.
Nobody knows where.

Every time a law changes — tax rates, data protection rules, capital requirements — your PL/SQL breaks somewhere. Finding it manually takes weeks.

🔍

Manual search takes weeks

DBAs grep through thousands of procedures hoping to find all affected code. They miss things.

💰

Consultants charge millions

A typical regulatory impact assessment: $300K–$1M, delivered in 3 months. Shadow does it in 30 seconds.

⏰

Compliance deadlines don't move

MAS notices, GST amendments, Basel III updates — the enforcement date is fixed. You can't be late.

How it works

Three steps. No setup.

Upload your code, tell Shadow what changed, get a full impact report with patches.

1

Upload your PL/SQL packages

Point Shadow at your Oracle source files — packages, procedures, functions, triggers. No database connection required.

2

Select the regulatory amendment

Choose from built-in law dictionaries (MAS, PDPA, GST, tax code, employment law) or define your own. Shadow maps every changed term to your code.

3

Get impact report + auto-fix patches

Shadow returns: a risk-scored impact map, auto-generated fix patches for each affected location, and a governance approval queue. Review, approve, commit.

Sample output

What you get

Real output from analyzing a financial services codebase against a GST amendment and three other regulatory changes.

shadow analyze --amendments amendment-sample.json --source ./src 
◈ Shadow v1.0 — Regulatory Impact Analyzer
─────────────────────────────────────────────────────

📚 Dictionaries loaded
  JP  消費税法           184 terms  · 30 patterns
  JP  民法               89 terms   · 20 patterns
  JP  労働基準法          74 terms   · 15 patterns
  JP  金融商品取引法      80 terms   · 25 patterns
  SG  MAS/PDPA/GST       50 terms   · 10 patterns
  Total: 477 terms / 100 patterns across 5 dictionaries

🔍 Phase 1–3: Static analysis
  PKG_ORDER_MANAGEMENT    ████████████ 75/100 [CRITICAL]
  PKG_PAYMENT_PROCESSING  ██████████░░ 60/100 [HIGH]
  PKG_CUSTOMER_DATA       ████████░░░░ 45/100 [MEDIUM]

📊 Amendment: GST (Amendment) Act 2026  [HIGH · SG]
  Direct impact   21 locations
  Indirect impact  2 locations
  Risk score      60/100

  PKG_ORDER_MANAGEMENT.func_calc_gst          line 312  CRITICAL
    → v_gst_rate := 0.09;  ← hardcoded rate, must update to 0.10
  PKG_ORDER_MANAGEMENT.func_calc_gst_inclusive line 330  CRITICAL
    → p_amount * 1.09  ← multiplier reflects old 9% rate
  PKG_ORDER_MANAGEMENT.proc_sg_aml_check       line 358  HIGH
    → PDPA consent validation requires updated retention period

🔧 Auto-fix patches generated
  ✓ GST rate: 0.09 → 0.10          strategy: master_lookup
  ✓ GST inclusive: 1.09 → 1.10   strategy: master_lookup
  ✓ Retention constant update              strategy: const_replace

🏛️ Governance: STRICT policy applied (tax/rate change)
  auto-approved    0
  senior review    3 pending   ← GST patches require senior sign-off
  compliance       0

━━━ EXECUTIVE SUMMARY ━━━
  Amendments analyzed    4  (3× JP, 1× SG)
  Impact locations      45
  Auto-fix patches       8
  Compliance grade       D  59/100  → target B by Q2

  Without Shadow         ¥130M/year  (consulting)
  With Shadow            ¥11M/year
  Annual savings         ¥119M  ·  ROI 3,819%  ·  payback < 1 month

  Tests: 15 pass / 0 fail
Who uses Shadow

Every regulated industry runs Oracle.

If your Oracle database is subject to legal compliance requirements, Shadow is built for you.

🇸🇬

Singapore Financial Services

MAS regulations, PDPA data protection, GST amendments — Shadow ships with SG law dictionaries out of the box.

MAS PDPA GST AML/KYC
🇮🇳

IT Services & System Integrators

Embed Shadow's API into your delivery pipeline. Automate compliance checks for all your Oracle clients at once.

API access Multi-client CI/CD
🇺🇸🇬🇧

US / UK Financial Institutions

SOX, Dodd-Frank, Basel III updates hit Oracle PL/SQL hard. Shadow's custom dictionary feature covers any jurisdiction.

SOX Basel III Custom dict
🗾

Japanese Enterprises

消費税法、民法改正、最低賃金改定、金融商品取引法 — built-in JP dictionaries covering major law amendments.

消費税法 民法 金融商取
Pricing

Simple. Transparent. No calls required.

All plans include full impact analysis. No hidden fees, no procurement process, no annual commitments.

Free
$0
Try Shadow before you pay anything.
  • 1 analysis / month
  • Up to 500 lines of PL/SQL
  • JP + SG built-in dictionaries
  • Impact report + risk scores
  • Email support
Get started
Dev MOST POPULAR
$19/month
For individual DBAs and engineers.
  • Unlimited analyses
  • Unlimited PL/SQL lines
  • JP + SG built-in dictionaries
  • Auto-fix patch generation
  • Governance approval workflow
  • HTML + JSON report export
  • Email support
Subscribe →
Team
$79/month
Custom dictionaries and API access.
  • Everything in Dev
  • Custom law dictionaries
  • REST API access
  • 5 team members
  • Executive dashboard
  • Compliance analytics
  • Priority email support
Subscribe
API
$299/month
Embed Shadow in your own toolchain.
  • Everything in Team
  • Full REST API (unlimited)
  • Multi-client / multi-codebase
  • Webhook notifications
  • Custom jurisdiction build
  • SLA: 48h email response
Contact
No calls. No demos. No sales process. Shadow is self-serve. Sign up, upload code, get results. All support is async via email. Typical response time: < 24 hours.
FAQ

Common questions

Do you offer demos or onboarding calls?
No. Shadow is designed to be self-serve. The sample output on this page shows exactly what you get. All communication is by email — async, text-only. If the product doesn't explain itself well enough for you to start, that's a product problem we want to fix.
Which Oracle versions are supported?
Shadow works with PL/SQL source files from Oracle Database 11g through 23c. No database connection required — analysis runs on source code files only.
Which jurisdictions are currently supported?
Japan (消費税法, 民法, 労働基準法, 金融商品取引法) and Singapore (MAS Capital Adequacy, PDPA, AML/CFT, GST, Employment Act, Companies Act) are included in all plans. US, UK, and EU dictionaries are in development. The Team and API plans let you define custom dictionaries for any jurisdiction.
Is my source code stored?
Analysis runs on your uploaded files and results are returned immediately. Files are not retained after analysis completes. On-premise deployment is available on the API plan — contact us by email.
How accurate are the auto-fix patches?
Shadow generates patches for high-confidence matches (master_lookup, const_replace, rate_update strategies). All patches are staged for human review before application — Shadow flags what needs changing and suggests how, but nothing is applied automatically without approval.
Can I use Shadow for a client's codebase?
Yes. The API plan is designed for SIs and consulting firms managing multiple Oracle codebases. You can run analyses for different clients through the same API key. Multi-client dashboard is included.
What's the refund policy?
Cancel anytime. If Shadow doesn't detect a single impact in your first analysis, email us and we'll refund your first month — no questions.

The next regulatory deadline is already set.

Start with the free tier. Upload one package. See how many lines are affected by the last amendment you know about.

Start free →