Ot

OpenL Tablets

Azure Developer Tools 1 variation

author business rules as excel decision tables and serve them as APIs

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Variations

This product is available in the build below. Open it for the operating system, cloud and version detail, or read its deployment guide.

ProductCloudOperating systemVersion
OpenL Tablets Azure Standard View · Guide

Overview

OpenL Tablets is an open source business rules management system. Rules are written as decision tables, lookup tables and spreadsheets in ordinary Excel workbooks, kept under Git version control, and executed by a rules engine that publishes each deployed ruleset as a REST and SOAP endpoint. OpenL Studio gives business analysts a browser IDE to create and edit rule projects, run and trace tests, and review project history, so pricing, eligibility and rating logic can change without a release of the surrounding application.

Why the cloudimg image

The OpenL Studio administrator password and a separate rule service credential are generated on the first boot of your own VM, never baked into the image. This matters here: the product ships configured for local evaluation, where its default mode applies no authentication at all and its rule endpoints answer to anyone. The cloudimg image forces multi-user authentication, places the rule endpoints behind authentication at the TLS front door, and closes the embedded user database to local access. A default deny firewall leaves only SSH and HTTPS reachable, no sample projects or demo accounts ship, and a paired deployment guide covers first sign in through calling a deployed ruleset. Backed by 24/7 support.

Common uses

  • Pricing, rating and eligibility rules owned by business analysts
  • Decision logic served to applications as versioned REST and SOAP APIs
  • Regulated rule changes needing history, tests and traceability