Perpetual Licensing for Enterprise Decision Automation

Code Effects was designed as infrastructure software, not as a hosted subscription dependency. For organizations building long-term business systems around decision automation, rule execution, compliance workflows, or AI-assisted operational logic, licensing strategy becomes part of the technical architecture itself.

Version 7 expands Code Effects from rule authoring and execution into a complete decision management platform, with the Rule Repository, Audit and the MCP server joining the Rule Editor and the Rule Engine. Every component of the platform is offered under perpetual licensing, allowing organizations to retain full ownership and operational control of their decision infrastructure, from the rules themselves to their versions, approvals and recorded production decisions.

Why Perpetual Licensing Matters

Modern enterprise systems increasingly depend on external subscription platforms for core operational functionality. This creates several long-term risks:

  • unpredictable operating costs
  • vendor lock-in
  • infrastructure dependency
  • forced migrations
  • pricing exposure
  • deployment restrictions
  • AI provider coupling
  • loss of access to decision history when a subscription ends
  • operational instability caused by third-party platform changes

Business rules engines occupy a particularly sensitive position in enterprise architecture because they directly control operational decision-making. If the rule engine becomes unavailable, inaccessible, unaffordable, or restricted, business operations themselves may be affected.

A decision management platform is even more sensitive. In version 7, the same platform that evaluates your rules also holds their immutable versions, their approvals, their tests and, with Audit, the record of every production decision they made. Under a subscription model, the ability to read that history, to prove which rule version produced a decision, and to change the logic that runs in production can all depend on a renewal.

Perpetual licensing eliminates this dependency. Once licensed, the platform remains part of your infrastructure permanently. Your applications continue to execute, and your rule history remains in your own database, regardless of future subscription pricing, cloud policy changes, hosting restrictions, or vendor business model shifts.

Perpetual License vs SaaS Subscription

SaaS rule platforms are a reasonable choice when an organization wants a vendor to host and operate the rule environment, and is comfortable with recurring fees and external dependencies. With a typical hosted rules subscription:

  • rules, versions and decision records are stored on the vendor's infrastructure
  • evaluations depend on the vendor's service and network availability
  • costs often grow with users, evaluations, environments or features
  • upgrades and platform changes follow the vendor's schedule
  • AI features, when offered, follow the vendor's choice of models and providers
  • continued access depends on continued payment

With a perpetual Code Effects license:

  • rules, versions, tests and decision records stay in a database you own
  • evaluations run inside your own applications, with no external service
  • there are no per-evaluation or usage fees
  • you decide when to update the libraries and when to run database update scripts
  • the built-in AI features use the models and API keys your application chooses
  • the licensed software keeps working without a renewal

How Code Effects Version 7 Is Licensed

Version 7 is offered as Code Effects packages. The Rule Engine and the Rule Editor are free for personal, community, development and research use as Code Effects Personal, with no limitations; see Code Effects Packages for the terms.

Commercial use is licensed perpetually, one package at a time, so organizations license only the parts of the platform they actually use. Each package includes everything in the one before it:

  • Code Effects Standard - the Rule Engine and the Rule Editor, the foundation of every implementation, with no user limits
  • Code Effects Business - Standard plus the Rule Repository: complete rule management inside your own web application, including the AI Rule Editor and the AI Assistant
  • Code Effects Enterprise - Business plus Audit: recording and explaining production decisions
  • Code Effects Ultimate - Enterprise plus the MCP server for external AI agents
Business, Enterprise and Ultimate are licensed per team of up to 30 Rule Repository users; Standard has no user limits.

For organizations that require ownership of the code itself, Code Effects Source provides the source code of the entire platform, perpetually, for organization-wide use. The Assurance, Distribution and Support add-ons extend a package with rights and services.

Every package except Code Effects Personal is downloaded with a product key from the Code Effects Portal. All earlier editions and free versions are deprecated, with an upgrade path for existing customers.

Stable Infrastructure for Long-Term Systems

Business rules are rarely short-lived. In many organizations, rule systems become deeply embedded into:

  • pricing engines
  • underwriting systems
  • eligibility workflows
  • compliance validation
  • fraud detection
  • healthcare processing
  • operational automation
  • manufacturing logic
  • internal governance systems

These systems often remain active for years or decades. A perpetual license aligns with this reality. Instead of treating the rules engine as a continuously rented operational dependency, organizations can treat it as a stable architectural component of the platform itself.

The same is true of decision history. A regulator, an auditor or a customer may ask months or years later why a decision came out the way it did. With the Rule Repository and Audit, the answer - the exact rule version that ran, the source version it was written against, the values it read, the branch it took, and who approved the logic before it went live - stays in your own database, under your own retention policies, for as long as you choose to keep it.

This is particularly important in regulated industries where infrastructure predictability and software lifecycle control are critical.

Full Infrastructure Ownership

Code Effects executes entirely inside your environment. The platform does not require:

  • hosted rule storage
  • vendor-managed evaluation APIs
  • external execution servers
  • cloud-only deployment
  • forced telemetry pipelines
  • remote runtime authorization
  • a separate user directory or sign-in

