Questions

Access to the template's private GitHub repository: the full source code, its README with set-up and deploy steps, the licence and the notices for every third-party file. You clone it and it is yours to build with.

Everything the template's page lists under "What you get" is in the repository.

Checkout runs on Stripe and asks for your GitHub username. Within a few minutes of paying, GitHub emails that account an invitation to the template's private repository (you can also see it at github.com/notifications). Accept it and the code is there.

You need a GitHub account; a free one is fine. Typed the username wrong, or no invite after fifteen minutes? Write to hello@cardzo.co.in with your receipt and we will sort it out.

Fixes and improvements to a template land in the same repository you were invited to. Pull them whenever you like. You never pay again for an update to a template you own.

Every template in the gallery now, and every new one as it is released. The pass comes yearly ($199 a year) or once for good ($299). With the yearly pass you have access while it is active. See pricing for the side-by-side comparison.

Write to hello@cardzo.co.in within 14 days of buying and you get the whole payment back. No questions asked, no forms. The refund page has the details.

Checkout runs on Stripe, which emails your receipt as soon as you pay. Prices are in US dollars, and any sales tax or VAT that applies is shown at checkout before you pay.

Every template is held to the same bar and comes with the same things: every page, both themes, every state, the 3D moment and lifetime updates. So each one is $49, once.

Yes. Build as many sites as you like with one purchase, for yourself or for clients, charge for the work, and hand clients the finished site with its source code. What you cannot do is sell or share the template itself as a template, theme or kit. The licence page says it in full.

Yes, when the repository is clearly your own finished site and not offered as a template. A public copy of the template itself, changed or not, is not allowed.

Each template uses the stack that suits it: Next.js with TypeScript and Tailwind CSS, Astro with TypeScript and plain CSS, or plain HTML, CSS and JavaScript with no build step at all. Every template page says which, and each README has step-by-step deploy notes.

No. They are complete front ends. Forms show every state (sending, sent, error) and either post to an endpoint you choose or run in a demo mode until you connect one. Sign-in screens, carts and checkouts are designed in full but not wired to a provider. Each template's page and README say exactly what is and is not connected.

No. Every business, person, figure, quote and price in the screenshots and previews is sample content, marked as such in the template. All copy and images live in one content file, so replacing them is one sitting's work.

The drawings, 3D scenes and illustrations are part of the template and covered by its licence. Where a template uses a photograph, its source and licence are listed in the template's NOTICE.md and IMAGES.md; treat photographs as demo content and swap in your own.

Completeness. Every page and state is designed: light and dark themes, phone, tablet and desktop, empty, loading, error and 404 states, visible focus and reduced motion. Each template has one 3D moment drawn from its subject, and none of them loads anything from another site or tracks visitors. If you want a free place to start, Leo's starters are MIT-licensed.

Yes, please. Write to hello@cardzo.co.in with what you are building. New templates arrive in batches, and requests decide which categories come next.