Jube Support

Jube is open source and free to use. Implementation and training engagements are fixed fee. Ongoing support is available in two arrangements — retained support and Enterprise — with advanced analytics consulting available under either, and larger defined tasks handled as fixed-scope project engagements, each under its own Work Order. All operate on the same business model: retained professional service hours, with a fair-use, no-overage commitment. The monthly amount is known in advance, and there is no bill shock by design.

This page is the offer. Rates, response commitments, inclusions, and governance are published here in full. Engagement proceeds directly to a quote which references this page (see From this page to a signed engagement below).

Jube Training

How support works

Support is delivered async-first — day-to-day via WhatsApp Business, with screencasts and voice notes preferred over scheduled calls. Meetings are available but treated as a last resort.

All client support runs through a single, transparent system. Issues are raised directly via WhatsApp and tracked in real time against a permanent record — every note, time entry, and status change captured once and traceable from start to finish. Most generally: a WhatsApp message becomes a ticket, responded to with a Loom video and links to documentation. Clients can request a full digest of open issues and progress at any time, including an AI-generated summary of status and suggested next steps.

The business model is retained professional service hours, with a fair-use, no-overage commitment. The monthly amount is agreed in advance, invoiced monthly in arrears as provided for in the JTOS, and — within fair use — is the amount invoiced, full stop. Professional services billing typically makes its margin in the overage, which is exactly where bill shock lives; this model removes the category.

Fair use has a published number attached to it rather than being left to judgement. Recorded hours are within fair use up to one and a half times the committed hours in a month, and are covered by the retained amount. Above that threshold the excess may be invoiced at the engaged hourly rate — but never silently: where it becomes apparent during a month that recorded hours are heading past it, you are told while there is still time to decide how you want to proceed. In practice sustained variance is dealt with by moving the commitment at the quarterly review rather than by invoicing the month.

Time is still recorded against every piece of work as it happens, and is fully auditable — but it exists to demonstrate fairness, not to generate charges. Recorded time feeds a quarterly account management review, where the retained rate is checked against sustained reality and adjusted, in either direction, prospectively and in the open. No prepayment, no blocks to buy in advance, no unused-hours administration, and no surprises at invoice time.

These rates should not be mistaken for cheapness. The margin on time is not radically different from a proprietary vendor’s — what differs is the cost base. Jube maintains a ruthlessly low one, and a strict, highly efficient async-first support model; the absurd overheads that proprietary vendors carry, and pass on, have been cut clean out. What you are paying for is the time of the person who wrote the platform, and very little else.

Retained support is terminable on thirty days’ notice, by either party, at any time, as set out in the JTOS. Long notice periods exist to keep clients who would rather leave. Support billed monthly in arrears has to earn its keep every month, and is retained because it is useful — not because a contract compels it.

Enterprise is the single exception, and the reason is worth stating plainly. Enterprise carries a twelve-month initial term to which both sides are equally committed — Jube cannot walk away inside the year any more than you can. What Enterprise sells is a year of maintained availability: the callout coverage, the patching response, the regulatory mapping, and a working knowledge of your implementation that stays current. None of that can be honestly promised on a thirty-day footing. After the initial term Enterprise continues month to month on the same thirty days’ notice as everything else.

Retained support

Retained support operates on committed professional service hours against a single published rate card. By the end of the training and integration programme, both sides have a very good understanding of what support the client’s environment actually demands, and a commitment is set broadly in keeping with that expected demand — billed monthly in arrears, under the fair-use, no-overage commitment described above.

The rate card is graduated as an exponential derate: no commitment earns no keen price, the discount is front-loaded as commitment begins, and the curve flattens onto a floor. It is published so that it is the same for every client — the rate is a function of commitment, not of negotiation. All rates are in United States dollars:

Committed hours per month	Hourly rate	Retained monthly amount
None (ad hoc)	$150	billed as used, one hour a month minimum
5	$125	$625
10	$114	$1,140
15	$106	$1,590
20	$100	$2,000
25 (Enterprise)	$96 (floor)	$2,400

Fixed-scope project engagements — the training and integration programme among them — are billed at the project rate of $125 per hour, matching the first committed rung: a project carries scope commitment, but not the ongoing commitment that earns the keener retained rates.

