Open-Source Ecommerce · reliverse

relivator

Relivator is an MIT-licensed Next.js 15 and React 19 ecommerce template featuring built-in authentication via better-auth, payment processing through Polar, and a modern UI stack with shadcn/ui and Tailwind CSS. It provides a pre-configured full-stack foundation using Drizzle ORM, Neon PostgreSQL, and includes developer tools like ESLint and Biome for rapid deployment.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/reliverse/relivator

1.6k

GitHub stars

278

Forks

TypeScript

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	reliverse/relivator
Owner	reliverse
Primary language	TypeScript
License	MIT — OSI-approved
Stars	1.6k
Forks	278
Open issues	5
Latest release	1.4.5 (2025-05-07)
Last updated	2025-10-04
Source	https://github.com/reliverse/relivator

What relivator is

A TypeScript-based ecommerce starter kit combining Next.js 15, React 19, Drizzle ORM with Neon PostgreSQL backend, better-auth for authentication, and Polar for payment/subscription management. Includes shadcn/ui component library, TailwindCSS 4.1, form handling via React Form and ArkType, and analytics via Vercel. Designed for server-side rendering and App Router patterns.

Quickstart

Get the relivator source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/reliverse/relivator.git2cd relivator3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Rapid ecommerce MVP development

Teams needing a production-ready ecommerce foundation can launch within days using pre-wired authentication, payment processing, and database schema. Polar integration handles subscription billing automatically.

SaaS with subscription monetization

Projects requiring tiered pricing, customer portals, and webhook-based subscription lifecycle management benefit from native Polar integration and better-auth seamless user flows.

Next.js skill building or portfolio projects

Developers learning modern full-stack patterns gain exposure to Next.js 15 App Router, TypeScript, ORM patterns, and authentication best practices in a functional, deployable context.

Implementation considerations

Environment variable configuration is mandatory; `.env.example` must be populated with Polar tokens, Neon credentials, and other service keys before `bun dev` runs.
Database schema migration via `bun db:push` and schema-driven ORM (Drizzle) mean schema changes require code updates and migrations; plan version control around DB changes.
Better-auth configuration in `src/app.ts` requires manual customization for custom user fields, OAuth providers, or role-based access; no low-code admin UI provided.
Deployment targets Vercel natively; self-hosted deployments (AWS, GCP, etc.) require additional DevOps configuration for serverless or container runtimes.
AI-ready codebase (mentioned as 1.4.0+) implies cursor/AI-IDE optimization; manual developer experience may differ if using traditional editors.

When to avoid it — and what to weigh

Stripe or Clerk-dependent workflows — If your existing payment stack or authentication provider is Stripe or Clerk, use the separate 'Versator' fork instead. Relivator is specifically Polar + better-auth focused.
Heavy customization or legacy system integration — Projects requiring extensive custom backend logic, third-party API integrations, or migration from monolithic systems may find the opinionated stack constraints limiting.
Multi-tenant or complex marketplace requirements — Relivator targets single-store ecommerce. Complex marketplace logic, vendor management, or multi-tenancy features are not baked in and would require significant architectural additions.
Enterprise-scale performance demands — While suitable for mid-market stores, projects requiring advanced caching, CDN optimization, or handling millions of concurrent users need additional infrastructure beyond the template baseline.

License & commercial use

MIT License (MIT). Permissive open-source license permitting commercial use, modification, and distribution with attribution required. No warranties provided.

MIT license explicitly permits commercial use. However, verify that dependencies (next.js, react, drizzle-orm, shadcn/ui, better-auth, Polar SDK) are also commercially compatible in your use case. No commercial support or SLA provided by the project maintainer; community Discord channel available.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Strong
Assessment confidence	High

Security considerations

No explicit security audit or CVE history provided. Threat surface: database credentials (Neon, Polar tokens) must be protected in environment variables; webhook signing via POLAR_WEBHOOK_SECRET is documented but implementation details not visible. Better-auth is a third-party auth library; review its security posture independently. OWASP considerations (input validation, CSRF, rate-limiting) not documented; assume defaults from Next.js and libraries apply.

Alternatives to consider

Versator (sibling template)

Same maintainer; swaps Polar+better-auth for Stripe+Clerk. Choose if your payment/auth ecosystem differs.

Medusa (open-source ecommerce platform)

Headless commerce engine with GraphQL API and modular plugins. Heavier-weight and more extensible than a template; better for complex B2B or multi-vendor scenarios.

Shopify Plus / Shopify Build (hosted solutions)

Managed SaaS alternative eliminating infrastructure and backend maintenance. Trade-off: less code ownership and higher operational cost.

Software development agency

Build on relivator with DEV.co software developers

Evaluate Relivator's fit for your stack. If Polar and better-auth align with your payment/auth strategy, this template can accelerate your launch. For Stripe or Clerk-based workflows, explore Versator instead. Discuss architecture and customization needs with our team.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

commerce nextjs-woocommerce requery

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Ecommerce Ecommerce Development Web App Development Cloud Deployment & DevOps Talk to DEV.co

relivator FAQ

Can I use Relivator with Stripe instead of Polar?

Not natively. The template is built for Polar. Use the Versator fork, which features Stripe + Clerk integration. Porting Stripe yourself requires significant rework of payment logic and webhook handlers.

What database does Relivator support?

Primary: Neon PostgreSQL. Drizzle ORM support extends to other PostgreSQL, MySQL, and SQLite, but ecosystem examples and setup scripts target Neon. Supabase noted as work-in-progress.

Is Relivator suitable for a production store?

It's a template, not a platform. It provides a functional foundation, but production readiness depends on your customization, testing, security hardening, and ops setup. Basic ecommerce workflows (checkout, subscriptions, auth) are present.

How do I host Relivator?

Vercel is the intended target (native Next.js support). Self-hosting requires a Node.js runtime, PostgreSQL database, and environment variable configuration. Docker/Kubernetes setup not provided in repo.

Software development & web development with DEV.co

Adopting relivator is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source ecommerce software in production.

Ready to build your ecommerce platform?

Talk to DEV.co Schedule a Consultation