TREN
Product ecosystem

Fluxis — Enterprise AI Ecosystem

Fluxis is the AI and infrastructure product ecosystem developed through FinPay Yazılım's R&D work. It enables institutions in banking, finance and similar regulated industries to use AI on their own infrastructure in an auditable and measurable way. All products are developed on a common platform.

Ecosystem architecture

Hover over or tap the products to explore. All products run on the common Fluxis Platform.

Fluxis PlatformCommon infrastructureThe common framework that supplies identity, authorisation, caching, queuing, data access and workflow to every product through configuration. No identity provider or workflow engine is written; the institution's existing components are attached as providers. Fluxis GatewayAI governanceThe control point through which all of the institution's language model and agent traffic passes: sensitive data masking and unmasking, local/external model routing decision, policy sets, audit trail. Fluxis AtlasCodebase analysisEnd-to-end dependency map of enterprise codebases, pre-change impact analysis and natural-language querying. Fluxis ContextEnterprise memoryAn enterprise memory platform that indexes the institution's documents, requirements and decisions on-premises, links them to code and provides auditable context to agents. Fluxis ForgeAgent-based productionA software production pipeline that builds enterprise software with AI agents and passes every output through an independent quality gate.
Selected component

Product page →

Design principles

Data stays inside the institution

All components run on the institution's own infrastructure. Large language models can be hosted on-premises; external model use takes place only through the gateway, with masking and policy control.

Auditability

Every AI interaction is recorded so as to answer who, when, which data and under which policy; audit-ready reports are produced for internal and external audit.

Integration with existing infrastructure

Identity provider, directory service, workflow engine and database are not rewritten; the institution's existing components are attached to the platform through configuration.

Regulatory compliance

KVKK and BDDK requirements are provided as ready-made policy sets in the products; the institution's own policies are defined within the same framework.

Deployment and licensing model

  • On-premises deployment or the institution's private cloud
  • Single-tenant architecture; no component is shared between institutions
  • Per-product or ecosystem-wide licensing