It is worth being explicit about what earns the keener rates on this card, because the answer is narrower than it first appears. The derate is bought by ongoing commitment — a monthly amount, sustained over time, that makes a portion of Jube’s capacity reliably spoken for. That is genuinely worth something: it removes the need to go and find the work, it smooths the year, and it is the reason the rate can come down at all. What is being priced is the commitment itself, not the number of hours attached to it.

Which means that a large piece of work does not, on its own, earn a keener rate. A hundred hours inside a single fixed-scope project is not the same proposition as a hundred hours committed across a year of months, however similar the arithmetic looks: the project ends, and the capacity it occupied goes back to being unspoken for. Fixed-scope projects are charged at the project rate accordingly, whatever their size.

The same reasoning applies to work delivered at your premises, including the on-site month within the training and integration programme. On-site work is charged at the project rate — no premium for the location, and no discount for the quantity of hours involved. If anything the case runs the other way, since travelling to you consumes a month of capacity outright rather than guaranteeing it, and a card that made the most demanding engagement the cheapest one per hour would be difficult to defend and harder still to sustain. So on-site work is not derated. It seems better to say where that line falls here than to leave it to be discovered halfway through a quote.

Commitments are set at the nearest rung to evidenced demand, and revisited at the quarterly account management review — moved up or down the same published card, prospectively and in the open. Within an Enterprise initial term the commitment does not move below the top rung, because that rung is what Enterprise is; a client whose sustained demand settles lower can move to retained support at the end of the term. $96 an hour is the floor of the card. Holding it matters more than winning any single engagement: a rate that moves under pressure is not really a published rate at all, and part of what this page offers is the assurance that the number you are given is the number everyone else is given.

Enterprise is the top rung of the same card rather than a separate product: twenty-five committed hours a month at the floor rate. There is no separate Enterprise price to reconcile against the scale, and no point at which the scale overtakes it — the card simply ends where Enterprise begins. The Enterprise inclusions come with that commitment rather than being charged for.

Retained support is a good fit for cost-sensitive markets and clients with modest or variable support needs — the entry rung, five hours a month at $625, is deliberately sized to work in emerging markets. Responses within four business hours during UK office hours, on a best endeavours basis.

Out-of-hours and emergency response is not part of retained support. Where it is provided at all it is at Jube’s discretion and on a best endeavours basis, charged at the ad hoc rate of $150 per hour with a two-hour minimum per callout. Guaranteed out-of-hours coverage is what Enterprise buys, and it is the honest answer to give here rather than an implication left hanging.

Enterprise support

Enterprise support is available at $2,400 per month — $28,800 a year — invoiced monthly in arrears in accordance with the JTOS and under the same fair-use, no-overage commitment, for clients who want a retained relationship, committed availability, and a named technical authority on their implementation. It is committed for a twelve-month initial term, mutually, and continues month to month on thirty days’ notice thereafter.

The price is not set apart from the rate card; it is the top of it. Twenty-five committed hours a month at the floor rate of $96 is $2,400, which is the whole of the calculation. The inclusions below are not priced separately and add nothing to the hourly rate; they are what a commitment at the top of the scale carries with it:

Reference configurations and client context — Jube maintains reference configurations for infrastructure and deployment. Support does not carry sign-off responsibility for the client’s environment — experience is that clients rightly want to do things themselves, and a sign-off gate serves neither party. Instead, material departures from the reference configurations are looked for as they surface in support work, and recorded in client notes to maintain working context, on a best endeavours basis. When something breaks, support starts from a known baseline and a record of where your environment deliberately differs from it.
Security patching and vulnerability management — credible, documented vulnerabilities in the Jube platform addressed through timely patches and releases, prioritised by severity and exploitability.
Regulatory feature mapping — ongoing commitment to ensuring Jube’s tooling supports evolving AML and fraud detection regulatory requirements, conducted on the basis of materials available in English.
Release advisory and support — hands-on guidance through platform upgrades, dependency changes, and infrastructure modifications, conducted against the reference configurations and your recorded departures from them.
Advanced analytics consulting — available within the scope of the relationship where the detection strategy requires it; see below.
24/7 callout coverage — urgent matters raised via WhatsApp Business are interrupt-driven and will be picked up as quickly as practically possible. Response during 06:00–18:00 GMT, Monday to Friday is guaranteed. Outside those hours, coverage is on a best endeavours basis. Callout is included within the retained amount and recorded like any other time; it is not separately invoiced. Sustained callout volume is a quarterly review conversation, not an invoice. Callout is tied to the top rung: if the commitment ever falls below twenty-five hours a month, callout and the other Enterprise inclusions cease from that billing period and the arrangement is retained support.

