What we build

From idea to
a resilient system.

We choose the technology and format around the problem—not the other way around.

01

Web products

Customer portals, platforms, and internal systems designed to scale.

Discuss a project
02

Mobile applications

Clear mobile products for customers and internal teams.

Discuss a project
03

Automation and bots

1C automation, integrations, Telegram bots, and back-office processes without manual routine.

Discuss a project
04

AI solutions

Assistants, knowledge search, and intelligent document processing.

Discuss a project
011C and accounting

Back-office systems: 1C and everything around it

The accounting system stops being a world of its own — its data works in web apps, bots, and AI workflows, and results flow back into the ledger.

01

Extensions that survive vendor updates

We automate inside 1C with external data processors and extensions. The standard configuration stays under vendor support, so official updates keep installing normally.

02

Exchange and integrations

Data between accounting databases, external services, and web products. Every exchange runs on an explicit contract — schema, validator, hard rejection on mismatch — instead of files that "usually open fine".

03

Documents and recognition

Invoices, registries, and source documents arrive from counterparties in arbitrary formats. We parse PDF and Excel with an LLM, learn each format once, and process it locally from then on.

04

Data quality control

Scheduled checks before closing a period: empty required fields, abnormal balances, unnetted settlements, broken references. Every finding comes with its exact address.

How we work with accounting systems
01

We don't break the standard configuration

We work through external processors and extensions. The configuration stays under vendor support, official updates install normally, and our part updates by replacing a single file.

02

Reconnaissance first, code second

We inspect the live database before designing: what the fields are actually named, what the data really holds, what the volumes are. Half of all "standard" solutions break on the fact that in this particular configuration a field is named differently — or doesn't exist.

03

Automation must check itself

We don't ship a robot that "usually works". The robot verifies its own output and honestly reports what didn't add up. Human time goes only there.

New project

Have a 1C project?

We take on automation, integrations, exchanges, and accounting-data quality projects.

Discuss a project
02Inside the product

Features that solve the problem—not decorate a checklist.

Explore product features
01

Roles and access

Precise permissions for customers, employees, and administrators.

02

Payments

Subscriptions, one-time payments, and clear statuses.

03

Live analytics

Metrics, reports, and alerts without the wait.

04

Integrations

CRM, ERP, Telegram, and external APIs in one workflow.

05

AI assistants

Answers, classification, and search over internal data.

06

Notifications

Timely messages in the product, email, and Telegram.

03Technology

Technology follows the product.

A modern stack without lock-in to closed platforms.

Explore the stack and integrations
Next.jsReactTypeScriptPayload CMSPostgreSQLFlutterNode.jsDockerTelegram APIAI / LLM1C:Enterprise 8.3PythonFastAPICOM/OData