POLICY ENGINE
Business rules enforced at API speed.
OWMS validates any decision against your business logic in under 100ms, without touching your existing stack. One endpoint. Every policy enforced.
Policy check response time
<100ms
Native data source types
4
JSON files per policy pack
5
Code changes to your stack
Zero
THE PROBLEM
Policy enforcement is missing or hard-coded everywhere.
Business rules live in spreadsheets, email threads, and tribal knowledge. When something breaks, no one can trace where the rule came from.
Approval rules buried in code
A discount threshold changes. Now you need a developer, a release cycle, and a prayer nothing else breaks.
No single source of truth
Finance has one version of the margin policy. Sales has another. Operations follows a third. None of them match.
Audit trails are an afterthought
When a regulator asks why a transaction was approved, the honest answer is “we’re not sure.” That’s a problem.
WHAT OWMS DOES
Two components. One policy engine.
OWMS Studio lets business teams author rules. OWMS Server enforces them via REST API at the moment of every decision.
OWMS Studio
Visual rule builder for business users. Define policies, thresholds, and exception logic with no SQL and no code. Rules are version-controlled and auditable.
OWMS Server
A REST API with a single endpoint, POST /check_policy. Send decision context, get approved or denied in under 100ms. Deploy anywhere.
Multi-Source Data
Rules pull reference data from CSV, PostgreSQL, Snowflake, or MySQL. No proprietary data layer. Works with what you already have.
Policy Packs
Each policy packaged as 5 JSON files: schema, rules, conditions, exceptions, metadata. Portable, auditable, deployable across environments.
Real-Time Enforcement
Every pricing, credit, discount, or approval decision is checked against live policy at the exact moment it happens. No batch runs.
Full Audit Trail
Every check logged with timestamp, input context, rule applied, and outcome. Compliance gets the evidence they need without calling engineering.
HOW IT WORKS
From rule to enforcement in four steps.
Business teams own the rules. Engineering integrates once. Every decision is enforced automatically thereafter.
1
STEP 1
Author in Studio
Business users define approval logic, thresholds, and exceptions in the OWMS Studio visual editor.
2
STEP 2
Package as a Pack
Rules compile into a Policy Pack — five JSON files, version-stamped and ready to deploy.
3
STEP 3
Call /check_policy
Your application sends decision context to the OWMS Server REST API. One endpoint, any language.
4
STEP 4
Get the verdict
OWMS returns approved, denied, or escalate — with the rule applied and a full audit record — in under 100ms.
INTEGRATION
One API call. Every policy enforced.
Integrate in an afternoon. No new infrastructure, no vendor lock-in.
Works with any language or framework
Deploy on-premise, Azure, AWS, or GCP
Supports multi-tenant policy packs
JSON response with decision reason codes
SAP-compatible context schema
REST API
Python
Node.js
Java
SAP-compatible
Multi-tenant
POST /check_policy
REQUEST
{
“decision”: “discount”,
“amount”: 4200,
“customer_tier”: “gold”
}
RESPONSE
{
“result”: “approved”,
“rule”: “discount.gold.max”,
“elapsed_ms”: 38
}
APPROVED
Resolved in 38ms