Project engagements

Some work is too large to sit inside day-to-day support — a major version upgrade, a cluster build, a migration, a substantial integration, or a sustained piece of model development. These are handled as fixed-scope projects, on a project-by-project basis: properly scoped and planned before anything begins, priced at the published project rate of $125 per hour against the scoped estimate, and delivered under a specific Work Order as defined in the JTOS — the training and integration programme itself is delivered on exactly this basis.

Where the line falls is the client’s question rather than Jube’s: retained hours can be spent however the client pleases, and there is no obligation to convert anything into a project. In practice, for the really big pieces of work, clients usually want the commitment — a scoped plan and a known price — and this is where they get it.

The discipline is the point, and it is what extends the no-bill-shock principle to the biggest tasks, where it matters most. A project does not begin until its scope, plan, and price are agreed and recorded in its Work Order; the price is known before the work starts, and it is the Work Order that changes it — never the invoice.

Project engagements are ordinarily delivered remotely, on the same async-first basis as everything else. Where a project genuinely warrants attendance at your premises, that is agreed in advance and recorded in the Work Order, priced at the project rate with no derate for attendance, and with travel and subsistence handled exactly as set out for the on-site month: flights and accommodation booked directly by you, economy class, scheduled within social hours, and subsistence at the published HMRC scale rate. Days spent travelling to you and back are not billed and consume none of the engaged hours.

Advanced analytics consulting

The real value of transaction monitoring is rarely in the platform — it is in the quality of the models running on it. Infrastructure and software keep the system standing; the analytical work is what makes it detect.

This is a consulting offer, not a helpdesk category. Jube works alongside your team on the detection strategy itself — designing, building, validating, and maintaining the models — with training and knowledge transfer woven through the work rather than sold separately. The consulting covers the full lifecycle of detection models, delivered inside a common methodology and lexicon:

Abstraction and feature engineering — the statistical features computed against a customer’s own history and their peers that give raw transactions meaning, set out prescriptively by risk factor in the Jube AML Monitoring Compliance Guidance.
Model development — supervised and unsupervised classification across Logistic Regression, Decision Trees (C5 and Random Forests, whose rule output can be deployed directly as Jube coder rules), Support Vector Machines, Neural Networks including Jube’s Exhaustive topology exploration, and Bayesian Networks — the weapon of choice where causality, explainability, and a walk through the graph are required.
Calibration and validation — well-calibrated probabilities, confusion matrices, ROC and AUC appraisal, and bootstrap arc-strength analysis, anchored to the generally accepted model validation practices of BASEL so that the work product is defensible in front of a regulator.
Deployment — models wrapped for real-time recall over HTTP (R Plumber into Jube’s HTTP Adaptation), separating analytics cleanly from the pipelines that create the abstractions.
Stress testing and monitoring — Monte Carlo simulation of model behaviour, and ongoing measurement of expectation against reality as models drift over time.
Analytical context — as with reference configurations on the infrastructure side, Jube maintains client notes on the analytical environment: the models in production, the abstractions they depend on, validation history, and the decisions behind them — on a best endeavours basis, so that consulting work starts from context rather than archaeology.

The methodology behind this work is published openly: Labrador-Level Advanced Analytics sets out the reasoning, the techniques, and the required reading. There is nothing proprietary about the approach — the value is in its consistent, defensible application to your data.

Advanced analytics consulting is available under either arrangement. The work is recorded at the client’s engaged hourly rate like everything else, and reflected in the retained commitment at review. For sustained model development, Enterprise support is its natural home.

Analytical training — little and often

Training and knowledge transfer is part of the consulting relationship rather than a separate product. It is delivered on a little and often basis: short, frequent sessions folded into business-as-usual — a model built together, a validation walked through, a procedure handed over — rather than a block course delivered once and forgotten. Deep expertise evolves as part of the working relationship, in the context of your own data and detection strategy.

Notwithstanding the embedded cadence, knowledge transfer is not left to chance: a specified curriculum ensures it is comprehensive. The Advanced Analytics with R procedures serve as both the syllabus and a desk reference — written so that skills obtained do not fade and can be applied consistently in practice. The curriculum spans R foundations, data structures, loading and shaping data, summary statistics, abstraction and transformation, linear and logistic regression, decision trees, Bayesian classifiers and networks, neural networks, Exhaustive search, and Monte Carlo simulation.