The Rule Repository and Audit keep rules, versions, tests, activity records and recorded evaluations in a SQL Server or PostgreSQL database that you own, on your own hardware, with Oracle and MySQL support planned. Code Effects provides the database creation and update scripts, and you decide when they run. The Rule Repository runs inside your own web application, on your own sign-in, with the permissions your application assigns to each user.

Perpetual licensing extends this architectural independence.

Organizations retain full control over:

  • deployment topology
  • update schedules
  • security boundaries
  • infrastructure isolation
  • data residency
  • operational uptime
  • AI integrations
  • runtime behavior
  • rule and decision history

Your rules engine remains part of your application stack, not part of somebody else's service infrastructure.

Predictable Economics at Scale

Subscription pricing scales indefinitely. As rule systems expand across products, teams, regions, and environments, recurring operational fees often exceed the original implementation cost many times over.

Perpetual licensing changes the financial model from continuous operational expense to long-term infrastructure investment.

  • predictable budgeting
  • lower long-term TCO
  • simpler procurement
  • reduced operational exposure
  • no runtime metering concerns
  • no evaluation-based billing
  • no per-developer or per-machine fees as teams and deployments grow
  • no AI request taxation by the platform itself

This becomes especially important in high-volume rule evaluation environments where decision execution occurs continuously across large datasets or transactional systems, and in organizations where the number of people and AI agents working with rules keeps growing.

Implementation cost is predictable as well. With the Rule Repository, a production-ready rule management system typically takes one developer 3 to 4 days, plus 1 to 2 days of testing, instead of the months a team would spend building storage, versioning, approvals and testing of its own. See Code Effects Implementation.

AI Without a Gateway Subscription

Version 6 introduced Adaptive Source and Prompt-enabled rule elements for integrating AI into deterministic decision automation. Version 7 brings AI into the entire decision lifecycle: the AI Rule Editor and AI Assistant of the Rule Repository write, change, explain and test rules and answer questions about rules, recorded decisions and user activity, while the MCP server lets the AI clients your people already use work with your rules under your own OAuth sign-in.

All of these features use the models your application registers, with your own API keys. Any model that supports tool calling can be used, and Anthropic's Claude and OpenAI's GPT models have been tested. The Assistant reports token usage and cost for each conversation, so AI spending stays visible and remains between you and the provider you chose. Perpetual licensing keeps it that way. Your AI strategy remains under your control:

  • your models
  • your API keys
  • your prompts
  • your inference infrastructure
  • your security boundaries
  • your execution policies
  • your approval of every change AI proposes

AI agents and services can never delete, approve, take a rule live or take it offline, even if granted those permissions by mistake, and every rule an AI saves waits for a person's approval. The rules engine does not become a gateway subscription standing between your application and your AI stack, and AI does not become a way around your decision workflow.

Deployment Flexibility

Many enterprise environments cannot rely entirely on externally managed SaaS infrastructure. This includes:

  • government systems
  • defense contractors
  • healthcare environments
  • financial institutions
  • industrial automation
  • air-gapped environments
  • hybrid cloud deployments
  • highly regulated infrastructures

Perpetual licensing allows Code Effects to operate as a permanent internal platform component regardless of deployment topology. The Rule Engine and the Rule Editor run on Windows, Linux and macOS, in containers and in the cloud, and the Rule Repository and Audit run in your own ASP.NET Core or ASP.NET application.

Applications can continue functioning even in fully isolated environments with no dependency on external licensing validation or cloud availability.

Protection Against Vendor Drift

Subscription platforms evolve according to vendor priorities. Perpetual licensing reduces exposure to these risks. Organizations maintain operational continuity independently of future commercial or strategic decisions made by the vendor.

For long-lived enterprise systems, this stability is often more valuable than short-term subscription flexibility.

Rule XML adds a further layer of protection. Every rule is stored as a complete, portable Rule XML document that is evaluated the same way wherever it runs, and every saved rule is structurally valid against its source object, whoever or whatever wrote it. Your business logic remains readable, documented data in your own storage, not a proprietary artifact locked inside a hosted service.

Code Effects was designed around the idea that decision automation should become part of enterprise infrastructure rather than a continuously rented external capability. The platform executes inside your systems, against your objects, under your security model, using your deployment architecture. Perpetual licensing extends that same philosophy to ownership itself.

Source Code Ownership

Some organizations need to own more than the right to run the software. Code Effects Source is a perpetual source code package for organizations that require maximum control over their decision infrastructure. With the source code, engineering teams can:

  • audit implementation details
  • compile the platform internally
  • apply internal security policies to the build process
  • align builds with enterprise deployment standards
  • maintain independent internal builds for the life of their systems

Code Effects Source covers the entire platform, including the Rule Repository, Audit and the MCP server, and permits its use across the whole organization.

This keeps licensing aligned with ownership rather than with operational fees for using the platform. As a result, organizations retain the flexibility to choose the licensing model that best matches their deployment strategy, business model, and infrastructure ownership requirements. See Code Effects Packages for details.

l102

p101

×