# DeploTeka > DeploTeka creates a dedicated Shopify custom-distribution app for each client store, from one codebase, inside your own organization, delivers sealed credentials to your backend, and marks a store installed only on evidence, from one console. ## Pages - [Pricing](https://deploteka.com/pricing): Plans from €49 a month for one app and 10 client stores, a 7-day trial, monthly billing, no per-store overage. - [Developer docs](https://deploteka.com/developers): The REST API and MCP server for workspace records and Shopify collaborator access, with the OpenAPI file. - [For agencies](https://deploteka.com/agencies): Controlled, tenant-scoped, resumable setup for one dedicated custom-distribution app per client store; the merchant still reviews and approves the install. - [FAQ](https://deploteka.com/faq): Straight answers: who owns the apps, what connecting takes, how billing works, whether Shopify allows it — with links to every primary source. ## Guides - [Shopify Is Deprecating Legacy Custom Apps (Jan 2026): What Vendors Need to Do](https://deploteka.com/guides/shopify-legacy-custom-apps-deprecation-2026): Since Jan 1, 2026, new custom apps can't be created in the Shopify admin. What still works, what breaks for multi-store vendors, and the migration paths. - [How to Create a Shopify Custom App in 2026 (Dev Dashboard, Step by Step)](https://deploteka.com/guides/create-shopify-custom-app-2026): The admin "Develop apps" path closed on January 1, 2026. The current procedure: create the app in the Dev Dashboard, set scopes, pick custom distribution, install. - [Can’t Install a Custom App on a Client’s Store? The Collaborator and Dev Dashboard Problem, Explained](https://deploteka.com/guides/custom-app-collaborator-client-store): Collaborator access is store-level; Dev Dashboard apps are organization-level. Why the install fails, which four workarounds work, and which are dead ends. - [Shopify Client Credentials Grant: Token Lifetime, Who Can Use It, and Common Errors](https://deploteka.com/guides/shopify-client-credentials-grant): The client credentials grant swaps a Dev Dashboard app’s client ID and secret for a 24-hour Admin API token, for stores in your own organization only. - [How to Install a Shopify App on Multiple Stores: The Real Options](https://deploteka.com/guides/install-shopify-app-on-multiple-stores): You can't install one Shopify custom app across different merchants' stores. Here are the four real options — and when each one actually works. - [Shopify Plus: One Custom App Across Multiple Stores in an Organization](https://deploteka.com/guides/shopify-plus-custom-app-multiple-stores): One custom app can serve every store in a Shopify Plus organization: the multi-store setting, the merchant route, and where the boundary stops you. - [Shopify Custom Apps Explained: Custom vs Custom-Distribution vs Public](https://deploteka.com/guides/shopify-custom-apps-explained): The three kinds of Shopify apps — legacy custom, custom-distribution, and public — differ by who can install them, not what they can do. A plain-English guide. - [Shopify Custom Distribution: How It Works, Its Limits, and When to Use It](https://deploteka.com/guides/shopify-custom-distribution): Custom distribution installs an app by link on one store, or on stores in one Plus organization. The rules, the permanent choice, and when it is the wrong pick. - [Unlisted Shopify Apps (Limited Visibility) vs Custom Distribution](https://deploteka.com/guides/unlisted-shopify-app): An “unlisted” Shopify app is a public app with limited visibility. It still needs app review and Shopify billing. When it fits, and when custom apps do. - [Implement the DeploTeka fleet contract for an unlisted Shopify app](https://deploteka.com/guides/fleet-contract-any-stack): Reference wire shapes for an owner-led integration when the stack or version is outside DeploTeka’s verified support matrix. This guide is not a compatibility or universal-support promise. - [Run one Express app as a fleet of dedicated Shopify apps (10–30 minutes)](https://deploteka.com/guides/express-fleet-adapter): A @shopify/shopify-app-express app binds one client_id at construction. The DeploTeka Express adapter dispatches every middleware to the requesting shop’s own dedicated app instead — one install, two edits, no rewrite. - [Run one Laravel app as a fleet of dedicated Shopify apps (10–30 minutes)](https://deploteka.com/guides/laravel-fleet-adapter): kyon147/laravel-shopify already ships a per-shop credential hook: config_api_callback. The DeploTeka Laravel adapter implements it, adds the two fleet routes, and turns one deployment into a fleet of dedicated Shopify apps — no rewrite, no upgrade. - [Run one Rails app as a fleet of dedicated Shopify apps](https://deploteka.com/guides/rails-fleet-contract): The shopify_app gem reads its credentials from ShopifyAPI::Context, a process-global singleton — so one Rails app can only speak for one Shopify app. Here is the per-shop credential recipe that changes that, the three places it has to be injected, and why the obvious around_action is not thread-safe. - [Run one Python Shopify app as a fleet of dedicated apps (Flask or FastAPI)](https://deploteka.com/guides/python-fleet-contract): shopify.Session.api_key and .secret are class attributes, so one Python process speaks for exactly one Shopify app. Two endpoints, one table and a per-shop lookup change that. Complete Flask and FastAPI implementations, with the byte-exactness details both frameworks get wrong by default. - [The 40-line fleet capture: webhook-only Shopify apps](https://deploteka.com/guides/webhook-only-fleet-contract): A Shopify app with no embedded UI has almost nothing to change to run as a fleet of dedicated apps: no OAuth to rewire, no App Bridge, no session tokens. Two endpoints, one table, and a per-shop secret in the HMAC check — with the exact code, and an honest list of when this is not enough. - [Extension-only Shopify apps: receiver, offline token and installation proof](https://deploteka.com/guides/extension-only-shim): Use the fleet scaffold for registration and readback. Verified extension-only installation also requires an offline token, matching app identity and independent extension proof.