Answers to the things people usually ask us first.

Shopify is where most of our work lives — it's the platform with the richest extension surface and the most interesting edges to push against. We'll take on non-Shopify ecommerce work if the system shape is a fit.

Yes. Everything we build runs as a small set of Docker containers and talks to Postgres + Redis. We can deploy onto your Coolify / Railway / Fly / bare Docker host, or run it on ours and hand it off later.

Most projects start with a 1–2 week discovery phase where we map the real system (not the diagram) and produce a concrete scope. From there, build phases run in 2–4 week increments with a working deploy at the end of each.

Yes — for systems we've built, we run monitoring and incident response. We prefer this over hand-off-and-walk-away because the alternative is a client stuck with an unfamiliar codebase the first time it breaks.

For CRUD-heavy merchant admin UIs, we default to server-rendered Go templ + HTMX. It gives us end-to-end type safety, far less code than an equivalent React + API stack, and it scales cleanly as the UI grows — which is why it's the right default for the kinds of dashboards we build. That said, we're not averse to modern JS/TS frameworks: React, Next.js, and TypeScript are regular parts of our toolkit on projects where a richer client-side experience is the right call, especially consumer storefronts. We pick the stack to match the problem.

Our client work is always delivered with full source. The innovonics app suite itself is closed-source as a product, but we're happy to walk through architecture in a call.

We do product and interface design for the systems we build — the admin console for recurrabee, the filter tree builder for searchabee, etc. We partner with specialist brand and marketing design teams when a project needs that work.