About Jube

Jube is open-source transaction and event monitoring software. Jube implements real-time data wrangling, artificial intelligence, decision making and case management. Jube is particularly strong when implemented in fraud and abuse detection use cases.

Data wrangling is real-time. Data wrangling is directed via a series of rules created using either a point-and-click rule builder or an intuitive rule coder. Rules are in-memory matching functions tested against data returned from high-performance cache tables, where datasets are fetched only once for each key that the rules roll up to for each transaction or event processing, with the matches aggregating using a variety of functions. Alternative means of maintaining a lightweight long-term state to facilitate data wrangling is Time To Live (TTL) Counters which are incremented on rule match and then decremented for that incrementation on time-lapse.

Data wrangling return values are independently available for use as features in artificial intelligence training and real-time recall or tested by rules to perform a specific action (e.g., the rejection of a transaction or event). Wrangled values are returned in the real-time response payload and can facilitate a Function as a Service (FaaS) pattern. Response payload data is also stored in an addressable fashion, improving the experience of advanced analytical reporting while also reducing database resource \ compute cost.

Jube is developed stateless and can support massive horizontal scalability and separation of concerns in the infrastructure.

Jube takes a novel approach to artificial intelligence, ultimately Supervised Learning, yet blending anomaly detection with confirmed class data to ensure datasets of sufficient amounts of class data. Using data archived from its processing, Jube searches for optimal input variables, hidden layers and processing elements. The result is small, optimal, generalised and computationally inexpensive models for efficient real-time recall. The approach taken by Jube allows artificial intelligence’s benefits to be available very early in an implementation’s lifecycle. It avoids over-fitting models to typology long since passed.

Transaction or event monitoring overlooks the embedding in human-engaging business processes. Jube is real-time, but this does not forgo the need for manual intervention; hence Jube makes comprehensive and highly customisable case management and visualisation intrinsically available in the user interface.

To ensure the segregation of user responsibilities, a user, role and permission model is in place, which controls access to each page within the Jube user interface. Detailed audit logs are available. Any update to a configuration by a user retains a version history, in which the original is logically deleted and then replaced with the new version.

Jube is multi-tenanted, allowing a single infrastructure to be shared among many logically isolated entities, maintaining total isolation between tenant data with no loss of function in the user interface.

Stargazing

Please consider giving the project a GitHub Star. Thank you in advance!

Quickstart

Jube runs on commodity Linux. The Quickstart has the following prerequisites:

.Net 8 Runtime.
Postgres database version 13 onwards (tested on 15.4 but no significant database development to cause a breaking change).
Optional but recommended: Redis version 6 or above (it probably works fine on earlier versions, as the command used are basic. RESP wire compatible implies that it is possible to use KeyDB, DragonflyDB, Garnet or any RESP compliant wire protocol database).

Subject to prerequisites, Jube can be up and running in minutes:

git clone https://github.com/jube-home/jube.git
cd jube/Jube.App
export ConnectionString="Host=<host>;Port=<port>;Database=<defaultdb>;Username=<username>;Password=<password>;Pooling=true;Minimum Pool Size=0;Maximum Pool Size=100;SSL Mode=Require;Trust Server Certificate=true;"
export RedisConnectionString="<host>"
export ASPNETCORE_URLS="https://localhost:5001"
export JWTKey="IMPORTANT:_ChangeThisKey_~%pvif3KRo!3Mk|1oMC50TvAPi%{mUt<9"B&|>DP|GZy"YYWeVrNUqLQE}mz{L_UsingThisKeyIsDangerous"
dotnet run

For security, there is no means to pass configuration values via anything other than Environment Variables, and the contents of those Environment Variables are never - ever - stored by Jube (which is something the CodeQL security scanner tests for).

The use of Redis is encouraged as it provides a 33% improvement in response times, and a marked improvement in response time variance contrasted against using Postgres Database. Redis also does not require Cache table indexing jobs, and while such indexing is automatic on existing data for Postgres, it does create some delay in the creation of Search Keys retroactively, however by contrast Search Keys in Redis can only be created on a forward only basis and there is no preexisting data. In general the trade of between Key \ Value Pair in-memory databases and RDMBS durable databases is not trivial. In general, the use of Postgres Database is probably the right choice for low volume or cost sensitive implementations where the staff and infrastructure complexity costs can’t be justified, whereas for any serious real-time implementation given infrastructure technical capacity, doubtless Redis is the better choice. Setting the Redis Environment Variable to false will fall back to using the Postgres Database for cache, and is the more simple implementation:

export Redis="False"

There are sensitive cryptographic values that need to be included at startup. At a minimum the JWTKey value is required:

export JWTKey="IMPORTANT:_ChangeThisKey_~%pvif3KRo!3Mk|1oMC50TvAPi%{mUt<9"B&|>DP|GZy"YYWeVrNUqLQE}mz{L_UsingThisKeyIsDangerous"

The JWTKey value is used to encrypt access tokens providing for API authentication, and therefore user interface authentication.

While outside of the scope of this installation documentation, other sensitive variables, while optional, are strongly suggested:

export PasswordHashingKey="IMPORTANT:_ChangeThisKey_~%pvif3KRo!3Mk|1oMC50TvAPi%{mUt<9"B&|>DP|GZy"YYWeVrNUqLQE}mz{L_UsingThisKeyIsDangerous"

