Skip to content
← Work

Product · Shopify app operations

DeploTeka

I built DeploTeka to run one dedicated Shopify app per store. It is in production for my own Fixel Pixel fleet, about 100 stores.

Status
In production for my own fleet
My role
Platform designer and engineer
Read the engineering story →

The problem

One app per store creates operational work.

Creating an app is one step. I also need to configure it, deliver credentials, record installation, release updates and recover a run that stopped halfway.

I put those steps in a control plane. App templates are versioned assets, so the platform is separate from the code each generated app runs.

Concept illustration of dedicated app operations.

Operating pipeline

A run has to leave evidence.

  1. Provision

    Create and configure the dedicated app inside the correct tenant scope. A repeated request must not duplicate the effect.

  2. Install and verify

    Deliver credentials through the controlled path. An offline session and required extension proof establish installation.

  3. Reconcile and recover

    Keep durable records of external effects. Resume from the recorded state; an unknown outcome remains unknown until it is checked.

Engineering decisions

The boundaries are part of the product.

I keep provisioning resumable and reads and writes tenant scoped. A successful request alone does not prove that a store is installed.

Dashboard automation is a consented compatibility adapter behind a feature flag. It is unstable and is not an official Shopify API.