Environment-Agnostic Decision Automation
Modern enterprise systems no longer operate within a single runtime, operating system, or deployment model. Decision automation infrastructure must be capable of operating consistently across all environments without forcing platform-specific rewrites, external service dependencies, or fragmented rule architectures.
Code Effects was designed specifically for this reality.
Built on .NET Standard 2.0, it supports deployment across all platforms on any compatible .NET runtime while preserving a single rule model, a single execution architecture, and a unified development approach. This provides broad compatibility across the .NET ecosystem, including:
- .NET Framework
- modern .NET
- ASP.NET
- ASP.NET Core
- Windows services
- Linux services
- Windows and macOS desktop applications
- containerized workloads
- cloud deployments
- iOS apps
- Android apps
- mobile and edge runtimes
As a result, organizations can deploy the same decision automation infrastructure across both modern and legacy systems without maintaining separate rule engines or incompatible rule definitions. Business rules remain portable across environments: every rule is stored as a complete Rule XML document, and the same document is evaluated the same way wherever it runs. The deployment model can evolve independently of the rule architecture itself.
The Rule Engine and Rule Editor target .NET Standard 2.0, which covers .NET Framework 4.6.2+ and .NET Core 2.0+, including .NET 8+, on Windows, Linux and macOS. The Rule Repository and Audit, added in version 7, run in ASP.NET Core or in ASP.NET on .NET Framework 4.7.2+, with SQL Server 2012+ or PostgreSQL 14+ and with Oracle and MySQL support planned for upcoming minor versions, and the MCP server runs in ASP.NET Core on .NET 8+.
Any Web Application, Any Front End
The Rule Editor runs in any .NET web application and in all current browsers. It works with:
- ASP.NET Core
- MVC
- Razor Pages
- Blazor
- WebForms
- React, Angular and Vue
- plain pages
The browser components are delivered as two dependency-free npm packages built on modern JavaScript modules: @codeeffects/editor for every application, and @codeeffects/repository for applications that use the Rule Repository. The Rule Repository places a complete rule management application in one element of your page, with light and dark themes, fonts inherited from your page, and layouts that adjust to tablets and phones. Neither package adds a framework of its own to your front end.
Supporting Both Legacy and Modern Architectures
Most enterprise organizations operate a combination of old and new infrastructure. Critical operational systems often remain on older frameworks for years due to:
- regulatory validation
- operational stability
- migration risk
- integration complexity
- long lifecycle requirements
At the same time, newer systems increasingly target:
- modern .NET runtimes
- Linux containers
- Kubernetes orchestration
- distributed cloud architectures
- mobile platforms
- edge execution environments
Code Effects allows these environments to coexist within a single decision infrastructure. This significantly simplifies long-term architectural evolution and operational maintenance.
Version 7 keeps that promise for rule management too. The Rule Repository and Audit run on .NET Framework 4.7.2 and later as well as in ASP.NET Core, so an organization can add versions, approvals, testing and decision explainability to an established ASP.NET application without first migrating it to a new runtime. Version 6 rule, interface and source documents remain readable, so existing rules move forward with the platform.
One Rule Model, Two Ways to Run It
Code Effects can be implemented in two ways, and both use the same source objects, the same rules, the same Rule XML and the same engine:
- Stand-alone - the Rule Editor and the Rule Engine, with your own storage in any database, file system or service. This fits desktop, mobile and embedded products with no web application to host rule management, and screens of your own design.
- With the Rule Repository - a complete rule management application inside your own web application, with optional Audit and MCP server. Your production applications load the live versions of their rules, together with the rules they depend on, as a complete ruleset ready for evaluation.
Organizations can start with one and move to the other, or use both in different systems, without changing how rules are written or evaluated. See Code Effects Implementation for the components, their packages and the estimated time to production.
Local Decision Execution on Mobile and Edge Platforms
Certain operational workflows increasingly execute outside traditional server infrastructure. Examples include:
- mobile validation systems
- field-service applications
- offline operational workflows
- industrial edge systems
- disconnected environments
- client-side automation
- local compliance validation
Because Code Effects targets .NET Standard 2.0, the engine can execute directly inside compatible iOS and Android runtimes in addition to desktop and server environments. This enables organizations to execute business rules locally on devices without depending on continuous connectivity to external rule-processing services. The engine is stateless and thread-safe, and compiles each rule once into IL, so the same rule runs at the speed of compiled code on a server, a desktop or a device.
Coming to Java in 2027
Many organizations run decision logic on more than one technology stack. The entire Code Effects platform - the Rule Editor, the Rule Engine, the Rule Repository, Audit and the MCP server - is planned to be introduced on the Java platform in 2027.
Until then, Code Effects is a .NET platform, and .NET Standard 2.0 continues to provide the broadest reach across Windows, Linux, macOS, containers, cloud and mobile runtimes.
Source Code Licensing and Maximum Deployment Freedom
Code Effects also offers a perpetual source code package for organizations that require maximum infrastructure ownership and deployment flexibility: Code Effects Source, with the source code of the entire platform, for use across the whole organization.
While standard assemblies are sufficient for most deployment scenarios, source code licenses provide organizations with complete control over how the platform is compiled, optimized, integrated, deployed, and maintained across different environments. Having this license, engineering teams can:
- compile the engine internally
- optimize builds for specific runtimes
- customize deployment behavior
- integrate internal tooling
- audit implementation details
- apply internal security policies
- align builds with enterprise deployment standards
- maintain independent internal builds
- adapt the engine to specialized deployment environments
This level of control becomes especially valuable in environments involving:
- Linux container optimization
- highly specialized infrastructure
- regulated enterprise systems
- performance-sensitive deployments
- proprietary internal platforms
- mobile runtime customization
- long-term internal maintenance requirements
The availability of source code licenses ensures that organizations are not limited by vendor-controlled binaries when designing long-term deployment strategies across Windows, Linux, macOS, iOS, Android, cloud, edge, or hybrid infrastructures.
Licensing That Follows Your Infrastructure
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 requires a perpetual Code Effects package: Code Effects Standard for the Rule Engine and the Rule Editor, or Business, Enterprise or Ultimate when you need the Rule Repository, Audit and the MCP server. There are no per-evaluation, per-device or usage fees, so extending decision automation to new environments does not add metered costs. Code Effects can be deployed in:
- internal enterprise systems
- SaaS platforms
- mobile apps
- containerized solutions
- cloud-native infrastructures
- on-premises and air-gapped environments
- hybrid infrastructures
This model allows organizations to maintain complete ownership of both their product architecture and their deployment strategy while preserving long-term independence from vendor-controlled hosting or execution models.
The result is a decision automation platform that can evolve alongside the organization’s own infrastructure, business model, and distribution strategy rather than constraining them.