From this page to a signed engagement

There is no proposal step. This page, together with the JTOS, constitutes the complete published offer. The quote adds only the parameters specific to your engagement:

Prerequisite — completion of the Jube Training and Integration programme is a prerequisite for taking on support. This is not gatekeeping for its own sake: the programme establishes the channels, the working relationship, and — through its asynchronous support period — an evidenced picture of what support your environment actually demands. Support arrangements are then sized from evidence rather than a guess, and continue on the same channels, cadence, and time-recording basis with no separate onboarding.
Quote issued — Jube raises a formal quote for digital signature, referencing this page, and stating: the client entity, the arrangement (retained or Enterprise), the committed hours and corresponding retained monthly amount from the published scale where applicable, the initial term where the arrangement is Enterprise, invoicing details, and the commencement date.
Signature — On digital signature of the quote, the quote and the referenced documents together constitute the Work Order as defined in the JTOS. Quotes are issued by Jube Operations Limited, the contracting entity (see Governance and insurance below).
Commencement — support commences on the confirmed date, typically continuing seamlessly from the programme’s asynchronous support period. Jube issues a Service Activation Letter on commencement, recording the start date, the arrangement, the delivery mode, and which of the Enterprise commitments are and are not in force. It states no fees or rates, which means it can be shared freely — including with your own compliance, audit, or procurement function, or where support reaches you through a partner and you want to see for yourself what has actually been contracted. It is reissued whenever anything it records changes.

Ownership of extensions and configurations

Jube provides extensive configuration and extensibility capabilities through mechanisms including Inline Scripts, dependency injection add-ins, custom DLLs, and rule extensions. These mechanisms are analogous to Lua scripts in Redis — an AGPLv3-licensed software where it is standard practice that user-created scripts remain proprietary to the user and are not considered modifications to the underlying platform.

Configuration and extensibility artefacts, such as Inline Scripts and similar extensibility features, are treated as configuration data, not as modifications to Jube’s core codebase. They are:

Stored as data within the system (not merged into source code).
Compiled or interpreted at runtime (not at build time).
Deployable without modifying Jube’s core binaries or source files.
Analogous to Lua scripts in Redis.

Notwithstanding that Inline Scripts may be written in C# or other programming languages, the way they are deployed to the software constitutes configuration rather than code modification. This architecture allows the client to develop sophisticated customisations without forking Jube’s codebase, and does not require that they be released to end users — protecting the client’s intellectual property. Extensions and configurations developed by the client remain the client’s proprietary assets. Just as it would not be expected to share stored procedures from an open-source database deployment, clients’ Inline Scripts and custom extensions are not automatically subject to source disclosure.

The AGPLv3 license applies to Jube’s core platform code. When Inline Scripts or custom extensions are executed as part of a network-accessible Jube service:

If they constitute independent works that merely use Jube’s APIs and extension points (akin to stored procedures using a database API), they are not derivative works and remain proprietary to the client.
If they are so tightly integrated that they form a derivative work of Jube’s AGPLv3 code, source availability may be required for that specific deployment to users of that service — but this is not the case when using the extensibility features of Jube.

In practice, Jube’s extensibility architecture is designed to ensure that client-specific logic implemented through Inline Scripts and supported extension mechanisms remains within the configuration layer. This design pattern is well-established in the open-source community (Redis Lua scripts) and provides the client with the flexibility to deliver proprietary value-added solutions while leveraging the AGPLv3-licensed Jube platform.

Governance and insurance

All engagements are delivered under the Jube Terms of Service (JTOS) — published, versioned, and written to be clear and equitable for both parties. Professional indemnity insurance is carried with a UK-authorised insurer at the level recorded in the Work Order, up to GBP 1M per claim, which is the ceiling Jube maintains and the most any client should expect, subject to exclusions as set out in the JTOS. Where work is delivered at your premises, public liability insurance is additionally carried, at the level recorded in the Work Order.

Behind the Jube name sit two companies. Jube Holdings Limited (JHL) is a Cyprus-based company that owns the Jube software and trademarks, registered with the Cyprus Intellectual Property Office. Jube Operations Limited (JOL) is a UK-based company and wholly owned subsidiary of JHL, providing services utilising JHL’s intellectual property. JOL is the customary client contracting entity, and the entity that issues quotes under this offer.