TheFrontKit vs BoxyHQ — SaaS Starter Kit Comparison 2026
TheFrontKit vs BoxyHQ: Which SaaS Starter Kit is Right for You?
If you're evaluating SaaS starter kits, you've probably come across BoxyHQ's open-source SaaS Starter Kit. It's one of the most popular enterprise-focused boilerplates on GitHub, with over 4,700 stars and a strong reputation for SAML SSO and SCIM directory sync.
But popularity and production-readiness aren't the same thing. Depending on what you're building—and who you're building it for—the right kit could save you months of work or leave you patching gaps for weeks.
This post compares thefrontkit's SaaS Starter Kit and BoxyHQ across the dimensions that actually matter when you're shipping a real product: UI completeness, design system, accessibility, AI readiness, and developer experience. (For a broader comparison, see Best SaaS Starter Kits 2026.)
Overview
BoxyHQ SaaS Starter Kit is a free, open-source (Apache 2.0) full-stack boilerplate built on Next.js, Prisma, and Tailwind CSS. Its core strength is enterprise identity: SAML SSO via SAML Jackson (now Ory Polis after Ory's acquisition of BoxyHQ in May 2025), SCIM directory sync, and audit logging via Retraced. The UI layer uses daisyUI for component styling and NextAuth.js for authentication.
thefrontkit SaaS Starter Kit is a frontend-focused kit built on Next.js, React, Tailwind CSS, and TypeScript. Its core strength is UI production-readiness: a complete set of accessible, token-driven components covering auth flows, app shells, dashboards, settings, forms, and notifications—with a matching Figma file and optional AI UX Kit.
They solve different problems. BoxyHQ gives you enterprise identity plumbing. thefrontkit gives you the entire frontend foundation. Understanding where each one excels helps you make the right call.
Feature Comparison Table
| Feature | thefrontkit | BoxyHQ |
|---|---|---|
| Stack | Next.js, React, Tailwind, TypeScript | Next.js 15, React 18, Tailwind, Prisma, TypeScript |
| Auth flows | Login, signup, reset, OTP — full UI recipes (bring your own auth provider) | Email/password, magic links, GitHub/Google OAuth, SAML SSO |
| SAML SSO / SCIM | Not included (pair with any SSO provider) | Built-in via SAML Jackson / Ory Polis — this is BoxyHQ's core strength |
| App shell | Production-ready sidebar, topbar, responsive layout, settings nav, dark mode | Basic layout structure |
| Dashboard components | Cards, charts, tables, activity feeds, stats | Minimal — team and SSO management screens |
| Settings pages | Account, billing, team, AI integrations, notifications, privacy | Team settings, SSO configuration |
| Design token system | Full token layer (color, spacing, radii, typography) via CSS custom properties | No token system — uses daisyUI utility classes |
| Figma parity | Yes — Figma file included, tokens synced to code | No Figma file |
| WCAG AA accessibility | Built-in: semantic HTML, ARIA, keyboard nav, focus management, contrast | Not verified — daisyUI provides basic semantics but no WCAG AA testing |
| Dark mode | Token-driven light/dark themes | Basic dark mode via daisyUI |
| AI-ready components | AI UX Kit available (streaming, citations, prompt UI) | Not included |
| Audit logs | Not included | Built-in via Retraced |
| Webhooks | Not included | Built-in via Svix |
| Billing | UI patterns included | Stripe in dependencies, but listed as "Coming Soon" |
| Database | Bring your own (frontend-focused) | PostgreSQL via Prisma |
| License | Commercial license | Apache 2.0 (free, open-source) |
| Best for | Teams that need a complete, accessible UI foundation | Teams that need enterprise SSO and identity compliance |
Where TheFrontKit Wins
1. Component Completeness
The biggest gap in BoxyHQ's starter kit is the UI layer. It uses daisyUI—a Tailwind CSS plugin that provides pre-styled component classes—for its interface. That gets you buttons, cards, and modals, but it doesn't give you the production patterns every SaaS needs: responsive sidebar navigation, multi-step forms with validation, dashboard data layouts, notification systems, or settings page hierarchies.
With thefrontkit, those patterns ship ready to use:
import { MainSidebar } from "@/components/ui/composites/main-sidebar"
<MainSidebar
activeMainNav={activeNav}
activeSection={activeSection}
onMainNavChange={setActiveNav}
onSectionChange={setActiveSection}
user={{ name: "Jane Doe", email: "jane@example.com" }}
onUpgrade={() => router.push("/pricing")}
/>
You don't build your app shell. You configure it.
2. Design Token System + Figma Parity
BoxyHQ has no design token layer and no Figma file. Colors, spacing, and typography are managed through Tailwind utilities and daisyUI theme classes. That works for prototyping, but it means rebranding requires hunting through components, and designers have no source of truth that matches the code.
thefrontkit ships with a full token system driven by CSS custom properties:
// tailwind.config.ts
colors: {
primary: {
50: "var(--color-primary-50)",
600: "var(--color-primary-600)",
},
}
To rebrand, you update token values—not component code. The included Figma file uses the same token set, so designers and developers stay in sync without a translation layer.
3. Accessibility (WCAG AA)
This is where the difference matters most for production apps. BoxyHQ's UI layer (daisyUI + react-daisyui) provides basic HTML semantics, but there's no accessibility testing infrastructure in the project—no axe-core, no pa11y, no documented WCAG compliance.
thefrontkit is built on accessibility-focused primitives from the ground up:
- Semantic HTML elements (no clickable
<div>s) - Proper roles, labels, and ARIA attributes on every component
- Visible focus rings and full keyboard navigation
- WCAG AA color contrast in both light and dark modes
- Focus management that moves to the first error on form submission
- Accessible error announcements for screen readers
If you're selling to enterprises, accessibility compliance (VPAT, Section 508, EN 301 549) is increasingly a hard requirement in procurement. Starting with WCAG AA built in saves you from a painful retrofit later.
4. AI-Ready Patterns
If your SaaS includes AI features—chat interfaces, streaming responses, prompt builders, citation blocks—thefrontkit offers an AI UX Kit that pairs directly with the SaaS Starter Kit. Same design tokens, same component architecture, same accessibility standards.
BoxyHQ has no AI-related components. (BoxyHQ the company has a separate llm-chat repository, but it's not part of the starter kit.)
5. Developer Experience for Frontend Teams
BoxyHQ is a full-stack kit. That's both a strength and a tradeoff. It bundles Prisma, PostgreSQL, NextAuth, Svix, Retraced, and SAML Jackson into one project. If you need all of those, it saves integration time. But reviews note a developer experience rating of roughly 6/10 due to the enterprise complexity, and the learning curve for understanding all the moving parts is steeper.
thefrontkit is deliberately frontend-focused. You bring your own auth provider, your own database, your own backend. The kit handles the UI patterns and design system. This makes it simpler to adopt and easier to integrate into an existing stack.
Where BoxyHQ Fits
BoxyHQ is the stronger choice if your primary requirement is enterprise identity infrastructure:
- SAML SSO is BoxyHQ's core competency. SAML Jackson (now Ory Polis) is a mature, battle-tested implementation used in production by enterprise teams. If your first customer requires SAML SSO and SCIM, BoxyHQ gets you there faster.
- Audit logging via Retraced gives you "who did what, when" tracking out of the box—a compliance requirement for many enterprise buyers.
- Directory sync (SCIM) automates user provisioning and de-provisioning from identity providers like Okta and Azure AD.
- Open-source (Apache 2.0) means no license cost and full control over the codebase. For teams that prioritize open-source infrastructure, this matters.
- Webhooks via Svix provide event-driven architecture for team and user lifecycle events.
If enterprise compliance and identity management are your primary blockers, BoxyHQ solves those problems well. The UI layer is secondary to its mission.
Pricing
BoxyHQ SaaS Starter Kit is free and open-source under Apache 2.0. Enterprise support, managed SAML, and related services are available through Ory's commercial offerings.
thefrontkit SaaS Starter Kit uses a commercial license. You get the full component library, Figma file, design tokens, and AI UX Kit add-on. See pricing for current plans.
The real cost equation isn't the kit price—it's the engineering time you save or spend. A free kit that requires 4–6 weeks of UI work to reach production quality may cost more than a commercial kit that's ready on day one.
Verdict + CTA
Here's the simple version:
- Choose BoxyHQ if enterprise SSO, SCIM, and audit logs are your primary launch requirements and you're comfortable building your own UI layer on top.
- Choose thefrontkit if you need a complete, accessible, token-driven frontend foundation and want to ship a production-quality SaaS UI in weeks instead of months.
For many teams, the answer is both approaches combined: use thefrontkit for your entire frontend—auth flows, app shell, dashboard, settings, design system—and integrate a dedicated SSO provider (including BoxyHQ's SAML Jackson / Ory Polis) on the backend when enterprise customers require it.
The two kits aren't direct competitors. They solve different layers of the same problem. The question is which layer is your bottleneck.
Ready to skip the frontend boilerplate? Explore the SaaS Starter Kit and start building your product on a production-ready foundation.
