Frequently asked questions

Answers to common questions about using PWASK and running a SaaS product

Clone the repo, copy the .env template, set your Supabase keys, then start the dev server. See the Getting Started guide for step-by-step instructions.
Yes. Use Add to Home Screen on mobile or Install App on desktop. The service worker caches the shell and content is cached on demand. You'll see a reload prompt when a new version is available.
Yes — it's offline-first. Writes are queued in IndexedDB and sync when you're back online. Large uploads are retried with exponential backoff.
Modern browsers (Chrome, Safari, Firefox, Edge) and current iOS/Android are supported by default. Legacy browsers are not supported out of the box.
Supabase Auth supports email/password, magic links, and OAuth providers like Google and GitHub. Use anon keys in the client only; keep service_role keys server-side.
Enable RLS on all user/tenant tables and use role-based policies (viewer/editor/admin). Test policies with multiple accounts and avoid broad rules.
Enforce TLS, use secure cookies, validate inputs server-side, and prefer signed URLs for private assets. See the Security guide for details.
Enable automated Postgres backups, periodically export critical storage, and rehearse restores in staging. Hosted plans include regular backups and export tools.
Version your service worker/assets, provide IndexedDB migrations when schemas change, and surface a "New version available" in-app prompt to reload gracefully.
We minimize personal data and provide export/deletion options. See our Privacy Policy for legal bases, cookies, and international transfers.
We offer a developer-friendly plan with everything included and commercial licensing. See the Pricing page for current rates and the Licencing page for usage rights.
Yes. The starter is designed to deploy on your infrastructure. We provide environment and production configuration guidance in the docs.
Supabase, Stripe, common OAuth providers, and optional email providers are included. It's straightforward to add more integrations.
Join our Discord for community support. Paid plans include priority support and optional SLAs. Enterprise support is available on request.
Yes — next-intl powers i18n. Add locales by providing message files and enabling them in configuration. The language switcher preserves the current route.
Stripe examples are provided. For subscriptions or marketplaces, add server-side webhooks and background workers, and always verify signatures.
Provide in-app account deletion and a contact for manual requests. For portability, offer CSV/JSON exports and include related assets when applicable.
401/403: check session freshness, anon vs service_role usage, and RLS rules. SW not updating: unregister or bump the version. Image 404s: verify next/image domains and storage policies.