A small systems studio for ambitious ecommerce brands.

How we think

We like boring technology. Go, Postgres, Redis, and Meilisearch on the backend. For merchant-facing admin UIs we reach for server-rendered Go templ + HTMX by default — it gives us end-to-end type safety and scales cleanly as the UI grows. When a project calls for a richer client-side experience, we're comfortable with React, Next.js, TypeScript, and the rest of the modern JS toolkit. We pick the stack to fit the problem, and the goal is always software that is legible six months from now to whoever inherits it.

How we work

Carefully. Every change we make is scoped, reviewed, and tested before it reaches your customers. We prefer small, reversible releases over big risky pushes; every deploy is one Docker image away from a rollback, every state transition is logged, and nothing is committed without a clear reason. Stability isn't a feature we add at the end — it's the shape of how we build.

Why the app suite exists

We build and operate our own Shopify apps — recurrabee, eventabee, searchabee — because the client work we take on demands infrastructure we understand from the inside. Every app in the suite solves a real problem we hit first, then shipped as a product.

Stack

What we reach for by default, and what we write against every week.

Platforms

Where the work lives. Shopify is our home base. We're fluent enough on the alternatives to integrate, migrate, or replatform when a project calls for it.

Who we work with

Brands past the early-stage plugin phase. Teams that have outgrown the Shopify app store defaults and need systems that hold up to real traffic, real catalogs, real subscription volumes, and real ad spend. If that's you, say hi.