Clonify.io SaaS Platform

Template marketplace SaaS platform migrated from WordPress to Next.js with custom CMS and payments.

2 min read

Sabin Shrestha

Full-Stack Developer — Next.js, React & React Native

Summary

Clonify.io is a premium template and UI-kit marketplace migrated from WordPress to a Next.js and Payload CMS SaaS architecture, with a custom CMS, subscription payments, and a JSON caching layer for performance.

Problem #

The WordPress version of Clonify was slow, hard to maintain, and left digital assets (including Figma files) reachable through direct, unprotected URLs — a real problem for a business selling premium downloadable products.

Solution #

The platform was rebuilt on Next.js with Payload CMS and a GraphQL API, backed by MongoDB. A custom server-side JSON caching layer reduces database load on frequently accessed content, and a secure, permission-checked download pipeline replaced the old direct-URL asset delivery. Subscription payments were integrated to support gated, membership-only products.

Architecture #

Payload CMS manages products, collections, and subscriptions behind a GraphQL API; Next.js renders the storefront with cached JSON reads for frequently accessed pages. Purchases and subscriptions gate access to premium assets, which are served through a server-verified, temporary-access download flow rather than static public URLs.

Stack #

LayerChoiceWhy
FrontendNext.jsServer rendering, static generation, fast storefront pages
CMS / APIPayload CMS, GraphQLType-safe content and product models with a flexible query layer
DatabaseMongoDBFlexible schema for products, subscriptions, and licensing data

Problems solved #

  • Migrated legacy WordPress system into modern SaaS architecture
  • Improved page performance and loading speed significantly
  • Built custom CMS workflows for managing products and subscriptions
  • Integrated payment system for subscription management
  • Created scalable frontend and backend architecture

Lessons learned #

Cache the read path before you optimize anything else

The single biggest performance win came from caching frequently accessed CMS data as JSON rather than querying on every request — a straightforward change that had an outsized effect compared to smaller frontend optimizations.

© 2026 Sabin Shrestha