The orchestrator that connects your core banking to your systems — and turns your data into decisions.
Temenos, Capital Banker, Sopra Amplitude, other core banking systems, Sage, Odoo, … : your systems generate value, but integrating them remains a permanent project. OCTY centralises all your flows through a single access point, exposes modern APIs to your applications, and transforms raw data into decision-ready dashboards. One platform. Unlimited connections.
Every new connection to your systems costs more than the last.
Your core banking, your ERP, your Oracle or PostgreSQL databases, your SFTP files: every system generates critical data. But connecting them to each other, to your channels and partners, increasingly resembles a spider's web — and you are its constrained architect.
With Temenos Transact, this problem takes a particularly acute form. Two challenges accumulate and reinforce each other:
One IRIS API per application. One technical debt per API.
The standard approach creates a separate API through the IRIS layer for each channel or external application. The result: a proliferation of entry points, duplication of business logic, and a maintenance burden that grows faster than your team. Every new application reopens this project — regardless of the source involved.
OFS is fast. IRIS, under load, is not always.
The native OFS protocol delivers high performance — but it is complex and verbose to manage at scale. The IRIS abstraction layer simplifies access but introduces significant latency under heavy load. IT teams face a difficult choice: performance or maintainability.
This is not a competence problem. It is an architecture problem. And an architecture problem is solved with a better architectural pattern.
A central orchestrator. Modern APIs to all your sources.
OCTY is not another connector. It is the centralised orchestrator that absorbs the complexity of your integrations — core banking, ERP, databases, files — so that your applications consume simple, modern APIs. Whatever the source.
A single connection point to your systems. No more connector jungle.
OCTY communicates with each source via the appropriate protocol or connector — native OFS for Temenos, SQL drivers for your databases, REST for third-party APIs. Single access governance. Zero logic duplication across your applications.
OFS performance, without OFS complexity.
For institutions running Temenos Transact, OCTY goes further: it communicates via native OFS protocol, bypassing the IRIS layer and its latency under load. Your applications consume modern APIs exposed by the orchestrator. OFS complexity stays on OCTY's side. Not on your teams'.
Connecting a new application no longer starts from scratch.
Every new external application connects to the OCTY orchestrator, not directly to your source systems. The integration foundation is already in place. Your time-to-market for any new channel or partner reduces to the connection to OCTY.
OCTY: the central platform with five tentacles reaching your data.
Like an octopus extending its tentacles to every source without losing the thread, OCTY centralises and orchestrates your data flows from a single point.
CBS & Systems Connection
Universal entry point: core banking (native Temenos OFS and others), ERP, databases, APIs, SFTP. Real-time extraction.
Octy Pipelines — OctyCraft
ETL engine: orchestration and transformation of data flows. 7 connector types. Sequencing & scheduling.
Octy Datamart
Continuous historisation. Data warehouses & data lakes. Centralised analytics.
Octy Search
Advanced search. Direct & SQL queries. Granular index/column control.
Octy BI — OctyBoard
BI without technical expertise. Visual queries. Dashboards. iframe/REST API integration.
From extraction to dashboard — every component does its part.
OCTY is a modular platform. Each module covers a precise scope and articulates with the others in a continuous data flow.
Programme your data pipelines. Without coding each step from scratch.
7 supported types: local, SFTP, PostgreSQL, MySQL, Oracle, SQL Server, API. Each connection point configured once, reused everywhere.
Source → transformation → destination. JSON configuration — precise, versionable, reproducible.
Pipeline chaining, manual or scheduled execution, detailed activity logs.
Your core banking connectivity layer. With native Temenos OFS integration.
OctyAPI exposes modern APIs to your applications and pipelines, regardless of the source system. For Temenos Transact institutions, OctyAPI integrates the Universal T24 Connector — native communication via OFS protocol, without going through the IRIS layer.
Access your server file paths from the interface.
Structured access to source paths (local I/O), destination paths (local outputs) and configuration paths (transformation scripts). No terminal manipulation.
Find any data in your Datamart. In seconds.
Precisely specify the data you are looking for.
Select the target index and column for surgical searches.
Direct queries or structured SQL queries depending on your need.
Directly accessible from the application, no external tool required.
Decision-ready dashboards. Without writing a line of SQL.
The interface translates user interactions into SQL — filtering, aggregation, joins.
Semantic layer over your database — table relationships, business metrics, accessible data.
Bar, line, pie, geographic maps. Custom visualisations via the visualisation API.
Embed dashboards via iframe or REST API into other applications.
Three concrete use cases. One platform behind each.
OCTY is not a technology demonstration. It is an operational tool deployed on real business cases.
From T24 to BCEAO declaration — without manual intervention.
The institution extracts its Temenos T24 data via OCTY, which injects it into the Datamart. FIRES — TNA Consulting's RegTech platform — consumes the Datamart to generate BCEAO regulatory reports. A fully automated pipeline, from Core Banking to regulatory submission. No manual consolidation. No intermediate CSV exports.
OCTY is the connectivity layer that feeds FIRES. The two products are complementary.
Your Core Banking, ready for national interoperability hubs.
National interoperability hubs — such as Mojaloop-type platforms (open-source FSPIOP/DFSP standard for financial inclusion, connecting banks, mobile money and fintechs) — require reliable and secure integration with the Core Banking systems of member institutions. OCTY is the orchestrator that connects Temenos Transact to these hubs. It translates hub requests into native OFS calls to T24, and returns responses in the formats expected by the interoperability platform. The institution connects to the national network without directly exposing its Core Banking.
All your sources in a single Datamart. Your dashboards fed continuously.
Your institution collects data from Temenos, SFTP files, Oracle or PostgreSQL databases, third-party APIs. OctyCraft orchestrates ETL pipelines from these seven source types to your Datamart. OctyBoard consumes the Datamart to produce the decision dashboards your teams use daily. Historisation is continuous — each extraction cycle feeds the warehouse without overwriting previous data.
OCTY installs in your infrastructure. On-premise, controlled.
OCTY is deployed on-premise in the institution's infrastructure. No data leaves your perimeter.
Technical prerequisites
| Operating system | Linux: Ubuntu 20+ / Rocky Linux 9 / RHEL 9 |
| Containerisation | Docker |
| Processor | Multi-core, 8 vCPU recommended |
| RAM | 32 GB minimum — 64 GB recommended |
| Primary storage | 512 GB SSD minimum (NVMe recommended) |
| Data Warehouse storage | 2 TB expandable (RAID 10 or SAN/NAS) |
Supported I/O connectors (OctyCraft)
| Local files | Local read/write |
| SFTP | Secure transfer |
| Databases | PostgreSQL · MySQL · Oracle · SQL Server |
| API | REST API |
Four reasons why OCTY is an orchestrator, not just another connector.
A proven integration pattern, not a patchwork.
The centralised orchestrator is the recommended integration pattern for modern core banking systems. OCTY implements it for all your sources — core banking, ERP, databases — with centralised access governance and modern APIs exposed externally. One orchestrator for all.
From extraction to decision — without switching tools.
OCTY covers the entire data chain: extraction (OctyAPI), ETL orchestration (OctyCraft), storage (Datamart), search (OctySearch), visualisation (OctyBoard). The same platform, from connector to dashboard.
Built for African financial institutions.
OCTY is developed and operated by TNA Consulting, a firm specialising in financial information systems in Morocco and Africa. Use cases — BCEAO reporting, interoperability, T24 — are at the core of the product, not late adaptations.
OCTY + FIRES = the complete chain from Core Banking to regulator.
OCTY feeds FIRES with clean, transformed and historised Temenos data. FIRES generates regulatory reports. Together, they cover the complete cycle: from Core Banking to the central bank, without manual intervention.
Your integration architecture can be simpler. Let's see how.
IT teams managing integrations between core banking, ERP and third-party applications know exactly where the friction is. OCTY was built from those friction points — not around them. Let's discuss your current architecture and what a centralised orchestrator would concretely change in your context.