DeploTeka FAQ

DeploTeka is a tenant-scoped control plane for a vendor's dedicated Shopify custom-distribution apps. It creates one app per client store, seals credentials, and keeps each setup run's state and next action explicit. It does not write, host, build or run your product code.

Yes if your Shopify-connected product already exists and repeated per-client app setup is the bottleneck. Agencies and studios with repeatable client work are also a fit. It is not for a merchant who needs one app, a team still deciding what to build, or a vendor that needs App Store discovery or unattended installation without merchant approval.

Server-backed apps need the versioned fleet contract, including /api/fleet/register, /api/fleet/installed, and a per-store credential lookup. What the tooling can change depends on an exact supported manifest row; an unlisted stack or version is not supported merely because a reference guide exists. → the any-stack integration guide

Each dedicated app is created inside your Shopify organization and remains visible in your Dev Dashboard. Disconnecting DeploTeka deletes our stored copy of the dashboard session and stops our use of it; it does not itself delete the app or end your session at Shopify — that lives in Shopify's own controls (your Dev Dashboard sign-in and organization settings). Shopify account continuity and policy decisions remain controlled by Shopify.

Through your own vendor contracts and payment arrangements. Generated custom-distribution apps cannot use Shopify Billing; DeploTeka billing belongs to the vendor's separate SaaS workspace. Check Shopify's distribution documentation for the current platform boundary.

The current workspace catalog displays Studio at €49/mo, Growth at €149/mo, and Agency at €349/mo, with app, store, and member capacity limits. These are capacity plans, not active-store metering or a customer-revenue percentage. This page does not promise when checkout starts.

Yes, when the agency has repeatable Shopify-connected software for known client stores and the custom-distribution topology fits. Each store gets a dedicated app in the agency's organization, and the merchant still reviews and approves the install in Shopify. → the page for agencies

One store at a time. There is no single action that updates every client store, so a new version reaches each store as its own release and each store shows which version it is on. An app that ships an extension needs a build from your own machine or CI before that release can run. If the new version asks for a Shopify permission the merchant has not granted, that merchant approves it before their store moves.

You sign in to Shopify in your own browser; password, captcha, and 2FA stay in that browser flow. The captured dashboard session is sealed with AES-256-GCM and used only through the consented, feature-flagged compatibility adapter. That implementation fact is not a compliance certification. The intended organization can remain unknown until verified, and an expired or unavailable session requires reconnecting. DeploTeka's access is your signed-in dashboard session, not a Shopify grant: ending the session in Shopify's own controls (signing out of the Dev Dashboard) is what stops it at Shopify, and disconnecting here deletes our stored copy.

Shopify documents custom distribution, and its API Terms say one custom app must not be made available to more than one merchant. DeploTeka's topology is one dedicated app per client store; that is a product boundary, not Shopify approval or legal advice. You must assess your own distribution case against Shopify's current distribution documentation and terms.

Workspace signup is available now, but there is no first-store time promise. A store setup still requires a consented Shopify connection, a supported backend or scaffold path, and merchant approval. Install evidence can remain unknown, and this page does not promise a billing start gate.

Create a workspace, then identify your exact stack and version. Use npx deploteka only for a supported manifest row; otherwise follow the matching adapter or verified scaffold path. An unlisted stack or version needs owner-led validation before it becomes a support claim.

An existing app can be represented only when its ownership, identity, and configuration can be resolved safely. Migration effort depends on how each store was wired, and importing an app does not by itself prove installation, current version, or release readiness. We scope that path before mutation. → installing one app on multiple stores

Platform token rules can change. Check Shopify's official changelog for the current public-app requirement and assess your own distribution method; DeploTeka does not promise a permanent exemption.

The current verified rows are: automated codemods for @shopify/shopify-app-remix v2–v4 and @shopify/shopify-app-react-router package majors 1–2; adapters for @shopify/shopify-app-express majors 4–8 and kyon147/laravel-shopify 17.3–27; and guided scaffolds for 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. → the guides index