Templates that ship as real projects.
Wensity templates are standalone Next.js starter projects, not theme skins or component bundles. Each one is a full app you unzip, run locally, and deploy on your own stack.
The marketplace on ui.wensity.com handles previews, pricing, checkout, ownership, and download authorization. Template source lives in separate frontend repos. After you download a ZIP, the project is yours to edit, rebrand, and ship without staying tied to Wensity runtime packages.
This page covers the buyer path: preview, purchase, download, and re-download. Template purchases are separate from component Pro plans. See Billing for how those products differ.
How templates work
Each template is a complete Next.js project with its own repo, build, and deploy target.
Marketplace pages iframe the deployed template so you can judge fit before checkout.
Downloads resolve through Wensity's authenticated download route, then redirect to a short-lived signed archive URL.
Purchased templates appear in Dashboard, Billing, and Downloads so you can fetch the archive again later.
Free vs paid
No purchase required. You still sign in before download so ownership and throttling can attach to your account.
Sold one at a time. Buying a template does not unlock Pro components, and Pro components do not unlock paid templates.
Paid template copy uses Private download · Lifetime updates. That means the ZIP is gated to your account, and registry updates can ship new archive versions over time.
Preview and buy
Open a template from /templates, read the detail page, and use the live preview. When you are ready to buy a paid template, use the purchase CTA on that page.
If you are signed out, checkout sends you through /signin?next=... first so the order attaches to the correct account.
The checkout success page is only a return path. A paid template becomes owned after Lemon Squeezy sends the webhook and Wensity records the purchase in the database.
Checkout and cart
Single-template checkout starts from the template detail page and posts to /api/checkout with the template SKU.
You can also buy multiple paid templates in one cart checkout. The cart stores template slugs locally, skips templates you already own, and sends the final slug list to the same checkout backend.
Downloads
Free and owned templates download from /api/templates/<slug>/download. That route checks your session, verifies free access or purchase ownership, applies download throttles, logs the event, and redirects to the configured archive URL.
| Rule | What it means |
|---|---|
| Use the dashboard | Download from the template page or Dashboard Downloads. Do not bookmark the signed archive URL. |
| Sign in first | Both free and paid downloads require an authenticated session. |
| Ownership is checked server-side | Paid templates return template_not_owned until the purchase is recorded. |
| Each download is logged | Events are stored for your history and abuse detection. |
After the ZIP lands, run pnpm install, then pnpm dev inside the extracted project. Treat the archive like any other starter you would version in your own Git repo.
Re-downloads
Open Dashboard, then Owned Templates or Downloads, and download the same template again when you need a fresh copy.
Paid and free template downloads share a rolling limit of 20 requests per user, per template, per 24-hour window. If you hit the limit, wait for the window to reset and try again.
Versions and updates
Template archives are versioned in storage, for example docs-site-v1.0.0.zip. The current release version is shown on the template detail page.
Contact support with your account email and template slug. Purchase records stay tied to your account, so ownership can be verified without payment receipts.