Skip to content

Magento stores, kept running

One senior Magento engineer and one person running estimates, schedules and support in Riga.

Free Store Audit

The store URL is all we need. A findings memo and a call in 2 to 3 business days, and the hours are ours, not yours.

Maksims Ivanovs, CTO, 11+ years on Magento 2. Andris Stinka, owner, years spent on estimates, schedules and support.

The agency that built your store is gone. Somebody has to keep it running.

We take over the codebase, the server and the backlog. We stabilise it, patch it, speed it up and keep it running, and we work in your repository under your name when the client is an agency's client. One engineer is accountable for the engagement, from the first estimate to the last release. No account manager, no junior hand-offs, no re-platform proposal on day one.

Andris Stinka, owner of HUB LLC, running estimates, schedules and support

Andris Stinka

Owner, Client Communication

Maksims Ivanovs, CTO of HUB LLC and senior Magento engineer

Maksims Ivanovs

CTO, Senior Magento Engineer

Who is on the project

One engineer writes the code. One person answers the phone.

The work we may name

One client by name. Two kinds of engagement by description. Where we may not name the client, we say so instead of inventing one.

AlkOutlet.lv

kept since 2024

One of Latvia’s largest online alcohol retailers, part of a retail network in more than 45 cities. We keep the Magento 2 store live: patches as they publish, monitoring with failover, the ERP stock sync.

What we do there
A product page on AlkOutlet.lv: the price, the in-stock line, the quantity field and the add-to-cart button
The price block, the stock line fed by the ERP, the add-to-cart path an audit reads first.

White-label engagements

by contract

Implementation and rescue work inside other agencies’ estimates, named in their reports and change logs, never in ours.

How that runs

Rescue engagements

one-off

Stores taken over from an agency that is gone, then kept or handed back. The client decides after the findings memo which of the two.

What rescue costs

Agency or merchant?

Both start with the same free audit. Neither needs a call first.

White label

Agencies who sold the project and need the Magento part done under their own name.

  • Fixed prices per engagement, which you mark up
  • Unbranded estimates, reports and commits in your repository
  • Non-solicit both ways, before the first credential

Rescue or maintenance

Merchants whose store was built by somebody else and that somebody is gone.

  • €90 an hour, two hour minimum, estimate first
  • Patches, cron, indexers and backups brought under control
  • The findings memo first, the work after you approve it

How it starts

  1. You send the store URL

    one line is enough · 2 minutes

  2. We spend the hours before anyone pays us

    6 to 10 engineering hours · 2 to 3 business days

  3. You get a findings memo and a call

    ranked, with hours beside each · the same week

  4. You get hours and a total before we touch anything

    you choose what to fund · before any work starts

The audit is free. That means we carry it: we spend 6 to 10 hours of engineering before you decide anything. We can do that because we do not pay for a sales team.

Findings memo · 3,400 SKUs on Hyvä

58 of 100 · 4 critical, 3 shown

  • F-01Magento security patches missing (latest 2.4.5-p3)Critical4h
  • F-02Mobile checkout LCP 5.1s, Apple Pay and coupon flow blockedCritical16h
  • F-04robots.txt blocks GPTBot, ClaudeBot, PerplexityBot unintentionallyCritical1h
The memo you get ranks every finding with hours beside it. The 25-page sample is public, no sign-up.