01
Production or it isn't done
A project is finished when there is a working URL, migrations, green tests and backups. A prototype that “basically works” does not count as finished.
Who we are: engineers who take the work to production and stay on for support
ASTROLABS is the IT division of the ASTRO GROUP holding. We build AI agents and business automation: we take a process apart into roles, hand each role to its own agent, and wire them into a pipeline that runs without a human. We are not a consultancy with slide decks: a project counts as finished when there is a working URL, migrations, green tests and backups.
How it started
We deployed it to ourselves first
The holding sells furniture and tools on marketplaces. The exact pains we now treat for clients hurt us first: prices and stock drifting apart across three systems, a buyer question backlog growing faster than the team, content blocking every new launch. We built ourselves a CRM, an operator copilot and a content factory — and only once all of it had survived our own live data did we take it to clients. That's why our demo is not a rig assembled for the meeting: we show the system we run our own business on every day.
ASTROLABS
Space-grade IT: automation taken all the way to production.
The IT division of the ASTRO GROUP holding
Principles
Engineering principles
02
Every decision gets an opponent
Non-trivial code goes through double-blind review: two reviewers read the change independently, seeing neither the author's reasoning nor each other's findings. On critical paths one of those voices is a model from a second vendor — one model family has systemic blind spots, and another one doesn't share them.
03
Client data: by procedure and by contract
Backup before the operation, a transaction with a row-count gate, read-back verification, a rollback plan. A bulk operation without a gate does not pass our review. We deploy inside your perimeter on request; calls to a language model go to a provider, and exactly what is sent there is fixed in the contract.
04
Numbers instead of adjectives
“Works correctly” is not an acceptance criterion. A criterion is a specific number: how many listings were updated, how many tests are green, what the drift is.
05
What you walk away with is written into the contract
On development projects, formal technical documentation and a handover package are part of the work. Transfer of the source code and of the rights to it is a matter for the contract: full assignment is one of the options. We fix the scope of that transfer before the work starts, so you know the boundary in advance instead of discovering it when we part ways.
06
An honest “no” beats a confident invention
This applies to our AI agents, which say “I don't know” rather than produce a plausible fiction, and to us: if a task doesn't fit the stated timeline or budget, we say so before the contract, not after.
How the work is set up
Instead of a “Team” page — who is accountable for what
We don't publish a gallery of faces or claim “50+ experts”. Behind your project there is one accountable person, a mandatory engineering pipeline, and contractors we bring in for a specific scope. That is our team — so you know from the start who you are talking to and who answers for the result.
01
An accountable project architect
Every engagement has one architect, and he is also your point of entry. His remit: taking the process apart into roles, the architecture of the solution, acceptance criteria expressed as numbers, access and data handling, sign-off on every stage, and the ship-or-not call. He does not hand you over to an account manager: the person you scoped the work with is the person you talk to during support. The flip side is stated honestly — we run a limited number of engagements at a time, and we tell you the realistic start date before the contract, not after.
02
The engineering pipeline is part of the team
The role an agency fills with a department, we fill with a procedure. Author and critic are always separated: two reviewers read the change independently, seeing neither the author's reasoning nor each other's findings — merged roles produce a self-confirming loop. A stage closes on a number from the acceptance criteria, not on the word “done”; an empty reviewer report means “no verdict”, not “all clear”. So the quality does not depend on who happened to be at the keyboard that day. Details are in Method.
03
External developers, per scope
When a project needs extra hands or narrow expertise, we bring in an external developer on contract for a defined scope of work. Their code goes through the same pipeline: review, tests, acceptance by numbers. Accountability towards you is neither split nor passed on — the contract, the deadlines and the result stay with ASTROLABS, and access to your systems is granted at the minimum level and only for the duration of the task.
Documents
The legal side
ASTROLABS is the IT brand of the ASTRO GROUP holding. Contracts, invoices and closing documents are issued by ALFADISK LLC, a company operating since 2021 and listed in the Russian federal register of personal data operators. We work under contract with a written specification, formal acceptance and clear allocation of rights to the deliverables. The company identifiers are right here on this page — you can verify them in the Russian state register of legal entities before we even speak. Bank details and the registered address come with the invoice and the draft contract.
Legal entity
ALFADISK LLC
Tax ID (INN)
7727479639
Registration No. (OGRN)
1217700601722
Holding
ASTRO GROUP
Operating since
2021
Personal data
Registered operator (Roskomnadzor)
Let's get acquainted
Tell us about the process you'd like to automate. We'll answer honestly — including “you don't actually need this”.
Write to us