.drako.yaml presets. Start from a template and override only what you need.
Using templates
Template inheritance
Apply a template via theextends field. Your config overrides anything the template sets:
- Scalar values (
mode,retention_days) are replaced by your override. - Lists (
permitted_tools,tool_types) are replaced entirely — not appended. - Nested objects are merged recursively.
To preview the fully resolved config after inheritance, run
drako config show.Available templates
base
Sensible defaults for any project. The foundation — every other template extends this.
startup
Balanced for speed and safety. More permissive than enterprise, more structured than base.
fintech
PCI compliance, spend caps, strict DLP. MiFID II, PSD2, SOX, SEC Rule 15c3-5.
healthcare
HIPAA alignment, PHI detection, 6-year audit retention. HIPAA Privacy Rule, HITECH Act.
eu-ai-act
EU AI Act Articles 9, 11, 12, 14. High-risk rules take effect August 2, 2026.
enterprise
Maximum governance. Intent verification, A2A security, topology monitoring.
Template details
base — Recommended defaults
base — Recommended defaults
The foundation. Every other template extends this. Use it for projects that don’t fit a specific industry vertical.Key design decisions:
- Governance level:
autopilot - Posture: Audit-first. Nothing is blocked by default.
- HITL in
auditmode: logs that approval would be needed but doesn’t pause execution. - DLP in
auditmode: PII is logged but not blocked. - Short audit retention (7 days) — extend for compliance requirements.
- Per-action spend limit of $10 — tighten for production.
startup — Balanced for speed and safety
startup — Balanced for speed and safety
For startups that need to move fast without breaking compliance.What’s different from base:
- Governance level:
balanced - Posture: Audit-first with more generous limits.
- HITL only triggers for
paymentandexecute(notwrite). - Higher magnitude limits per session ($100, 200 records).
- Longer circuit breaker tolerance (10 failures vs. 5).
- 30-day audit retention.
drako upgrade --balanced to enable DLP enforcement and ODD enforcement once you’ve reviewed the audit logs.fintech — Financial services
fintech — Financial services
For payment platforms, trading systems, and financial data processors.Compliance coverage:
- Governance level:
strict - Compliance references: MiFID II, PSD2, SOX, SEC Rule 15c3-5
- Posture: Enforcement active. Default-deny for ODD. Cryptographic audit trail.
| Standard | Requirement | Drako implementation |
|---|---|---|
| MiFID II Art. 16 | Recordkeeping | Cryptographic audit trail |
| PSD2 SCA | Strong Customer Authentication | HITL for payment tools |
| SOX Sec. 404 | Internal controls | ODD + HITL |
healthcare — HIPAA-aligned
healthcare — HIPAA-aligned
For healthcare applications processing Protected Health Information (PHI).Compliance coverage:
- Governance level:
strict - Compliance references: HIPAA Privacy Rule, HIPAA Security Rule, HITECH Act
- Posture: Maximum DLP enforcement. Conservative trust thresholds. 6-year audit retention.
| Regulation | Requirement | Drako implementation |
|---|---|---|
| HIPAA § 164.312(b) | Audit controls | Cryptographic audit trail |
| HIPAA § 164.502(b) | Minimum necessary | max_records_per_action: 25 |
| HIPAA § 164.308(a)(5) | Access controls | ODD + HITL |
| HITECH Act | Breach notification readiness | Audit trail provides evidence chain |
eu-ai-act — EU AI Act high-risk compliance
eu-ai-act — EU AI Act high-risk compliance
For AI systems classified as high-risk under EU AI Act (Regulation 2024/1689). High-risk rules take effect August 2, 2026.Article coverage:
Run
- Governance level:
strict - Compliance references: EU AI Act Art. 9, 11, 12, 14; ISO 42001
- Posture: Full enforcement. 10-year audit retention. All four Act articles covered.
| Article | Requirement | Drako implementation |
|---|---|---|
| Art. 9 | Risk management system | 97 scan rules, ODD enforcement, magnitude limits |
| Art. 11 | Technical documentation | Agent BOM, compliance reports, context versioning |
| Art. 12 | Record-keeping (10 years) | Cryptographic audit trail (retention_days: 3650) |
| Art. 14 | Human oversight | HITL checkpoints (mode: enforce, timeout_action: reject) |
drako scan . --format compliance to get a gap report against these four articles.enterprise — Maximum governance
enterprise — Maximum governance
For large organizations with the strictest internal compliance posture. Includes A2A authentication and topology monitoring.What’s unique to enterprise:
- Governance level:
strict - Posture: Everything enforced. Zero default-allow. Cryptographic trail. A2A secured.
- HITL triggers for the
networktool type (not just write/execute/payment). - A2A authentication enforced (DID-based credential exchange).
- Credential auto-rotation every 12 hours.
- Topology monitoring enabled (circular dependency and resource contention detection).
- Shorter intent TTL (120s vs. 300s default).
- HITL spend trigger at $10 (very tight).