A fully developed court case management system, licensed as source code
License the source code for a complete court case management platform, then adapt it around your rules, your workflows, and your long-term technology strategy.
The Problem
Legacy software no longer meets the needs of modern courts
Off-the-shelf court management systems have not kept pace with complex court environments. That leaves large jurisdictions stuck between two expensive paths:
Build from scratch
Fund years of custom development, rediscover every rule the old system already knew, and carry the risk that the project stalls before it ever replaces anything. Large court system builds have a long public record of running over budget, running late, or being abandoned outright.
Buy and customize
License a commercial product you will never own, then pay the vendor again to fix it again and again. Every statute change, local rule and new interface becomes a change order. The roadmap belongs to someone else, and so does the code.
A better way forward
A fully developed court case management system, licensed as source code
CPM creates a better opportunity. Your organization licenses a fully developed case management system together with the source code needed to understand, modify, extend, and modernize it. Begin with CPM as delivered, adapt it with an internal team, engage development partners of your choosing, or use it as the foundation for a broader jurisdiction-owned platform.
CPM is offered to courts and justice agencies under a source code license. Your jurisdiction receives the complete application and the source code behind it — not a hosted subscription, not a locked binary, and not a one-year customization budget.
What you do with it next is your decision:
Run it as delivered. Configure CPM to your case types, rules, fees, and workflows and go live on a proven foundation.
Adapt it. Modify screens, rules, integrations, and data structures with your own developers or a partner you choose.
Build on it. Use CPM as the starting point for a jurisdiction-owned platform and modernize it on your own terms.
With this model, your court gets:
Full code control. Modify and adapt the software to your specific needs, any time, without asking permission or waiting for a vendor release.
A Mature Platform
Case management, workflow, scheduling, financials, documents, integrations, and public access without beginning from zero.
Full Code Control
Modify and adapt the software to your specific needs, any time, without asking permission or waiting for a vendor release.
Rapid Deployment
Implement a complete system in a fraction of the time a greenfield build requires, because the core is already written and already works.
Massive Cost Savings
Avoid millions in custom development and years of ongoing vendor customization fees.
Freedom to Choose
Staff it internally, hire a systems integrator, or combine both. No single vendor is required to change your system.
Your Roadmap
You decide what gets built, in what order, and when it ships.
Control the roadmap
Move from vendor dependence to product stewardship
A source code license changes who determines what happens next.
Control your priorities
01
Plan releases around statutory changes, operational needs, security requirements, and the work that matters most to your court.
Choose your team
02
Use internal developers, approved contractors, a systems integrator, or a blended team.
Modernize in phases
03
Improve components at the pace your risk tolerance, budget, and operational calendar allow.
Protect solved logic
04
Preserve established data relationships, workflow behavior, and exception handling while the technology evolves.
Reduce vendor friction
05
Stop treating every local requirement as a customization request and every release as a dependency.
Build institutional capacity
06
Keep technical knowledge, documentation, governance, and release practices inside the organization.
A clear boundary
Source access is not the same as an unrestricted transfer of intellectual property. Exact rights, restrictions, term, deliverables, contractor access, and support obligations belong in the negotiated license agreement.
Built for capable institutions
For jurisdictions ready to govern their own platform.
This model is designed for courts and justice agencies with the scale, technical resources, procurement flexibility, and long-term commitment to manage a mission-critical system.
-
Large or operationally complex jurisdictions.
-
Internal application teams or qualified integration partners.
-
Substantial local requirements that conventional products cannot meet economically.
-
A need for direct control over releases, integrations, and infrastructure.
-
Product ownership, security review, testing, and change governance.
-
A custom-build ambition without the appetite to start from zero.
-
Multiple divisions, case types, and connected justice organizations.
-
A long-term commitment to sustaining an institutional platform.
A complete foundation
Not a framework. Not a prototype. A working court system.
Cases, people, events, documents, financials, tasks, and decisions stay connected in one browser-based environment and one relational data model.
Case & Identity
Case initiation through disposition. Parties, staff, attorneys, judges, affiliations, histories and relationships, with configurable case types and numbering.
Financial Management
Chart of accounts, general ledger, receipts, obligations, distributions, payments, deposits, restitution and financial reporting — inside the case, not in a separate ledger.
Workflow & Scheduling
Automatic and manual scheduling across judges, courtrooms, staff, attorneys, interpreters, reporters and resources, with relationship-based conflict checking and date logic.
Documents & Forms
Capture and ingestion, manual, automatic and barcode indexing, OCR, metadata search, versions, check-in and check-out, annotations, signatures, redaction and retention schedules.
Reporting & Metrics
Library and configurable reports run on demand, in the background, on a schedule or on a recurrence, with email distribution, an archive and PDF, RTF and spreadsheet-friendly output.
Probation & Supervision
Conditions, contact standards, supervision levels, violations, criminal history, restitution and bond-release obligations, seeded from existing court or prosecutor records.
Architecture
A layered approach
CPM is an n-tier justice system built in three layers. The user interface is presented in a web browser and is separate from the application logic and transactional core that holds the data.
Developers can update one part of the code without breaking the other parts. Each individual tier has a specific job and can run on separate servers.
Layered by design. Presentation can be modernized without rewriting business logic or data. Security and audit span every layer rather than sitting at the front door.
The Workbench
Built around the next action, not the next menu
The measure of a case system is not how much it can display. It is how few decisions a user has to make between opening it and doing the work.
Personalized
Saved searches and layouts follow the user across workstations.
Context-rich
Tabs, collapsible panels and detachable views keep dense case information close.
Responsive
Partial screen updates improve responsiveness without full-page reloads.
Directed
Task notifications take users straight to the required work context, not to a list that contains it.
Process automation without losing human judgment
Routine work moves automatically. Exceptions stay visible to the people accountable for resolving them.
Configuration
Configuration... not code
Authorized administrators can adapt navigation, data elements, screens, work queues, reports, financial distributions and business rules. New entities and fields can extend baseline tables, and relationships can be configured to reflect local information requirements.
This does not mean every change is free of design, testing or governance. It means most changes move out of a software development queue and into a controlled configuration process — shorter elapsed time, and a core codebase that stays stable.
Where the line sits
Configuration covers screens, fields, rules, queues, notices, distributions and reports. Anything that changes how the platform itself behaves — a new integration pattern, a new financial calculation model — is development work.
Trust and Governance
Security is enforced through the system technical stack
A unified system reduces the number of integration seams that must be secured, patched, monitored and trusted. CPM then layers controls inside the product and the database.
Security and Audits
-
TLS/HTTPS protects data in transit.
-
Oracle Database encryption, or Amazon RDS for Oracle controls in an AWS deployment, protects data at rest.
-
Audit logs record user identity, time, location and created or modified information; case workflow adds a process-level history.
-
Automatic and manual redaction can protect sensitive information while authorized roles retain access to the underlying record.
-
CPM can authenticate against Active Directory or LDAP.
-
True single sign-on and multi-factor authentication are not enabled by default; they are implemented through deployment architecture.
Interoperability
Standards-ready where possible, legacy-capable where necessary
Justice ecosystems are mixed by definition. Statewide networks, criminal identification systems, motor-vehicle bureaus, payment services and legacy applications often coexist for years.
Know what you are buying
A mature core with clear modernization boundaries
CPM separates the browser experience, justice-domain services, and relational system of record so the system can evolve to meet future needs without starting over.
01 / Presentation
Browser workbench
Role-specific case work, searches, queues, administrative screens, and a modern public portal.
02 / Application
Justice-domain services
Case, workflow, scheduling, financial, configuration, integration, and security behavior.
03 / Data + Controls
Relational system of record
Oracle records, referential integrity, views, procedures, and database-level controls.
Components and Technical Baseline
Database
Oracle Database
A mature transactional foundation. Licensing, support lifecycle, and cloud portability can be modeled to meet your specific needs.
Application Server
Oracle WebLogic
An established enterprise runtime. A mature, enterprise application server that scales to meet any workload.
Java Runtime
OpenJDK / Oracle JDK
Java Development Kit. Combines everything required to build modern enterprise software.
Development Framework
Oracle ADF
Application Development Framework. A commercial, framework that accelerates enterprise application development.
Public Access
Node.js / React (LTS)
A contemporary constituent-facing surface that evolves independently of the core.
Deployment
On-prem, Cloud, Hybrid
Infrastructure aligned to meet virtually any jurisdiction’s responsibility and deployment models.
Modernization
Source access facilitates modernization. It makes the baseline inspectable and gives the licensee the ability to prioritize and execute a modernization plan.
Reporting & Analytics
Court and operations reporting with JasperReports
Courts are asked for numbers by legislatures, constituents, the press, and their own administrators, usually at short notice and rarely in the consistent formats.
We build court reporting on JasperReports — an established, vendor-neutral reporting platform that works with virtually any database and scales from a single division to a statewide deployment. That neutrality is the point: the reports you commission are not locked to us.
What we deliver
-
Contract-based custom report development, working directly with court staff and your IT team.
-
Secure connection to your existing case management database — CPM or otherwise.
-
Reports designed around court workflows and statutory requirements, not around the shape of the data.
-
Reports your own staff can maintain and extend afterwards.
Delivery and control
-
Web-based access to reports and dashboards, with scheduled delivery by email or secure portal.
-
Interactive drill-down, filtering and charting, with guided parameters so output stays consistent.
-
Role-based access control, field-level data security, and auditing of report access and usage.
-
Output as HTML, PDF, Excel, CSV, RTF, TXT and XML.
-
On-premises, cloud or hybrid deployment.
The reason to care
Reports that a court cannot produce quickly only introduce additional budgetary and operational concerns.
Boundary
Reports read — they do not correct the underlying data. If the operational data is wrong, a report makes that visible faster, which is valuable and occasionally uncomfortable.
With our reporting tools, locate and address data issues before they're a problem.
CPM Public Portal
Public information without a second system of record
A modern, responsive court-record search experience reads the court’s Oracle data through a deliberately restricted, read-only path.
CPM Public Access has been modernized from the ground up: same court data, same database, same restricted read-only account the legacy site used.
One door to the data. Every read passes through a single restricted identity and a curated set of read-only views. There is no second connection and no back door to the raw tables.
Six public workflows designed to meet the needs of the public
Every public portal screen is bookmarkable and shareable, the back button works, and nothing hides behind a pop-up standing in for a page.
Search by case number
The fastest path. Someone who already has a case number reaches the full record in one step.
Search by name
Person or business, with prefix matching on the last name and a required first initial — a deliberate anti-scraping rule, not an oversight. Results are grouped one row per case with the parties listed beneath.
Search by case type
One or more case types across a required file-date range. The date range is a guard: it stops a single query from scanning every felony ever filed.
Attorney case list
The cases an attorney appears on and whom they represent, each linking through to the case record.
Court Calendar
Every scheduled event in a date window, with Today, Tomorrow and Next 7 Days shortcuts. The maximum span is capped and configurable per deployment — a load control, not a picker hint.
Download your results
CSV, XML, spreadsheet and a print-ready PDF of the same list you are looking at. Exports are capped, and a search too broad to export gets a polite refusal rather than a giant file.
Frequently Asked Questions
What are the boundaries?
CPM is presented here as a source code license, not an outright assignment of all intellectual property. The agreement should define the jurisdiction’s possession, use, modification, operation, and maintenance rights.
No resale or redistribution right is implied. The working model supports the jurisdiction’s own authorized use and development, subject to the signed agreement and sensible provisions for approved contractors and government relationships.
That is a central advantage of the proposed model, subject to confidentiality, security, access, and contractor provisions. A partner should not receive independent rights to the software.
They should not be assumed. Documentation, transition assistance, implementation support, maintenance, knowledge transfer, and advisory services can be defined separately.
No. CPM has a mature enterprise Java and Oracle core. It can run on premises, in AWS-hosted arrangements, or in a hybrid model, with source access supporting a controlled modernization path.