--- title: iFlux Recorder | Multivendor Call Recording url: https://www.corecx.ai/products/iflux-recorder/ description: One recorder for every telephony vendor: every call captured with context, encrypted per call with post-quantum keys, PII redacted, plus a compliance option. publisher: CoreCx AI Pte Ltd updated: 2026-10-20 --- Record # iFlux Recorder One recorder for your whole estate, whichever telephony vendors you run. Every call is captured with full context, replayed in stereo and sealed with post-quantum encryption. Add the Compliance Recorder option when a regulator is watching. - Multivendor recording - Encrypted per call - Automatic PII redaction - Compliance option - On-premise or your own cloud **Concurrent calls: 250 to 1,000+** Storage: ≈15 MB per hour per channel ## Multivendor call recording, compliance-grade and sealed the moment every call is written. ### Multivendor by design One recorder captures calls from every telephony vendor in your estate at the same time, each configured on its own. ### Context on every call Agent identity, direction, hold and talk time, transfer and conference stitching. ### Sealed at write time Each recording is encrypted under its own key the instant it hits disk, wrapped by CoreSec KMS with post-quantum cryptography and verified every night. Multivendor ## One recorder, every telephony vendor Most estates run more than one vendor. iFlux Recorder records them all in one place, so your people search, replay and prove every call the same way. **Multivendor**Every telephony vendor in your estate, in one recorder **Every call**Inbound, outbound, internal, transfers and conferences **Every agent**Identity and call context on every conversation **Every site**Branches and data centres recorded together **iFlux Recorder** - Encrypted per call - One contact per conversation - Alarm on any missed leg - Verified every night **Replay and search** **Compliance archive and legal hold** **Speech analytics in AI Hub** **Reports and Partner API** Capabilities ## What iFlux Recorder does for you ### Multivendor by design One recorder captures calls from every telephony vendor in your estate at the same time, each configured on its own. Adding or changing a vendor never changes the recorder, the archive or the way people search and replay. - Several vendors, one recorder - One archive, one search - No recorder change when telephony changes ### Context on every call Agent identity, direction, hold and talk time, transfer and conference stitching. A conversation stays one contact from first ring to last word. - Agent identity - Transfer stitching - One contact per conversation ### Sealed at write time Each recording is encrypted under its own key the instant it hits disk, wrapped by CoreSec KMS with post-quantum cryptography and verified every night. - Per-recording keys - Post-quantum wrapping - Nightly integrity sweep ### Replay, pause and prove Stereo replay, annotations, Listen Live, PCI pause with an audited reason, and reports with spreadsheet and PDF export. A dropped leg is kept as a partial recording and raises an alarm, never lost silently. - Stereo replay - PCI pause - Never silently lost ### Personal data redacted automatically Card numbers, security codes and one-time passwords are found in every call and masked in transcripts, search and playback. Only authorised people can see the original, and every unmask needs a reason and is recorded. - Card, CVV and OTP masking - Masked in playback and transcripts - Unmask with reason, audited **250 to 1,000+** Concurrent calls **≈15 MB per hour per channel** Storage **7 years and beyond** Retention **Fully offline** Installer Options ## Choose the recorder you need Start with the recorder. Add the Compliance Recorder option when retention, legal hold and audit are mandated. Capture, encrypt, search and replay ### Recorder Multi-source capture, per-recording encryption, stereo replay, PCI pause, Listen Live, reports, multi-tenant isolation and the Partner API. [Ask about the recorder](https://www.corecx.ai/contact/) For regulated retention ### Compliance Recorder option Adds retention policies per source, legal hold by case, approval before purge, WORM archive targets, PII masking and redaction, audit-log retention and integrity alarms. Nothing is deleted before it is archived. [Ask about compliance](https://www.corecx.ai/contact/) Integrations ## Works with what you run - Multivendor telephony - iFlux Contact Centre - Directory and single sign-on - Partner REST API - NAS or object storage, including WORM Security ## Built in, not bolted on - AES-256-GCM per recording, keys wrapped with ML-KEM - Encrypted signalling and media in transit - Automatic PII redaction for card numbers, security codes and one-time passwords - Tamper-evident audit log - Role-based access and multi-tenant isolation Use cases ## Where iFlux Recorder makes the difference iFlux Recorder · Compliance officer, telephony lead ### Record every regulated conversation from any telephony The problem Each telephony change forces a recorder change, and some lines are quietly not recorded. How CoreCx solves it One multivendor recorder for the whole estate, with alarms for any dropped leg and a nightly integrity sweep. How this differs Legacy recorders are tied to one telephony vendor and lose calls silently. CoreCx records from everything and raises an alarm on every gap. [iFlux Recorder](https://www.corecx.ai/products/iflux-recorder/) iFlux Recorder · CISO, compliance officer ### Seven-year retention that survives the quantum era The problem Recordings kept until 2033 are encrypted with keys the vendor holds, using algorithms a quantum computer will break. How CoreCx solves it Every recording is sealed under its own key, wrapped with post-quantum cryptography by CoreSec KMS, and retained under the Compliance Recorder option with legal hold and WORM archive. How this differs Competitors encrypt with vendor-held keys and classical algorithms, if at all. CoreCx uses customer-held, quantum-safe keys on every file. [iFlux Recorder](https://www.corecx.ai/products/iflux-recorder/) iFlux Recorder · PCI assessor, QA lead ### PCI pause that an auditor accepts The problem Card numbers end up in recordings, or pauses happen with no record of who paused and why. How CoreCx solves it Agents or the API pause recording during card capture. Every pause is audited with a reason and shown live to the agent. How this differs Many recorders offer pause without an audit trail. CoreCx records the reason and the person on every pause. [iFlux Recorder](https://www.corecx.ai/products/iflux-recorder/) ## See what else you can do with CoreCx [ ### iFlux Secure Search & Replay Retire the legacy recorder. Keep every recording. Learn more](https://www.corecx.ai/products/iflux-secure-search-and-replay/)[ ### CoreSec KMS Post-quantum key management that keeps your recordings yours. Learn more](https://www.corecx.ai/products/coresec-kms/)[ ### CoreCx AI Hub Speech analytics, conversation intelligence and autonomous quality management, on-premise or in your own cloud. Learn more](https://www.corecx.ai/products/corecx-ai-hub/)[ ### iFlux Contact Centre An AI-ready contact centre that runs entirely on your infrastructure. Learn more](https://www.corecx.ai/products/iflux-contact-centre/) ## Put iFlux Recorder to work on your own infrastructure A pilot against your real telephony, on your hardware, in days. ## Frequently asked questions about iFlux Recorder What does iFlux Recorder do? One recorder for your whole estate, whichever telephony vendors you run. Every call is captured with full context, replayed in stereo and sealed with post-quantum encryption. Add the Compliance Recorder option when a regulator is watching. Can iFlux Recorder run on-premise or in your own cloud? Both. Most customers install it on-premise from a signed offline bundle, with no internet connection needed. You can also bring your own cloud and run it in your own cloud subscription. Wherever it runs, it never sends your data back to CoreCx. What does iFlux Recorder integrate with? Multivendor telephony, iFlux Contact Centre, Directory and single sign-on, Partner REST API, NAS or object storage, including WORM. How is iFlux Recorder secured? AES-256-GCM per recording, keys wrapped with ML-KEM. Encrypted signalling and media in transit. Automatic PII redaction for card numbers, security codes and one-time passwords. Tamper-evident audit log. Role-based access and multi-tenant isolation. Contact: contact@corecx.ai · https://www.corecx.ai/contact/