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 charging station management system the studio designed, built and maintains. Europe (Stripe, AFIR) and Russia (YooKassa, 54-FZ) in one codebase, each brand on its own instance.
An operator needs a system of its own rather than renting someone else's cloud: stations from different vendors and protocol versions, payment without registration, revenue straight to the station owner, roaming with other networks.
Station protocols are a separate C++20 service. Business logic and money live in PostgreSQL in one transaction: the calculation, the invoice and the payment never diverge. A new brand is deployed from a signed license in 5–10 minutes.
Three brands on two markets and a test server. The retail service ocpp-css.com has been taking drivers' payments into station owners' accounts since July. The software is registered with Rospatent.
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. The test server first, then partner systems, the live system last.
Update with one command, roll back just as easily, 24/7 support.
Update orderA new version is first installed on the test server and in partner systems. The live system with real customers is updated last – and only if the three stages before it had no failures.
Our own open platform, in production since 2017. Sign-in and permissions, REST API, workflows, files, notifications, reports and the journal already work – the budget goes to your logic.
The business logic that sets your system apart. The only level written from scratch.
Dozens of PL/pgSQL modules: OAuth 2.0, three-dimensional permissions, workflows as data, files, event publishing, reports.
C++20: HTTP, WebSocket, TLS and PostgreSQL in one epoll event loop. Like nginx – not part of your project.
The price of the choiceBusiness logic is written in PL/pgSQL, and there are fewer specialists in it than in mainstream stacks. That is why every system is handed over with its specification, and every entity's files follow the same layout.
Two ways to work and budget guidelines. We name the exact sum and timeline after looking at the task.
$100 / hour
$800/day · $4,000/week · $16,000/month
We take the whole project – from architecture to production and maintenance. One point of accountability.
$60 / hour
$480/day · $2,400/week · $9,600/month
We join your team or reinforce the server side within your processes. Minimum – one week a month.
| Project | Timeline | Budget |
|---|---|---|
| A compact MVP or an integration on the ready foundation | 1–1.5 months | $16,000–24,000 |
| A system with several user roles and payments | 3–5 months | $48,000–80,000 |
| A multi-tenant SaaS at the Apostol CSMS level | 6+ months | from $96,000 |
The A-POST-OL and db-platform frameworks are open under the MIT license. No closed black box.
The code, the specification and the decision history are handed to the client.
Any PostgreSQL developer can maintain the system: the logic is standard PL/pgSQL.
We reply within one business day – in person. The 30-minute call is free and commits you to nothing.
