Scope is a promise, not an opening bid
We quote what we can deliver and say no to the rest. A project that grows quietly is a project that ends badly for both sides.
A small team that ships its own products.
Aethera is an engineering company in Tashkent. We build software for clients and we build our own products with the same people, which keeps us honest about what things really cost.
01 / 03
Every great system starts as a drawing.
Before code, there is a line on paper: who does what, where the money moves, what must never break. We draw first. The drawing is the promise.
02 / 03
We build for month twelve, not day one.
Demos are easy. Systems that survive growth, audits and staff turnover are not. Everything we ship is designed for the year after launch.
03 / 03
Our own products keep us honest.
We run two products in production. Every method we recommend to a client has already cost us our own money first.
How we got here
- 2023
Contract work, one team
Started as four engineers taking on backend and mobile work for companies in Tashkent. Enough projects to see the same problem everywhere: operations running on spreadsheets and 1C exports.
- 2024
First field systems
Shipped the first offline-first field apps for distribution and logistics. Learned that the hardest part is never the code — it is the shift supervisor's actual workflow.
- 2025
Aethera ERP begins
Turned the pattern into a product: a cloud ERP with the compliance core built in rather than bolted on. Development started against a real wholesale business.
- 2026
Two products, one standard
Aethera Health joined the portfolio, and client work now runs on the same engineering standard as our own products — same reviews, same gates, same people.
How we decide
Four positions we do not trade away.
Boring technology, on purpose
PostgreSQL, TypeScript, well-worn frameworks. Novelty is a cost paid by whoever maintains the system in three years.
The client owns everything
Code, infrastructure, documentation and accounts. Lock-in is not a business model we are interested in.
We say when something is not working
Including when it is our estimate, our architecture, or our mistake. You find out in the weekly call, not at the deadline.
Team
Who you actually work with.
No account layer between you and the engineers. The people below are the people on the calls.
Giyosiddin UbaydullayevFounder, engineeringArchitecture, ERP compliance core Dilshod ErgashevBackend leadNestJS, PostgreSQL, integrations Malika TursunovaProduct designField interfaces, design system Otabek NazarovMobile leadReact Native, offline sync Sevara QodirovaDeliveryDiscovery, scope, client communication
Contact
Tell us what is not working.
A short description of the problem is enough to start. We reply within one working day, and the first conversation is free.