You already built it for one client. Make the next setup a controlled per-store run.
DeploTeka helps agencies run a tenant-scoped setup for one dedicated custom-distribution app per client store. Each run can pause for your operator, the merchant, or a customer-owned machine, and an unavailable observation stays unknown instead of becoming success.
- Reusable client work
- Internal tools you resell
- Integrations you maintain
Every app is created inside your own Shopify organization, with access you grant and can revoke. Your source code is never cloned, built or run on our servers, and each client still approves their own install.
The build was billable. Repeating the setup is not.
A studio's second client is a discount on the first one's engineering. The setup work in between never gets that discount — it is the same hour, at full length, every single time.
Every client needs their own app
A Shopify custom-distribution app belongs to exactly one merchant. Client six means creating and configuring a sixth app — name, icon, URL, scopes, redirects, distribution — by hand, correctly, again.
The setup lives in one person's head
Whoever onboarded client three is the only one who knows which credentials went where and which step was skipped. Handover is a call, not a screen — and it happens the week they are on holiday.
Nobody can say what a client is running
An install link that was sent is not an install that happened. Which client is on which version, with which scopes, is a question you answer by asking the client.
You already know the problem.
These are not our words. They are two agency operators, in public, describing the part of client work that does not scale.
"Managing custom integration apps as an agency partner is now cumbersome and significantly more time consuming. Each integration with every client now requires a video call with a step-by-step walkthrough to set up a new app in the dev dashboard, since we can't do this on a merchant's behalf."
— agency partner, Shopify dev forum, 2026-04-14 · community.shopify.dev/t/33280
"none of our customers are technical and anything more complicated than clicking on a link and pushing a couple of buttons will cause mayhem"
— agency operator, Shopify dev forum, 2026-04-08 · community.shopify.dev/t/33016
What a client setup becomes.
One persisted, resumable run with named operator and merchant gates. It can finish, pause, fail, or remain unknown; an install link is a next action, not evidence that installation happened. See the workflow.
One app per client store, in your organization
The dedicated app is created in your Shopify organization and remains visible in your Dev Dashboard. Disconnecting DeploTeka does not itself delete it; Shopify account continuity and policy remain Shopify-controlled.
One install request with an honest state
Your client gets a signed install link and approves it in their own admin — the merchant approval Shopify requires. The link itself is not install proof. Supported installation evidence may establish installed; it does not establish the stricter verified-live state while extension and storefront evidence are incomplete.
Credentials that never touch a chat window
Each client credential is sealed with AES-256-GCM and delivered to your backend through the bounded contract. Ordinary cabinet views expose credential state and bounded metadata, not the secret value. This implementation fact is not a compliance certification.
Releases go out one client store at a time
There is no single action that updates every client store. Each client's app is released on its own, and each store shows the version it is on. An app that ships an extension needs a build from your own machine or CI first, and a Shopify permission the merchant has not granted is approved by that client before their store moves.
Check the distribution boundary before you start.
A dedicated app per client store is DeploTeka's product topology. It is not Shopify approval or legal advice; your agency must assess its own case against Shopify's current documentation and terms.
Read the primary sources
Shopify's API Terms say one custom app must not be made available to more than one merchant. Shopify's distribution documentation describes the available methods. DeploTeka never presents those sources as endorsement.
The merchant approval stays human
The agency prepares the dedicated app and install request; the merchant still reviews and approves the install in Shopify. DeploTeka does not claim an unattended or zero-human approval path.
Read the competing interpretations and source links before deciding whether the topology fits: distribution boundary.
What connecting your code actually takes.
No rewrite, but one real change: your backend exposes two routes and a per-store credential lookup, so it can be told about each client's app. A studio running several client codebases should start with the any-stack integration guide.
Automated codemods
@shopify/shopify-app-remix v2–v4 and @shopify/shopify-app-react-router package majors 1–2. Run npx deploteka, then review and test the diff.
Adapter packages
@shopify/shopify-app-express majors 4–8 and kyon147/laravel-shopify 17.3–27: Express guide · Laravel guide.
Fixture-verified guided scaffolds
Rails with shopify_app ~>22.4, Python with ShopifyAPI 12.7.0, webhook-only Node with @shopify/shopify-api 11.6.x, and extension-only apps. An unrecognized stack or version is not supported: Rails · Python · webhook-only.
Bring the work you already do for clients.
The current workspace catalog displays Studio at €49/mo, Growth at €149/mo, and Agency at €349/mo. Agency has capacity for up to 3 apps, 200 stores, and 25 members. These are catalog capacities, not active-store metering. See the full pricing table.
Have client stores you set up by hand and want moved in? Tell us the shape of it and we will scope it with you — hello@deploteka.com.