Trusted by product teams
Ship faster with audited React primitives, Tailwind v4 tokens, and patterns tested in real billing, admin, and storefront flows.
➜ ~ projects/acme-saas
$
Built for the same surfaces you ship every sprint
8
Library tiers
From Starter to Developer Vault
TS
TypeScript-first
Typed components & token exports
EU
Based & invoiced
Clear B2B purchase records
1:1
Technical support
Direct email support
Scale from a lean starter kit to the full vault. Each package is versioned, documented, and licensed for commercial use.
A foundational library of 50+ essential Tailwind CSS buttons, forms, and input components.
€15.23
Premium dark-mode optimized UI components and navigation systems for modern web apps.
€26.34
Full-page SaaS landing templates and conversion-optimized marketing blocks.
€36.78
Advanced data-visualization components, including interactive tables, charts, and filtering systems.
€48.98
A specialized E-commerce UI kit featuring product grids, checkout flows, and shopping cart layouts.
€25.32
A complete Next.js admin dashboard template with integrated authentication UI and state management.
€37.13
High-performance animation presets and motion-design frameworks for interactive user experiences.
€45.09
The complete design system including Figma source files, React components, and a custom theme engine.
€68.24
A credible UI vendor should reduce risk — on accessibility, licensing, and long-term maintenance — not add it.
Layouts and components mirror how real SaaS teams structure apps — not generic marketing blocks.
Commercial terms in plain language. Know what you can ship, redistribute, and extend before you buy.
Keyboard paths, focus states, and semantic patterns are part of the kit — not an afterthought add-on.
We track Next.js App Router, Tailwind v4, and TypeScript so upgrades stay predictable.
Straightforward B2B flow — no dark patterns. You always know what you are licensing.
Match a package to your roadmap. Start small or bundle with Developer Vault for everything.
On the product page, enter your details. I’ll email you an itemized invoice and a secure payment link.
GitHub invite or ZIP delivery — then plug components into your Next.js app and align tokens with Tailwind v4.
Built like internal design infrastructure — not demo widgets. Compatibility is part of the contract.
Framework
Next.js 15 (App Router)
Styling
Tailwind CSS v4
Language
TypeScript (strict-friendly)
import { Button } from '@ziad/ui'
Tree-shakeable exports, accessible primitives, and copy-paste examples aligned with your stack.
Addressing common objections up front saves your team a procurement round-trip.
Yes. A paid commercial license covers deployment in your products for the scope defined at purchase (typically per team or per product line). Redistribution as a standalone UI product is not allowed — see the licensing page for detail.
Packages follow semver. Minor and patch updates are included for the support window attached to your tier. Major version upgrades may require a renewal or upgrade path — ask us when you are scoping Vault or enterprise use.
The kits are optimized for the App Router and Tailwind v4. Many primitives work in other React setups, but we document and test against the stack listed in Technical specs. Email us with your setup before buying if you need a compatibility check.
I usually reply within one to two business days. Email me at larbiziadalaoui@gmail.com and include your product tier and any screenshots/logs.
Leave your work email — I’ll open a thread with your address pre-filled. No third-party CRM; just a direct email.
Typical response: 1–2 business days · CET-friendly hours
I’m Ziad — an independent developer focused on high-performance frontend architecture and production-ready UI systems.
My goal is to bridge the gap between design and deployment — so you spend less time rebuilding UI and more time shipping what matters.
Abstract UI scaffolding — no stock photography, just the patterns your engineers recognize.
Choose a tier, review the commercial license, and ship with components your engineers will actually reuse — maintained against the stack you are already adopting.