UA

Message us on Telegram

Backend and integrations that hold the load

APIs, queues, rule engines, payments, exchange with banking and accounting systems. We take the server side on its own or together with the interface.

Discuss a project on Telegram

Timeline by estimate

  1. Interfaces React · Next.js · Astro
  2. Server Node.js · NestJS · Python
  3. Data and queues PostgreSQL · Oracle · Redis
  4. Infrastructure Docker · Traefik

The layers this service works with are highlighted.

What is included

We agree on the exact scope after the brief. Usually it is:

  1. APIs and services shaped around your processes
  2. Queues and stream processing: Kafka, RabbitMQ
  3. Rule engines and calculations over large tables
  4. Integrations: payments, banking and accounting systems
  5. Monitoring, logs, automated deployment

Experience in this field

We don’t name clients. The figures and the technology are real.

Financial monitoring for a bank

The system continuously pulls customers, accounts, balances and transactions from core banking: about 20 million Kafka messages a day, which arrive in roughly 4 hours. The same business day it runs them through the rules: risk criteria and suspicious-activity indicators.

Every hit adds points to the customer’s score. Once the score is high enough, the system opens an alert, and an analyst and controllers review it. In a quarterly session about 300 rules go through 1.5 billion rows; most rules analyze transactions, which make up 95% of all records in the database.

Stack Node.js, TypeScript, Kafka, Oracle, PL/SQL, Redis, React

  • 20M messages a day, in about 4 hours
  • ~300 rules: risk criteria and suspicious-activity indicators
  • 1.5B rows in a quarterly session
  • 95% of the records in the database are transactions
  1. Kafka
  2. Parsing
  3. Rules
  4. Score
  5. Alert
  6. Decision

Trading platform: Forex and CFD

Real-time quotes, order execution, automated trading and a back office where access rights go down to a single field.

Stack NestJS, PostgreSQL, Redis, WebSocket, React

  1. Market data
  2. Quotes
  3. Order
  4. Execution
  5. Back office

Process

Five steps. After each one you have a result you can check.

  1. Talk and brief We find out the task, the constraints and how you will know the project worked.
  2. Diagram and estimate We draw how the system will work and name the timeline and the cost.
  3. Development Short iterations. After each one we show a working version.
  4. Launch Domain, server, monitoring, checks of speed and search markup.
  5. Support We stay in touch: fixes, growth, keeping an eye on how it runs.

Questions

Worth knowing before we talk.

Which systems do you integrate with?

Payment providers, banking and accounting systems, message queues and third-party APIs. If a system has a documented interface, data can be exchanged with it.

What volume of data is routine for you?

In financial monitoring the system takes in about 20 million messages a day, and in a quarterly session the rules go through 1.5 billion rows.

Other services

A project often touches several of them at once.

  • Web apps and platforms

    Client portals, CRMs, back offices, booking and payments, SaaS.

    from 4 weeks

  • Websites

    A landing page, a company site, a catalog. Fast and ready for search from day one.

    landing page from 3 days, website from 2 weeks

  • Bots and automation

    Telegram bots, including AI-powered ones, and the routine a script can take over.

    from 1 day

Tell us about the task

Leave a request and we will get back to you. A contact is enough: the rest we can discuss when we talk.

Or message us on Telegram: @exc1usive

What you need

One sentence is fine.

Telegram, phone or email.

The request comes straight to us. What happens to the data.

The form needs scripts. Without them, message us on Telegram.