License

Build anything with it. Just don't sell it back. The Vuesax license in plain words, with real examples of what's fine and what isn't.

License & terms 6 min read

Vuesax is a box of parts (components, sections, animations, backgrounds) and you get broad rights to use them. This page is the cheat sheet. It skips the legal wording and doesn’t make you guess about an “extended license”. It covers what you can do, what you can’t, and real cases on both sides.

The binding text is Terms §4. Everything here says the same thing in plainer words.

Is Vuesax part of what you're making, or is it the thing you're selling?

Part of itA button in your app, a hero on your site, an animation in your product. Go ahead, that's what it's for.
It is the productThe pieces themselves, packaged to sell or hand out, paid or free. That's the only line.

1. One license, two ways in

Every item is covered by the same license, whether it’s marked Free or needs PRO. The price is different. The rules are the same.

Three marks carry the verdicts on this page:

  • Yes. Go ahead.
  • No. Never, not even for free.
  • Careful. Allowed with a condition, or ask us first.
1.A
Free itemsEvery item marked Free, with a free account
  • Cost: Free. Sign in to copy the source.
  • Users: One, which is you.
  • Duration: As long as your account is open.
  • Use: Unlimited. Personal, commercial and client work, in as many projects as you like.
  • Inside what you build. Never as the product itself.
  • Modify: Yes. Restyle it, rename it, rewrite it.
  • An edited piece is still ours. Editing it doesn't make it yours to resell.
  • Attribution: Not required.
  • Resell / redistribute: Never. Not on its own, not in a pack, not even for free.
  • In a template or UI kit for sale: No.
1.B
PROAnnual or Lifetime. The whole catalog plus the MCP
  • Cost: Yearly, or a one-time payment. See pricing.
  • Users: One. A seat is personal.
  • Duration: Annual lasts while the plan is active. Lifetime lasts for life.
  • Use: Unlimited. Personal, commercial and client work, with no per-project fees.
  • Inside what you build. Never as the product itself.
  • Modify: Of course. Your AI editor can too, over the MCP.
  • An edited piece is still ours. Editing it doesn't make it yours to resell.
  • Attribution: Not required.
  • Resell / sublicense / transfer: Never. Your license can't be passed on.
  • If your plan ends: Shipped work stays. Products you already shipped keep working. You can't start new work with PRO items.
Why templates and UI kits are a no Some icon sets allow this if you credit them. Vuesax doesn't, because a template or UI kit built from our pieces is our catalog in another package. When you build a site for one client, Vuesax is part of that site. When you sell the same site as a template to many buyers, the pieces are what you're selling.

2. Vuesax in action: yes vs no

Still not sure where your project fits? Here are real cases, grouped by the questions people ask most.

Your projects

Yes

  1. A SaaS dashboard built on VsTable, VsButton and VsCard, sold to thousands of customers.
  2. Your portfolio, blog or side project, with no credit line anywhere.
  3. An animation in your mobile app's onboarding.
  4. A background as your hero, video intro, slide deck or printed poster.
  5. Charging whatever you want for the thing you built.
  6. Getting every piece from vuesax.com or the official MCP, so you know it's licensed.

No

  1. Starting a new project with PRO items after your Annual plan has ended.
  2. Reposting the backgrounds as a wallpaper pack or wallpaper app.
  3. Selling a background alone as an NFT, stock image or print-on-demand item.
  4. Taking pieces from a repo or site that isn't Vuesax and assuming they're licensed.
  5. Using a Free item as if "free" meant "no rules". The same license applies.

Your touch

Editing, authorship and branding.

Yes

  1. Restyle VsCard until it looks nothing like ours.
  2. Rename, refactor or port a piece to React, Svelte or anything else inside your project.
  3. Crop, recolour or composite a background into your own artwork.
  4. Let your AI editor pull and adapt pieces over the MCP. What it builds for you is yours.
  5. Say "built with Vuesax" if you feel like it. It's optional, never required.

No

  1. Saying "I made these components", even after heavy edits.
  2. Registering a component or background as your IP or trademark.
  3. Re-encoding, upscaling or stripping a watermark and calling it a new work.
  4. Using the Vuesax name or logo as if it were your brand.
  5. Training or fine-tuning a model on the catalog so it can reproduce Vuesax.

Building for others

Client work, templates and code you publish.

Yes

  1. Build a client's site or app, deliver it and bill for it, for as many clients as you have.
  2. Hand the client the finished project, with the Vuesax code inside it.
  3. Show the result in your portfolio, case studies or Dribbble.
  4. Ship a paid app or game whose interface runs on Vuesax.
  5. Make one custom theme for one client. That's client work, not a template.

No

  1. Selling a template, theme or UI kit made from Vuesax pieces on ThemeForest, Framer, Gumroad or UI8.
  2. Publishing a "Vuesax 2" or an "improved set" to GitHub or npm, free or paid.
  3. A site builder or no-code tool that offers Vuesax blocks to its users.
  4. Uploading pieces to a marketplace or snippet site.
  5. Giving a client the raw component folder "for later". They need their own seat to build new things.
Somewhere in between? Some cases need a closer look: an open-source app with Vuesax source in its repo, a starter kit for your own team, or a course that teaches with our pieces. Write to us before you publish. We'd rather say yes.

Fair play

Accounts, keys and the platform.

Yes

  1. Use your own seat for everything you build.
  2. Get a seat for each person on the team who pulls from Vuesax.
  3. Keep your MCP key in an environment variable or your editor's secret store.
  4. Revoke a leaked key from your dashboard. It stops working within a minute.
  5. Ask us when you're unsure. It's free and it's quick.

No

  1. Sharing your login or MCP key with colleagues, students or a Discord.
  2. Posting download links to anyone without a seat.
  3. Scraping, bulk-downloading or automating past rate limits or the paywall.
  4. Selling or transferring your license to someone else.
  5. Building a competing catalog with the pieces.

3. At a glance

Free itemsPRO AnnualPRO Lifetime
CostFree, with an accountYearlyOne payment
What you can copyItems marked FreeEverything, plus MCPEverything, plus MCP
Personal & commercial use Yes Yes Yes
Client work Yes Yes Yes
Modify & combine Yes Yes Yes
Attribution required No No No
Resell / redistribute No No No
Open-source repo with the source Ask first Ask first Ask first
Templates / UI kits for sale No No No
When access ends Shipped work stays Shipped work stays Never ends
Users111
Transferable No No No

4. Burn this into your brain

Four rules that cover every item, Free or PRO:

  1. Part of it, never the product. Vuesax can be inside anything you build. It can't be what you sell.
  2. Authorship stays with Vuesax. What you build belongs to you. The pieces, even edited, stay ours.
  3. Your seat is yours. It's personal and can't be transferred. It isn't a shared login.
  4. Shipped stays shipped. If your license ends, products you launched in good faith keep working.
You get a lot of freedom here. Now go build something great.Just keep the pieces inside what you make.

Want the lawyer version?

This guide gives you the plain version. The binding text, with every clause in full, is Section 4 of the Terms of Service. If the two ever seem to disagree, the Terms win, and we’ll fix this page.

Not sure about your case? Email support@vuesax.com and tell us what you’re building. We’ll give you a straight answer.