One Themis for
Majority and Rebtel
We run a single Risk codebase as two separate deployments—one per company, each with its own database, secrets, and configuration.
Risk overview
Why we're sharing the platform
Same fraud patterns
Both companies deal with the same fraud vectors, especially around SMS. Building a feature once covers both.
Existing models
Majority already has an SMS fraud model in production; Rebtel brings an online ML model.
Joint team
Rebtel engineers contribute directly to the Risk codebase, with Nick leading the product across both.
Two instances on Majority's AKS cluster
Majority Risk
namespace: riskMajority's Themis instance
Own DB & KeyVault
Majority config
Consumes from Majority PubSub
Rebtel Risk
namespace: rebtelRebtel's Themis instance
Own DB & KeyVault
Rebtel config
Consumes from Rebtel Kinesis
Majority hosts the Rebtel deployment and its Azure resources—the tenants are isolated by namespace and storage, not separate clusters.
How Rebtel connects to Themis
Event routing and analytics
Risk / Themis
Emits DecisionEvent
Majority RabbitMQ
Rebtel exchanges and queues are prefixed with Rebtel.
Majority Auditing
Consumes all events and routes them by tenant header
Rebtel analytics
Kinesis → Rebtel Snowflake
Majority analytics
PubSub → Majority BigQuery
Auditing forwards events to the matching tenant's stream based on the header rather than broadcasting to both.
Metrics and logs
Tagged by tenant
tenant.id:rebteltenant.id:majority
Set in app-settings.json (e.g. Risk.response.count).
Rebtel log view
rebtel-backend-*
OpenTelemetry logs from the Rebtel instance show up under the rebtel data view.
Both tenants report into Majority’s existing Datadog and Elastic setup.
How config and releases work
be-risk-configuration
- Split by company first, then by environment.
- Changes in Majority's
product-datasheetsautomatically open a PR here. - Rebtel config is edited directly in this repo.
Deployed together per environment
- Promoting to stage or prod rolls out both instances at once.
- Rebtel splits runtime and config into two ArgoCD apps.
We plan to move Majority's configs out of product-datasheets later on. There's also a proposal to merge be-risk-configuration into be-configuration, though we aren't there yet.
Rebtel resources in prod
Database & secrets
prod-r-risk-use2-sqlDb
prod-r-risk-kv
Single codebase
Features and models are built once and shared.
Isolated state
Each tenant keeps its own DB, secrets, and config.
Shared ops
Hosted and monitored on Majority's AKS stack.