Loading…
Open-Policy Exchange
~4 min to deploy
SaaS Ops Pack
Cloud spend, discount, and entitlement gates — stop runaway burn, margin leakage, and unsupported entitlement changes.
For: B2B SaaS finance, RevOps, DevOps
SOC 2 CC6.1ISO 27001 A.5.15Change evidence
What it enforces
Cloud Spend Circuit Breaker
Restrains automated changes that would materially increase daily burn.
Discount Logic Gate
Escalates discount exceptions when contract value evidence is missing.
Entitlement Enforcement
Checks plan and contract terms before premium access is granted.
saas-ops-pack.yaml
# SaaS Ops Pack
# Fork: the three gates from the saas_ops starter pack, with your thresholds.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: saas-ops-pack
surface: sdk
policy_pack_id: saas_ops
standards: [SOC2-CC6.1, ISO27001-A.5.15]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: cloud_spend_circuit_breaker
when: "action == 'infrastructure.change'"
decision: |
RESTRAIN IF daily_burn_delta_percent > 15
ALLOW OTHERWISE
reason_code: burn_delta_over_threshold
- name: discount_logic_gate
when: "action == 'pricing.discount'"
decision: |
ESCALATE IF discount_percent > 20 AND contract_value_usd < 50000
ALLOW OTHERWISE
reason_code: discount_evidence_missing
- name: entitlement_enforcement
when: "action == 'entitlement.grant'"
decision: |
BLOCK IF feature not in plan.entitled_features
ESCALATE IF contract.term_end < now
ALLOW OTHERWISE
reason_code: feature_not_entitled
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.