DeploTeka FAQ

The fleet layer for Shopify custom distribution. If you sell one product to many client Shopify stores, DeploTeka creates a dedicated custom-distribution app per client store inside your own organization, delivers sealed credentials to your backend, releases your app version, and confirms each install with proof. It does not host, build, or run your code.

Yes if your product connects to client Shopify stores you don't own — SaaS, ERP/warehouse connector, attribution, support tooling — or you're an agency shipping apps to client stores. No if you sell to unknown merchants through the App Store: that's what public distribution is for, and we'll say so.

No rewrite — but yes, one real change: your backend must expose two routes (/api/fleet/register, /api/fleet/installed) and a per-shop credential lookup. On Remix v2–v4 or React Router v7, npx deploteka applies it for you. Express and Laravel get a package plus a recipe; other stacks get a written guide. → fleet-contract-any-stack

You do. Every dedicated app is created inside your Shopify organization, visible in your Dev Dashboard, mechanically identical to one you'd create by hand. Disconnecting DeploTeka doesn't delete them, and you can revoke our access through Shopify-side controls at any time. We can leave and your fleet stays.

However you already do — your contracts, your invoices, Stripe, bank transfer, anything. Custom-distribution apps can't use Shopify's Billing API, which cuts both ways: no Shopify-mediated payments, and no Shopify billing requirements between you and your clients. Your pricing stays entirely yours.

No. You pay a flat subscription (from €49/month) priced per app and per active client store. We never see, touch, or take a percentage of what your clients pay you.

Yes — it's the textbook case: a client-specific app for a client store is exactly what custom distribution exists for. The app lives in your organization; your client clicks one install link instead of sitting through a Dev Dashboard walkthrough on a video call. → /agencies

You release a new app version once; DeploTeka applies it across the fleet. Extension-free apps release entirely server-side. Apps that ship extensions build once through a small agent on your machine or CI, then fan out. Scope changes are previewed and confirmed before any store is re-released, and new scopes still require merchant approval.

You sign in to Shopify in your own browser, once, and grant DeploTeka a captured dashboard session for your organization. It's sealed in an AES-256-GCM vault, used for app creation and releases, and it expires routinely — we notify you and reconnecting takes a minute in the browser. You can revoke it on the Shopify side at any time.

Custom distribution is a supported Shopify path, and the API Terms require one-app-per-merchant — which the model satisfies by construction. Four Shopify staff describe this exact setup on the record; one staff post reads the multi-merchant case differently. We link all five sources and you should read them. → /#allowed

Workspace: two fields, right now. First live store: connect Shopify in your browser (minutes), wire the backend contract (minutes on Remix via npx deploteka; longer on other stacks), then send your merchant the install link. The slowest step is usually the merchant clicking it. Your first app and first verified store are included before billing starts.

Run npx deploteka inside your app's repository. It pairs your workspace, reads your app config, wires the backend contract where it can, and walks you through connecting Shopify. No repo handy? Create the workspace at /start and follow the four-gate checklist instead.

New custom apps can no longer be created in a store's admin, and the copyable admin token is gone from every screen — so "create a custom app and paste us the token" onboarding instructions now describe screens that no longer exist. → shopify-legacy-custom-apps-deprecation-2026

All public apps must move to expiring offline access tokens by January 1, 2027. As of today, Shopify's changelog lists custom apps as unaffected — one migration the custom-distribution path doesn't inherit. That's current policy, not a guarantee; here's the changelog so you can check it yourself: changelog.

Three tiers, honestly labelled: Remix v2–v4 and React Router v7 — npx deploteka applies the change; Express and Laravel — adapter package plus a documented recipe; Rails, Python, webhook-only, extension-only, and everything else — a written guide with starter files. If yours isn't listed, email us the framework and we'll answer plainly. → guides index