It is imperative that the keys be changed from their defaults and kept safe in appropriate storage. Jube will not start if the keys above are used.

Change the template value for setting the ConnectionString and JWTKey Environment Variables, then run the shell script as above. Wait for the build to complete, after which observe the welcome message.

Waiting a few moments more will ensure that the embedded Kestrel web server is started correctly. In a web browser, navigate to the bound URL https://localhost:5001/ as per the ASPNETCORE_URLS Environment Variable.

The default user name \ password combination is Administrator \ Administrator, although the password will be need to be changed on first login.

A more comprehensive installation guide is available in the Getting Started of the documentation.

Roadmap

The product roadmap spanning 2025 and 2026 involves modernisation and optimisation of the software and general preparation for the presentation of cloud cum managed services, planned for the start of 2026. Cloud means working towards a proposition that provides for a generous free tier given shared infrastructure, or if paid, dedicated infrastructure. In the midst, mindful that Jube already has supervised learning for transaction analysis, Phi Language models will be included in the case management pages for summarization, developed as part of other modernisation efforts.

The following table lays out the product Roadmap through April 2026:

Milestone	Description	Delivery
.Net 9	Upgrade to .Net 9.	December 2024
Git Version Control	Implement file based representation of the database in Git and allow for recovery and replay of changes.	June 2025
Modernisation	Upgrading the user interface to Blazor and Radzen tooling. Essentially a total rewrite of the User Interface and the porting of functionality out of controllers into Service Layers. Existing controllers will be supported in their current form, although Blazor will not use REST (JSON over HTTP), rather go directly to Service Layers. Possible upgrade of LINQ2DB layer.	October 2025
Phi	Implementation of Case Management Summarization using Phi.	November 2025
Unit Testing and Code Optimization	The inclusion of unit tests across all critical transaction processing functionality. To the extent critical transaction processing functionality is too larger or complex, it will be refactored. Optimisations sought in all units through benchmarking and trials.	November 2025
Transaction Serialisation	Explore improvements in transaction processing by removing the JSON and serialization overhead and using a byte representation over gRPC.	December 2025
Cloud Portal	The creation of a portal to allow for self service management of distributed and highly available implementations of Jube using containerisation. Intention is to offer a free edition of Jube using shared infrastructure, or paid for given dedicated infrastructure	April 2026

Documentation

The documentation has been drafted to include all features, and there should not be any undocumented know-how. The documentation adopts an instructional style that will explain most features step-by-step with extensive use of screenshots.

Jube is committed to high-quality instructional documentation and maintains it as part of the overall release methodology. If documentation is inadequate, unclear or missing, raise a Github Issue.

Training

The Jube user profile is technically proficient in reading, building and running code.

Jube currently makes a single commercial offer in the form of a training program that focuses on achieving proficiency in the effective implementation and utilization of Jube. Training returns a significant acceleration in the implementation of Jube in an organisation, while assuring its success.

The schedule covers a duration of three days, with the length of each day ranging from 6 to 8 hours, depending on the undertaking of Elective Modules. Elective Modules cover in-depth training in advanced administrative concepts using dedicated training servers. Elective Modules are targeted at technical participants whom are likely to assume overall system administrative responsibility of an implementation of Jube.

Day 1:

Introduction.
User Interface.
HTTP Messaging.
Models and Payload.
Inline Functions.
Abstraction Rules.
Abstraction Calculations.
Lists and Dictionaries.
Activation Rules.
Elective: Architecture and Caching.
Elective: Environment Variables.
Elective: Installation and Log Configuration.

Day 2:

Suppression.
Sanctions Fuzzy Matching.
Time To Live (TTL) Counters.
Introduction to Artificial Intelligence (AI).
Exhaustive AI training.
Case Management.
Security.
Elective: Tracing Transaction Flow and Response Time Analysis.
Elective: High Availability.
Elective: Performance Counters.
Elective: AMQP.

Day 3:

SQL database discovery.
Performance Monitoring.
Visualisation and Reporting.
Inline Scripts.
Scores via R Plumber (HTTP).
Elective: Cache Bottleneck Analysis.
Elective: Archive Bottleneck Analysis.
Elective: Multi-Tenancy.

Delivered at client site or venue, globally. Fee of USD 3600, excluding travel and expenses. For further details, including the detailed training plan, kindly contact support@jube.io.

Support

The free support offer is available via Github Issues and is on a best endeavour basis.

Reporting Vulnerabilities

Please do not file GitHub issues for security vulnerabilities, as they are public.

Jube takes security issues very seriously. If you have any concerns about Jube or believe you have uncovered a vulnerability, please contact via the e-mail address security@jube.io. In the message, try to describe the issue and, ideally, a way of reproducing it.

Please report any security problems to Jube before disclosing them publicly.

Governance

Jube Holdings Limited is a Cyprus company registered HE404521. Jube Holdings Limited owns Jube software and Trademarks ( registered or otherwise). Jube is maintained by Jube Operations Limited, a United Kingdom company with registration

Jube Operations Limited is a wholly owned subsidiary of Jube Holdings Limited. Jube Operations Limited provides training and support services for Jube. Jube and “Jooby” (the logo) is a registered trademark in Cyprus.

Licence

Jube is distributed under AGPL-3.0-or-later.