Private training that takes your team from first principles to a working pre-production deployment of Jube — for compliance professionals, engineers, analysts, and architects. Delivered remotely over seven weeks, or on-site across a single month, at the end of which the system is in pre-production. The curriculum, certification, and payment schedule are the same either way; on-site simply compresses the curriculum into week one and turns the remaining three weeks into full-time implementation alongside your team.
This page is the offer — fees, payment schedule, and what’s included are published here in full, with nothing held back for a sales call. Get in touch to get started.
Get in touch about your team →
In private training, you’ll gain:
- Practical mastery — configure rules, workflows, and machine learning models hands-on, in scenarios drawn from your own data
- A pre-production deployment — including a chaos-tested high-availability cluster (Docker Swarm, Patroni, Redis Sentinel, HAProxy)
- Direct access to the developer throughout, for architectural correctness and certification
- Fully customised delivery — built around your team’s schedule, experience level, and objectives, via Google Meet or on-site, with recordings either way
Training is delivered by the Jube developer, ensuring first-hand knowledge throughout — from compliance fundamentals through to production deployment and C# extensibility.
Choosing a delivery mode
Both modes deliver the same eleven sessions, the same two days of custom gap development, and the same certification. What differs is how implementation support is delivered, and therefore how long the project takes.
| Remote Fast-Track | On-Site Core Accelerator | |
|---|---|---|
| Velocity milestone | Seven-week curriculum; pre-production typically follows within about three months | Pre-production within the month |
| Curriculum | Eleven sessions over seven weeks | Eleven sessions in week one, two blocks a day |
| Session length | Capped at three hours, one at a time | Two three-hour blocks a day |
| Implementation support | Asynchronous, alongside the curriculum and for two months after | Full-time in the room across three weeks, plus a follow-on on-call tail |
| Fee | $6,250 | $17,500 |
| Travel and subsistence | None | You book travel directly; subsistence at HMRC scale rate |
| Implementation reviews | Twice-weekly, remote | Daily, in the room |
Not sure which mode fits your team? Get in touch — happy to help you decide.
Both fees are fixed, agreed in advance, and include two days of custom gap development. Payment is de-risked for both sides: 50% after the first week of training, the balance on success (proof-of-concept stability and the first live transaction), typically within twelve weeks. On-site adds travel booked directly by you and subsistence at the HMRC scale rate — no premium for location, no expense float either way, and travel days aren’t billed. Support beyond what’s included continues under standard support terms.
On-site reaches pre-production faster because latency compounds (a fortnight of async questions is an afternoon over a shoulder), the expensive mistakes are the ones nobody thinks to ask about, and some institutions will badge a person but never open a remote connection at all. Structure: a remote lead-in to get the basics done before travel, week one for the full curriculum, weeks two to four full-time implementation against your own cluster and data, and an on-call tail through to first live transaction. It needs your team genuinely released for it, and an environment ready to deploy into — which the lead-in exists to confirm.
Working to a deadline like that?
Get in touch about the on-site month →
What’s included
Included in both remote and on-site delivery:
- Fully customised curriculum across eleven sessions, based on your team’s schedule, experience, and objectives
- Two days of custom gap development into the core product, closing exact client requirements ahead of training
- Hands-on workshops, guided configuration, and optional developer-focused sessions
- Practical own-time project exercises bridging each phase of delivery
- Integration support via WhatsApp, JIRA, and Loom, continuing through pre-production — asynchronous on remote delivery, an on-call tail following the on-site month
- Direct access to the developer for technical guidance throughout
- Sessions recorded and made available via OneDrive
- Jube Certified Application Specialist Verifiable Certificate
On remote delivery, additionally: implementation review meetings twice-weekly across the seven weeks.
On the on-site month, additionally: full-time implementation support in the room against your own environment and data; daily implementation review; whiteboard architecture sessions with your infrastructure and security teams; and a supervised cluster build and chaos test rather than the same work attempted unsupervised.
Who this is for
- Teams and organisations adopting Jube for AML or fraud detection
- Compliance professionals, engineers, analysts, and architects preparing for pre-production deployment
- Organisations modernising legacy transaction monitoring with an open, flexible platform
The on-site month suits a fixed external date — a licence condition, a remediation deadline, a migration cut-over — or a security posture, data residency, or co-located team that make remote delivery slower. Remote suits distributed teams and a longer runway. Sessions are grouped so each of compliance, case management, developers, and system administrators can prioritise the ones relevant to them; on the on-site month this determines who needs to be in the room on which day (roughly two to two and a half days each, not a week), sequenced around your calendar during the lead-in.
Your working week, not ours. A substantial share of Jube’s work is with institutions in the Gulf, Africa, and South and Southeast Asia, and the schedule is built around that as a matter of course:
- The training week follows your working week (e.g. Sunday–Thursday), not a European default.
- Two-block days break for prayer rather than pausing mid-topic.
- Ramadan is planned for — shortened days, or scheduled around it entirely if you’d rather.
- National and religious holidays are identified during the lead-in, not discovered on arrival.
Why Jube Training and Implementation?
- Training direct from the developer — Learn Jube from its developer, with no second-hand interpretation.
- Rapid mastery — Become proficient in weeks rather than months, accelerating your implementation timeline.
- True independence — Own your AML and transaction monitoring stack, free from vendor lock-in and restrictive contracts.
- Genuine ROI — Faster evaluation, smoother implementation, and independent mastery significantly reduce the cost of getting to production.
- Fully open-source and transparent — Jube is fully open-source (AGPLv3), auditable and extensible, keeping your data under your control.
Training Plan
Eleven sessions, each followed by a practical own-time project exercise, building toward a complete pre-production implementation. Remotely, they run over seven weeks (max three hours each); on-site, as two three-hour blocks a day inside week one.
- Session 1 (1 hour) — Prerequisites and Dress Rehearsal
- Session 2 (3 hours) — From Regulation to Real-Time
- Session 3 (3 hours) — From Data to Decisions
- Session 4 (3 hours) — Precision, Memory and Intelligence
- Session 5 (3 hours) — Managing the Human Side
- Session 6 (3 hours) — Access, Data and Insight
- Session 7 (3 hours) — Extending the Platform
- Session 8 (2 hours) — Transaction Flow Analysis and Redis Cache Internals
- Session 9 (3 hours) — Production-Grade Deployment
- Session 10 (3 hours) — C# Architecture Patterns and Solution Structure
- Session 11 (3 hours) — C# Background Threads and Transaction Processing
Practical exercises run throughout: a transaction monitoring strategy, a compliance-grade case management system, chaos engineering a live cluster, and an analytical dashboard. See the Full Training and Integration Plan PDF for session-level detail.
Practicalities
Integration support continues async-first through WhatsApp, JIRA, and Loom, on the same ticket-and-Loom-video model used in ongoing support — this period doubles as the natural introduction to that model, sizing any follow-on tier from evidence rather than a guess. Implementation review meetings run twice-weekly (daily, in the room, on-site).
Training servers are dedicated cloud instances (DigitalOcean, Frankfurt or Singapore), live for two months in isolated tenants. Participants need Git, Docker, and a running Jube instance beforehand — validated in Session 1, completed remotely before travel for on-site delivery.
Custom gap development (two included days) closes any gap between your environment and the platform — a Kafka integration in place of RabbitMQ or HTTP, say — identified and delivered during the lead-in. It’s built into the core product under AGPLv3, not held as a private fork.
Scheduling: Jube runs one training and implementation client at a time, with a typical two-month lead time from signature to commencement — a capacity constraint, not a sales device, since delivery is personal to the developer. The lead-in isn’t idle time: it’s used to stand up the training server, the WhatsApp channel, and any custom gap development ahead of Session 1.
Ownership and governance
Your Inline Scripts, custom DLLs, and configuration remain your property — treated as configuration data, not a modification to Jube’s AGPLv3 core, the same principle as Lua scripts in Redis. Full detail is in the AGPLv3 compliance guide.
There is no proposal step. This page, together with the Full Training and Integration Plan PDF and the JTOS, is the complete published offer — insurance, liability, and the contracting entity are all set out there in full. On-site attendance is subject to your site access, security, and health and safety requirements; where your procurement process requires evidence of insurance or background checks ahead of site access, raise it when you get in touch and it’s sorted during the lead-in.
Following successful implementation and first live transactions, ongoing support is available directly from the Jube developer. See Support for details.