Appearance
License & Attribution
AdminVora licence
AdminVora is commercial software published by CreativeIgniter. Every tier includes the full source: SCSS, JavaScript, tokens, HTML templates, and build tooling. There is no minified-only tier.
Tiers
Two questions decide your tier: how many applications you are building, and whether the people who use them will be charged.
| Tier | Use | Apps | Paying end users | Seats | Price |
|---|---|---|---|---|---|
| Regular | One application, free to its users, that you or your client operate | 1 | No | Up to 5 | $39 |
| Regular Plus | Up to five such applications — five clients, or five internal projects | 5 | No | Up to 25 | $179 |
| Extended | One commercial application sold or licensed to end users (SaaS, product) | 1 | Yes | Up to 5 | $599 |
| Extended Plus | Up to five commercial applications | 5 | Yes | Up to 25 | $1,299 |
| OEM | Unlimited applications, redistribution rights, white-label | ∞ | Yes | Unlimited | Contact us |
Prices are in USD, exclusive of VAT and sales tax, and are per legal entity. The tier you need is the cheapest row whose answers are both true — if your end users pay to use what you build, no amount of Regular licences covers it.
A developer is someone who touches the source while building or maintaining the application. People who use, test, review or deploy it are not counted. LICENSE.md §2 is the binding wording.
Refunds
Every tier except OEM carries an unconditional 30-day refund, for any reason. You do not have to justify the request, and it is not refused because you downloaded the files and decided against them.
A refund ends the licence: stop using AdminVora, delete your copies, and take it out of anything you have not already shipped. Applications you had already put in front of their users before the refund are unaffected — those users keep them. LICENSE.md §14 is the binding wording.
Where you bought through a reseller, request the refund through that reseller.
What every licence permits
- Use in commercial and non-commercial applications
- Modify the source freely
- Use across development, staging, and production environments
- Distribute as part of a functioning application
- Use in applications behind a login or paywall
- Updates and support for the window recorded on your invoice (renewal optional; your version keeps working indefinitely)
- Use of an AI coding assistant while you build — what is not permitted is handing the source to a third party to train on
What no licence permits
- Redistributing AdminVora as a template, theme, UI kit, or component library — modified or not
- Reselling, sublicensing, or including it in a product whose primary value is the UI itself
- Publishing the source to a public repository
- Using it to create a competing admin template
- Sharing licence keys outside the licensed organisation
- Supplying the source as training data for a machine-learning model, or into any dataset built for that purpose
The distinction
| ✅ Permitted | ❌ Not permitted |
|---|---|
| Building a CRM for a client with AdminVora | Selling "AdminVora Pro Edition" |
| A SaaS product whose UI uses AdminVora | A theme marketplace listing derived from it |
| An internal tool for your company | A public GitHub repository containing the source |
| A WordPress plugin's admin screens | A WordPress theme sold as a product |
| An open-source app that bundles the compiled CSS/JS | An open-source repository containing src/ |
Note — the test is whether the customer is buying your application or the interface. If the interface is the product, that is redistribution.
Open-source projects
Contact licensing@creativeigniter.com. Free Regular licences are granted to non-commercial open-source projects, on the condition that src/ is not committed to the public repository. The compiled dist/ output may be committed.
Full terms
LICENSE.md in the distribution is the authoritative document. This page is a summary and does not override it.
Third-party software
AdminVora vendors the packages below and nothing else. Every one is permissive (MIT, BSD-2, BSD-3, Apache-2.0, or OFL-1.1 for the fonts) and safe to redistribute inside a commercial product.
NOTICE.md is generated by npm run vendor from tools/vendor.manifest.json, reproduces each licence in full, and is copied into dist/ by the build, which fails if it is missing. It must be distributed with your application: naming a licence is not attribution, and MIT, BSD and Apache-2.0 all require the notice itself to travel with the copy.
The table is generated. npm run check:licenses fails the build if it disagrees with the manifest in either direction — software listed that does not ship, or software shipping that is not listed.
| Package | Version | Licence |
|---|---|---|
@codemirror/autocomplete | 6.20.3 | MIT |
@codemirror/commands | 6.11.0 | MIT |
@codemirror/lang-json | 6.0.2 | MIT |
@codemirror/language | 6.12.4 | MIT |
@codemirror/lint | 6.9.7 | MIT |
@codemirror/search | 6.7.1 | MIT |
@codemirror/state | 6.7.1 | MIT |
@codemirror/view | 6.43.9 | MIT |
@fontsource-variable/fraunces | 5.3.0 | OFL-1.1 |
@fontsource-variable/inter | 5.3.0 | OFL-1.1 |
@fontsource-variable/jetbrains-mono | 5.3.0 | OFL-1.1 |
@fontsource-variable/nunito | 5.3.0 | OFL-1.1 |
@fontsource-variable/plus-jakarta-sans | 5.3.0 | OFL-1.1 |
@fontsource-variable/space-grotesk | 5.3.0 | OFL-1.1 |
@lezer/common | 1.5.2 | MIT |
@lezer/highlight | 1.2.3 | MIT |
@lezer/json | 1.0.3 | MIT |
@lezer/lr | 1.4.10 | MIT |
@marijn/find-cluster-break | 1.0.3 | MIT |
apexcharts | 3.54.1 | MIT |
codemirror | 6.0.2 | MIT |
crelt | 1.0.7 | MIT |
filepond | 4.32.12 | MIT |
filepond-plugin-file-validate-size | 2.2.8 | MIT |
filepond-plugin-file-validate-type | 1.2.9 | MIT |
filepond-plugin-image-preview | 4.6.12 | MIT |
glightbox | 3.3.1 | MIT |
imask | 7.6.1 | MIT |
leaflet | 1.9.4 | BSD-2-Clause |
quill | 2.0.3 | BSD-3-Clause |
sortablejs | 1.15.6 | MIT |
style-mod | 4.1.3 | MIT |
tabulator-tables | 6.5.2 | MIT |
tom-select | 2.6.2 | Apache-2.0 |
w3c-keyname | 2.2.8 | MIT |
Seventeen of those rows are CodeMirror 6, which is not one package but a tree of them. They are listed individually because each carries its own copyright and each licence has to be reproduced.
Correction — this page used to list about thirty-five libraries. It was written as part of the 1.0.0 specification, so it named what the product intended to bundle rather than what it does: Bootstrap, Chart.js, ECharts, Grid.js, DataTables, jQuery, Flatpickr, noUiSlider, Dropzone, Cropper.js, TipTap, Prism, FullCalendar, markdown-it, Swiper, SweetAlert2, SimpleBar, Motion One, Lenis, jsVectorMap, DOMPurify, Day.js — and GSAP, which had a section of its own explaining how to comply with the GreenSock "No Charge" licence. None of them has ever been in the build.
That is a worse error on this page than on any other. Over-claiming invites a licence question with no answer — a purchaser's legal review asking how a restrictively licensed library is being redistributed, when it is not being redistributed at all.
npm run check:licensesnow holds the list to the manifest.
Fonts, bundled
Six font families ship in vendor/fonts/, vendored from @fontsource-variable and pinned with checksums in tools/vendor.manifest.json. Their @font-face rules are src/scss/base/_fonts.scss.
| Family | Source | Licence |
|---|---|---|
| Inter | rsms.me/inter | OFL-1.1 |
| Plus Jakarta Sans | tokotype/PlusJakartaSans | OFL-1.1 |
| JetBrains Mono | jetbrains.com/lp/mono | OFL-1.1 |
| Fraunces | undercasetype/Fraunces | OFL-1.1 |
| Space Grotesk | floriankarsten/space-grotesk | OFL-1.1 |
| Nunito | googlefonts/nunito | OFL-1.1 |
The SIL Open Font License 1.1 permits commercial use, embedding and redistribution. Its conditions travel with the files: keep the copyright notice and licence (both are reproduced in full in NOTICE.md, generated by npm run vendor), do not sell the fonts on their own, and rename a font you modify. Shipping them inside an application built on AdminVora meets all three.
Icons — authored, not bundled
No icon set is bundled either. The 187 icons in the UI kit are inline <svg> written into the markup on a 24 × 24 stroke grid, which is what lets one sit inside a button and inherit that button's colour, weight and size with no extra rule. There is no sprite, no icon font, and no icon package in the manifest.
Answered by the Licensor on 30 August 2026; expanded 4 September 2026: all 160 paths were original artwork. The Licensor confirmed the original 80 were drawn for this product on the 24 × 24 stroke grid, not traced from Tabler, Phosphor or any other set. The additional 80 were authored directly for AdminVora during the 4 September expansion.
The set is 178 as of 5 September 2026, and the eighteen additions carry the same provenance without needing a fresh answer. They were not drawn: each was promoted out of the pages, where 272 glyphs had been pasted into markup rather than added to the gallery. The geometry is unchanged and was already in this repository under the Licensor's ownership; only a name and a file were added. Nothing was traced, and nothing was taken from a third-party set — a Tabler evaluation on the same day was rejected precisely to keep this statement true.
The question was held open — and could not be closed by reading the repository — because the obligation follows the artwork rather than the dependency: a path traced by hand from an MIT original owes that set its copyright notice in the distributed notices even though no package is installed, and a finished SVG does not record how it was made. Nothing is owed, no notice is added here, and the icons are an asset the Licensor owns rather than one licensed in — which is the form the EULA should state it in.
Map tiles
Leaflet is a library, not a tile provider, and this build ships no default tile provider at all. data-av-map-tiles is required and has no fallback, because a default would make every map in the product issue requests to a third party's servers on the consumer's behalf — deciding, for them, what happens to their users' IP addresses and what their CSP has to allow.
A map with no tiles still pans, zooms and shows its markers.
| Provider | Terms |
|---|---|
| OpenStreetMap | Free, attribution required, and governed by a tile usage policy that does not permit production traffic |
| CARTO, Mapbox, Stadia and similar | Commercial tiers, attribution required, terms vary |
| Self-hosted (TileServer GL) | Your infrastructure, your terms |
Whatever you choose, the attribution control is a condition of the data licence and must not be removed.
Demo content
| Asset | Reality |
|---|---|
| Photographs | None. The product wells are generated SVG placeholders — npm run images, from tools/placeholders.manifest.json. No raster image ships except Leaflet's own marker PNGs, which are BSD-2 and covered by NOTICE.md |
| Avatars | CSS and initials, not portraits |
| Logo, wordmark, favicon | Original SVG, by CreativeIgniter — yours to replace, not to reuse as a mark (see Trademarks) |
| Company names, people, figures | Fictional |
This page previously listed Pravatar avatars and Unsplash product photographs, with a warning to replace them before production. The avatars are gone for good — they are CSS and initials.
The photographs are worth the longer note, because for a period this table was wrong. Twenty Unsplash photographs were vendored into
src/img/products/on the same terms as a library — pinned by source URL and SHA-256 — while this row read "None". Pinning was the right machinery aimed at the wrong risk: every free-stock licence, Unsplash and Pexels and Pixabay alike, permits use and prohibits redistributing the files, and redistribution is precisely what this repository does. The photos shipped insidedist/, propagated into all eight starter kits, and landed in each customer's public asset root, from which their clients redistributed them again. Attribution was never the bar; no attribution line makes a redistributable file redistributable.They were replaced with generated placeholder wells on 25 August 2026. The row is true again, and the principle it states is the reason: a template that ships stock imagery hands every buyer a licence they did not read and cannot audit.
Your obligations
When you ship an application built with AdminVora:
- [ ] Include
NOTICE.md(or equivalent) somewhere accessible — an "Open source licences" page is the usual approach - [ ] Keep the tile provider's attribution control if you use Leaflet — this build sets no default provider, so whichever you choose, its terms are the ones you agreed to
- [ ] Self-host the three fonts if you want the intended typography, and carry their OFL notices
- [ ] Do not remove copyright headers from vendored files
- [ ] Do not publish AdminVora's
src/to a public repository
An "Open source licences" route rendering NOTICE.md satisfies the attribution requirement for every bundled dependency in one place.
php
// Laravel example
Route::view('/licences', 'legal.licences')->name('licences');blade
<div class="av-prose">
<h1>Open source licences</h1>
{!! Str::markdown(file_get_contents(base_path('NOTICE.md'))) !!}
</div>Trademarks
"AdminVora" and "CreativeIgniter" are trademarks of CreativeIgniter. A licence to use the software does not grant a licence to use the marks.
You may:
- State that your product is "built with AdminVora"
- Reference AdminVora in documentation and technical materials
You may not:
- Use the AdminVora name or logo in your product name, logo, or domain
- Imply endorsement or partnership
- Register a confusingly similar mark
Contact
| Topic | Address |
|---|---|
| Licensing questions | licensing@creativeigniter.com |
| Open-source licence requests | licensing@creativeigniter.com |
| Commercial support | support@creativeigniter.com |
| Security | security@creativeigniter.com |
| Accessibility | a11y@creativeigniter.com |
This page is a summary for convenience. LICENSE.md in the distribution is the authoritative agreement and takes precedence where the two differ. It is not legal advice.