Help
Support for DestinPQ Studio
Studio exports a folder. It does not host the site. Start with the checks below, then email us with the starter name and macOS version if you are still blocked.
The app won’t launch
Install the current Mac App Store build and use macOS 13 or later. Studio on the store is a sandboxed Mac app. If it still fails to open, email support with your macOS version and whether you are on Apple Silicon or Intel. Update to the latest store build before sending logs.
A starter kit did not download
Some agency builds fetch kit files from storage configured for that build, including WorkDrive. The public marketing site never asks you to paste those credentials. If a kit fails to arrive, email the starter name. Do not send workspace secrets in the first message.
The export folder is empty or incomplete
Pick an output path your Mac user can write. A finished export includes README-DESTINPQ-CLIENT-HANDOFF.md and .destinpq-export.json. If those files are missing, export again to a different folder and confirm the disk is not read-only.
The CMS does not connect after deploy
The exported frontend reads the Apps Script URL and related values from .env.local. Check that the script is deployed and that the Sheet is the one named in the handoff README. DestinPQ does not host that Sheet or the live site. Hosting stays on Vercel, Cloudflare, or your own infra.
Billing
Version 1.0 has no in-app purchase and no subscription inside Studio. We do not charge your client’s website visitors. Payment gateways in some exported commerce kits, such as Razorpay, are configured by your agency with the client’s keys. That billing is separate from the app.
Email support
Include the starter name, macOS version, and whether the handoff README was created. For a team rollout or custom starters, write to the sales address.