Research work (NIR)
A review of the field, hypotheses and tests of them on your data. The result is a reasoned answer: whether the problem can be solved, and at what cost.
R&D · Research · Development
We carry out R&D in software and AI: we research and build an algorithm, a model or an architecture when no ready solution exists yet. In Russia, R&D is more often associated with instruments and design documentation. Our subject of research is different, but the order of work is the familiar one: hypothesis, experiment, report, acceptance.
For companies that need something the market does not offer: their own algorithm, a model for their own task, a test of a technical hypothesis before investing in a product.
A review of the field, hypotheses and tests of them on your data. The result is a reasoned answer: whether the problem can be solved, and at what cost.
From a confirmed hypothesis to a working prototype: architecture, implementation, testing, documentation.
We develop algorithms and models when ready-made solutions do not fit on accuracy, licensing or deployment requirements.
The technical specification, the test programme and methodology, stage reports. Documents that pass acceptance and are needed to account for the work.
The result stays with you: source code, documentation, team training. We do not build in a dependence on us.
We turn a vague goal into a testable hypothesis with a success criterion. Without that, research can go on forever.
A review of the field, experiments, early checks. We take on the research risk and report a negative result at once.
Building the solution and testing it to an agreed methodology.
Stage reports, source code, training for your team.
Some of our work is open: the Balansis numerical library on PyPI and the Agent Native Universe agent runtime under MIT. For the Balansis model, 153 theorems are proved in Lean 4 with no gaps (as of 05.10.2026). They prove the algebra of the model over the real numbers, not the behaviour of float64.
If a hypothesis is not confirmed, we say so at an early stage, while that is still cheap. We publish our own negative results too: the open Agent Native Universe repository records that the relationship graph between agents gave no advantage on these tasks.
If you need it, we take the prototype to a service in operation. That is what happened with sandwich-panel specifications from CAD drawings: on one real project, 784 of 784 panels matched the manual specification line by line.
Manufacturing · Building materials
MVP in operationReads DWG/DXF layouts and builds the Excel spec: 10–30 seconds instead of 2–15 hours by hand. All 784 panels of one real project matched the manual spec line by line.
Real estate · PropTech marketplace
MVP in operationFrom a mock-up to a working platform: plot → works → contractor → request. Rule-based next-step engine, three dashboards, personal-data compliance. MVP in 2 months.
Marketplace e-commerce · Pricing
PilotCompetitor prices tracked per SKU, a price computed by rules inside an agreed corridor and applied only after confirmation. Pilot: 10 SKUs, setup within 14 days.
EdTech · HR-tech
MVP in operation (demo stand)The client had a business model and no product. We built a student-task marketplace MVP where the server enforces legal and platform rules, and put a demo stand live.
AI infrastructure · multi-agent systems R&D
Research projectIn four days we built and open-sourced (MIT) an agent environment where code enforces the rules: cryptography, a PBFT-style agreement protocol, reproducible experiments.
EdTech / AI research
Research projectA research neuromorphic memory core and a student model, taken to a service in 10 days: 32 REST endpoints, 368 tests, 21 Lean 4 statements. The code is open.
Scientific computing / R&D
Research projectCompensated-computation library: precision loss is visible and checkable, the model’s algebra is proved in Lean 4, each numeric claim has a reproducible benchmark.
Research (NIR) answers the question “is this possible, and under what conditions”. Its result may turn out negative, and that is a normal outcome. Development (OKR) takes a possibility confirmed by the research and brings it to a design or a working sample.
Yes. R&D is defined by the nature of the work, and the industry plays no part: there has to be scientific or technical uncertainty that standard design cannot remove. Developing a new algorithm or model for a task with no ready solution meets this criterion.
That is a regular outcome of research, and it has value: you get a reasoned answer that the path does not lead to the goal before you invest in developing a product. We plan the stages so that such an answer comes as early and as cheaply as possible.
The contract sets the rights to the result. By default we assume they belong to the client. The terms on exclusive rights are fixed before work starts.
Forecasting · ML · Data analytics
Multi-agent architectures · LLM · Autonomy
AI agents · Assistants · Task automation
The AVA calculator works out the economics of your process from your own figures, with no form and no price from us. If automation does not pay off, it says so.
Estimate the paybackDescribe the problem in your own words. If it can’t be solved or won’t pay off, we’ll say so before any work starts.