Who is accountable
A Magento store fails quietly long before anybody notices, and it gets fixed by one person at a time. This page says who those people are, and what stands between your store and a bad release.
- Andris Stinka
- Owner — estimates, schedules, the phone and the form
- Maksims Ivanovs
- CTO, senior Magento engineer — the code and the server
- Associates
- Contracted per project, named to you, approved before access
Nobody is hired for one engagement and left off it without telling you.
Andris Stinka
Owner, Client Communication
Maksims Ivanovs
CTO, Senior Magento Engineer
Two names, and the bench behind them
Both answer for the work. Neither works alone when the work is bigger.
How the work is organised
When an engagement needs more hands, the extra hands are contracted associates: named to you, approved by you, and paid by us. You always know whose commit is in your repository.
- Who estimates
- The person who will do the work, after looking at the work. The estimate is revised out loud if the scope moves.
- Who writes it
- A named engineer, in your repository or ours, with the branch history to prove who did what.
- Who checks it
- Review before release on anything that touches production, and the finding re-measured after the change ships.
- Who answers
- Andris — one inbox, two numbers, the form and the email, during Riga business hours, usually the same day.
The firm behind the name
MagentoHUB is the Magento and Adobe Commerce work of HUB LLC: engineering in Riga, invoiced from the US entity, both numbers answered. The addresses and the numbers are printed in the footer of every page and on the contact page.
What this site will not tell you: a headcount it cannot show you, a client it has no permission to name, a rating nobody gave us, or a team of twenty. The one client we may name, and the four screens that show what we did there, are on the work page.