Payment and billing systems, multi-tenant SaaS, IoT and real-time protocols, ERP. Each project is led by an architect with 25 years in IT; the code is written by a team of a dozen AI agents with fixed roles, and correctness is confirmed by code review, automated tests and an independent audit.
A free 30-minute call · an answer within one business day
Transactions, thousands of persistent connections, several tenants in one system, integrations with payment and government services. Behind every class of problem is a system that already runs.
Charges, pre-authorisation, refunds, partner payouts, double-entry bookkeeping, fiscal receipts. The calculation, the invoice and the payment never diverge: everything is posted in the database in one transaction.
In production: Apostol CSMS, CopyFrog
Operator data isolation is built into the core. A new brand on the same version takes minutes, under a signed license.
In production: Apostol CSMS – three brands and a test server
Thousands of persistent WebSocket connections, OCPP, OCPI, NTRIP, telemetry. No message brokers and no garbage-collector pauses.
In production: Apostol CSMS, Campus CORS
States and transitions are stored as data and change without a rebuild. Action journal, reports, compliance with industry rules.
In production: Ship Safety ERP – in the Russian software registry
Real-time quotes from several exchanges, arbitrage pair discovery, signals, control through Telegram.
In production: Apostol ARB
Utility debt collection: penalty calculation, court documents, Excel and PDF import, scan recognition – Python services around the core.
In production: DEBT-Master
A management system for EV charging stations that the studio designed, built and maintains. A driver finds a station, charges the car and pays from the phone, and the revenue goes to the station owner. It runs in Russia and in Europe.
An operator needs a system of its own rather than renting someone else's cloud: stations from different vendors, payment without registration, revenue straight to the station owner, roaming with other networks.
Stations from different vendors work in one system. The charge, the invoice and the payment go through as one operation and never diverge. A new network under its own brand launches in 5–10 minutes.
Three brands on two markets – Russia and Europe. The retail service ocpp-css.com has been taking drivers' payments into station owners' accounts since July. The software is registered with Rospatent.
A-POST-OL is the studio's own open platform, in production since 2017, and every system we build stands on it. Sign-in and permissions, the API, workflows, files, notifications and reports are already built and proven in production – the budget and the timeline go to what sets your business apart.
Your business logic – what sets your system apart. The only level written from scratch.
A business platform inside the database: users and permissions, workflows, documents, files, notifications and reports already work.
The server: keeps browsers, apps, devices and partners connected – thousands of connections at once.
Every action goes through whole or not at all: the invoice, the payment and the history change together.
Stages and rules are stored as settings, not hard-wired into the program. A new process step goes live without stopping the system.
From one server to a cluster and Kubernetes. Growth does not mean rewriting the program.
The platform is open on GitHub under the MIT license. The system is handed over with its code and specification.
Different industries, one approach. Every system can be opened and checked.
Safety management for shipping companies under SOLAS and the ISM Code. Listed in the Russian software registry.
Ad copy, images and video for products; several AI providers, subscriptions and card payments.
Utility debt collection: pre-trial work, court orders, statutory penalties, documents for court.
Crypto futures arbitrage: real-time quotes from five exchanges, pair discovery, signals in Telegram.
GNSS corrections over NTRIP from a network of base stations: centimetre accuracy for farming and surveying.
A Telegram bot for talking to ChatGPT, entirely in PL/pgSQL – from business logic and payments to the OpenAI integration.
P2P deals with a 2-of-3 bitcoin multisig escrow and PGP signatures. Python and React: the stack fits the task.
The open build a new project starts from: sign-in, REST API, roles and workflows already work.
A new version of the safety system for shipping companies: an ISM Code safety management system and electronic ship logbooks. Built on the Apostol 2.0 core, with the API moving to Go. The goal is type approval by the Russian Maritime Register of Shipping after pilot operation.
The same studio model as Apostol CSMS: an architect and a team of roles – from the database to the independent audit.
The studio is organised like a design bureau. Each role works only in its own part of the system: testing does not fix code, the audit changes nothing – its finding becomes a task. A person approves the release.
25+ years in IT, 10+ of them as a technical director; grew up in banking IT, where the cost of a mistake is measured in money. The A-POST-OL and db-platform frameworks are his own tools, grown out of real projects. He sets the task, takes every decision and approves every release.
NoteThe agents work in plain sight, not in the background: the architect sees every session and can stop the work at any moment.
Sets the task, takes decisions, approves the release. The contract is signed with him.
The only one who allows the live system to be updated.
Task board, acceptance of results, project state, legal matters.
Writes no code.
Technology strategy, the specification, breaking a business goal into development tasks.
Writes no code.
Business logic in PL/pgSQL – the project's and the platform's; pgTAP tests.
Changes the database structure only through migrations: the system already holds real data.
C++ modules and processes, the AI support service.
Does not touch the core or the station protocols.
The C++20 transport framework: HTTP, WebSocket, TLS, PostgreSQL.
A fix goes into shared code only after it is proven on a project.
The dashboard, the driver app, payment, the sign-in screen.
Does not change shared libraries – orders the change from their developer.
The whole OCPP server, its console and the station emulator.
One repository, nothing beyond it.
A Go service over the business logic: a new way to reach the same data.
Everything is closed by default: access opens through an explicit allow-list.
Brands, version builds, image registries, installing updates on servers.
Updates live servers only on the architect's direct instruction.
End-to-end automated tests: database, REST, station protocols, payments.
Tests every part of the system, fixes none.
Requirement → code → test. Looks at the product through an outsider's eyes.
Fixes nothing: a finding becomes a task.
You get documents, not promises. They can be read, checked and taken away together with the code.
A 30-minute call: processes, goal, timeline, constraints.
Architecture and requirements with identifiers, per ISO/IEC/IEEE 42010 and 29148.
Every task is a card on the board; every change is reviewed before it enters the code.
Automated tests of every part of the system and an independent conformance audit.
One version number for all the code. Every version is checked on the test server first.
Update with one command, roll back just as easily, 24/7 support.
We reply within one business day – in person. The 30-minute call is free and commits you to nothing.
