For Technology: move without creating chaos
ReactorCX is the enterprise loyalty platform built as a real-time decision layer with one API surface for the UI and integrations, two-level event streams to your bus, batch through FeedXChange, lower environments kept in sync with production, versioned JSON deployment with audit trail, OIDC SSO and multi-AZ availability. The documentation is public, so your architects can validate it without a sales call.
A solutions architect, not a sales development rep, takes the first call.
Four things you want answered before anyone books a meeting
Is it headless, API-first and event-driven?
Yes. Nothing is UI-only. REST APIs with selective retrieval and embedded lookups; Level-1 change events and Level-2 business events published to Kafka, Kinesis, EventHub, Pulsar, GCP or webhooks; FeedXChange for batch. Integration and Events
Can we replace X without breaking balances?
SafeSwitch runs ReactorCX beside the legacy system on production traffic, reconciles every member, and cuts over by gate with rollback armed. You see the reconciliation report before you decide. Safe Migration
Is there observability, are there environments, is there rollback?
Lower environments kept in sync with production, so changes are validated before release; JSON import/export with publish and unpublish; per-activity execution logs; audit on every change. Architecture and Extensibility
Who is accountable when integration breaks?
Loyalty Methods. The team that builds ReactorCX delivers and operates it. Integration outcomes are named in Vision Alignment and owned, not disputed. Implementation and Ownership
Where ReactorCX sits in your landscape
Channels
POS, forecourt, app, web, kiosk, PMS, gaming systems, partners.
Edge
REST APIs · FeedXChange batch · partner feeds.
ReactorCX core
Activity engine · promotions and arbitration · ledger and liability · personalization · member care · analytics · governance.
Event stream
Kafka · Kinesis · EventHub · Pulsar · webhooks.
Enterprise systems
CRM/CDP, ESP, warehouse (Snowflake, Databricks, Redshift), finance/GL, BI.
Bring your landscape diagram. The Architecture Review is a working session with Loyalty Methods engineering.
Book an architecture reviewValidation checklist, with where each item lives
| Evidence | Where | Status |
|---|---|---|
| Architecture diagrams and processing model | Architecture docs | Public, no form |
| API concepts and reference | API documentation | Public, no form |
| Event catalog | Event Catalog | Public, no form |
| Environment model, deployment and rollback | Architecture and Extensibility | Public |
| Migration mechanics: what is compared, how differences are reconciled, rollback path | Safe Migration · Migration docs | Public; redacted reconciliation report via See a Parallel Migration |
| Availability history with definition and period | Reliability and Scale | Public |
| SOC 2 Type II report, pen-test summary, DR/BCP, sub-processors | Trust Center · Request Security Pack | Summary public; documents via request |
| Migration case with numbers and dates | Gap Inc. · MGM Resorts | Public |
| Reference call with a peer CIO or CTO | Through your account team | On request |
The platform understands itself, and still asks permission
ReactorCX exposes its configuration, rules, APIs, events and implementation patterns to approved AI agents through a Model Context Protocol server. AI-prepared changes land in a stage environment as versioned JSON, pass review and approval, publish with an audit entry and remain reversible. The deterministic engine executes only what a human approves.
AI and MCP · MCP documentation
What procurement will ask you to confirm
- SOC 2 Type II attestation and ISO/IEC 27001:2022 certification, dates and scope on the Trust Center.
- OIDC SSO, role- and attribute-based access, encryption in transit and at rest.
- Two privacy modes: PII in platform, or tokenized identifiers with PII held by you.
- Annual independent penetration testing.
Questions technology leaders ask
Is ReactorCX headless, API-first and event-driven, and what does it run on?
Yes. ReactorCX is a headless, API-first platform with one API surface for the UI and integrations, two-level event streams to Kafka, Kinesis, EventHub or webhooks, and batch through FeedXChange. It runs cloud-native on AWS with microservices, a NoSQL data tier and multi-AZ availability.
Is zero-downtime migration real?
SafeSwitch runs ReactorCX in parallel with the legacy platform on mirrored production traffic, reconciles balances, tiers and transactions across the full member base, and cuts over through gates only when both systems agree. Rollback stays armed afterwards. Every SafeSwitch cutover to date has completed with zero member-visible downtime.
What do we own, what does Loyalty Methods own, and who is accountable when integration breaks?
Vision Alignment documents every system, feed and integration point and who owns it before the platform is chosen. Loyalty Methods builds, delivers and operates ReactorCX with the same in-house teams and treats the customer's loyalty outcome as its problem, including integrations that sit outside the product.
Read it first. Then bring your diagram.
Public documentation for evaluation. An Architecture Review with engineering for validation. A Migration Readiness Assessment for selection. A Security Pack for procurement.