Every entry is tested before publishing
The launch catalog is founder-authored and run against real workflow expectations before it appears for sale.
Versioned files and revision history
Each product file records version, file size, MIME type, storage key, and SHA-256 manifest data before production release.
Five-hour cooling-off window
By default, orders are held for five hours. Cancel before release for a full refund; waive only when you want instant delivery.
Gated delivery, not public file links
Downloads go through entitlement checks, short-lived tokens, download logging, and server-side watermarking for JSON workflows.
Feedback desk
Reader notes drop here.
Early feedback is intentionally editorial: short notes from buyers, reviewers, and operators. After live orders begin, this section can be replaced with verified buyer feedback tied to actual purchases.
“The value is not that it is another workflow. It is that the whole chain is named, documented, and ready to adapt.”
“I could see exactly where the workflow expected credentials, what it touched, and how to test it before turning it on.”
“The refund delay makes sense for downloadable files. It is clear, and it removes the awkward buy-download-refund loophole.”
Audit trail
What can be checked before launch.
- Catalog manifests validate product metadata, license tiers, file sizes, and hashes.
- RLS smoke tests verify anonymous, buyer-owned, cross-buyer, and admin-only database access.
- Payment webhook handling is idempotent and records orders, entitlements, refunds, and audit events.
- Release automation runs every 15 minutes through Supabase cron with a bearer-protected endpoint.
Payments
Secure checkout is processed by Stripe. Eligible methods appear at checkout based on your region, currency, and Stripe settings.
Wallets when eligibleLocal methods varyStripe-hosted checkout
Social
Channels opening soon.
No public social profiles are linked until the official Valzak handles are reserved. For now, reach the team at hello@valzak.ae.