Next.js 15, PostgreSQL and Razorpay can form a workable stack for an Indian SaaS product, but the choice needs a reason: in October 2026, Next.js 15 is in Maintenance LTS while 16 is Active LTS, and the right deployment and billing design depends on your application and merchant account. Treat this as an implementation guide, not a claim that this particular combination has been tested or is used by the publisher.
Is Next.js 15 still a sensible choice for a new SaaS?
It can be, especially when a product or team has a concrete compatibility or migration reason to stay on 15. But it is no longer the current Active LTS major: the Next.js support policy checked on October 7, 2026 lists 16.x as Active LTS and 15.x as Maintenance LTS. The policy encourages production applications to use the latest Active or Maintenance LTS release. Stable does not mean equally current: Next.js called 15 stable and production-ready when it launched on October 21, 2024, while the present support classification is a separate, later consideration.
As an Amazon Associate I earn from qualifying purchases.
What to check before pinning to 15
- Choose and record the exact Next.js 15 patch version. The sources establish the major’s support status, not which patch a particular application should deploy.
- Confirm compatibility with the application’s dependencies, deployment platform, and team’s upgrade plan. The framework documentation does not establish that every project should remain on 15.
- Set a plan for moving to a supported major. Maintenance LTS is a supported track, but it is not the same status as Active LTS.
Next.js 15’s upgrade guide specifies React and React DOM 19 as minimum versions for the documented upgrade path. It also makes request-related APIs asynchronous: this includes cookies, headers, draftMode, params, and searchParams. Review code that reads these values rather than assuming older synchronous usage still applies.
Recommended Free Tools
Recheck caching behavior
Next.js 15 changed defaults: fetch requests, GET Route Handlers, and client navigations are no longer cached by default. A SaaS application may need deliberate caching for some reads, while account-specific or frequently changing data may need fresh results. Inspect each route and data access pattern and configure caching explicitly where the product requires it; do not carry forward assumptions from an earlier Next.js version.
#1 Best Overall
Which PostgreSQL version should the application run?
PostgreSQL is a database option for this stack, not a version requirement imposed by Next.js. The PostgreSQL release documentation checked on October 7, 2026 listed PostgreSQL 18 as current and versions 18 through 14 as supported. It listed these latest minor releases, each released August 13, 2026:
| PostgreSQL major | Minor release listed August 13, 2026 | Status in the checked release documentation |
|---|---|---|
| 18 | 18.6 | Supported; current major |
| 17 | 17.11 | Supported |
| 16 | 16.15 | Supported |
| 15 | 15.19 | Supported |
| 14 | 14.24 | Supported |
PostgreSQL’s versioning policy provides five years of support for a major version and recommends using the current minor release within the chosen major. Minor releases include fixes, so select a major that fits your hosting and compatibility needs, then plan to apply its current minor updates. The release information above is date-specific; check the project’s current release information when choosing or upgrading.
Make database operations part of the version decision
- Record the deployed major and minor version and how PostgreSQL is hosted.
- Check managed-service availability and any required extensions against the chosen host; those application-specific compatibility facts are not established by the PostgreSQL release list.
- Define who owns backups, upgrades, and recovery before production. A supported version alone does not describe your operational readiness.
How should Next.js be deployed?
Next.js documents running an application as a Node.js server or in a Docker container. Static export is another option, but it has limited support for features that require a server. A product that depends on server-side request handling or other server-dependent behavior should not assume a static export is interchangeable with a server deployment. Provider adapters can also have platform-specific support, so check the capabilities of the actual adapter and hosting environment.
| Deployment form | What the documentation establishes | Decision to make |
|---|---|---|
| Node.js server | Next.js can run as a Node.js server. | Confirm the target host supports the required server runtime and application behavior. |
| Docker container | Next.js can run in a Docker container. | Plan how the container will be built, deployed, and operated in the chosen environment. |
| Static export | Support is limited for server-dependent features. | Use only if the required application features work within static-export limitations. |
| Provider adapter | Support depends on the platform and adapter. | Verify the adapter’s support for the specific deployment target. |
How does Razorpay fit into checkout and payment state?
Razorpay documents Web Standard Checkout for India, Malaysia, Singapore, and the United States. That list describes where the documented checkout is available; it does not guarantee merchant eligibility, account activation, or approval for a particular business. The documented setup sequence is to create an account, generate API keys, test the integration, and replace test credentials with Live Mode API keys before accepting real payments.
Choose the checkout approach deliberately
Razorpay describes Standard Checkout as the managed checkout option and Custom Checkout as more complex and requiring development resources. Select based on the product’s actual checkout needs rather than assuming a custom flow is automatically better. Confirm account configuration and eligibility for the intended market before planning a live rollout.
Verify webhook events before changing entitlements
Payment state should be handled on the server, with webhook processing designed for verification and retries. Razorpay’s webhook guide specifies an HMAC-SHA256 signature using the webhook secret and the raw webhook body. Verify the signature before parsing or casting that body. Changing its representation first can invalidate the verification input.
- Receive the webhook request and retain the raw body for signature verification.
- Verify the signature using the webhook secret before processing the event.
- Use the unique
x-razorpay-event-idto recognize duplicate deliveries; persist processed IDs or provide equivalent idempotent handling. - Reconcile the event against the payment or subscription state before granting, changing, or revoking access.
Webhook deliveries may be duplicated, and event order is not guaranteed. Do not rely on an authorization event always arriving before capture. Design state transitions so that a repeated event cannot apply the same change twice and an out-of-order event does not incorrectly overwrite a more advanced state.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Should recurring billing use Razorpay Subscriptions?
That depends on who should control the billing schedule. Razorpay describes Subscriptions as plan-based recurring payments with a defined schedule and automatic charges. Its Recurring Payments option uses tokens and lets the merchant decide when to initiate repeated charges using its own business logic.
| Model | Who defines when charges are initiated? | Consider it when |
|---|---|---|
| Subscriptions | A plan defines the recurring schedule; charges are automatic. | The product’s billing fits a defined plan and schedule. |
| Recurring Payments | The merchant controls initiation using tokens and business logic. | The product needs merchant-controlled timing for repeat charges. |
Razorpay’s Subscriptions documentation describes plans, trials, retries, and lifecycle operations, and lists cards, UPI AutoPay, and e-mandate. Treat those as documented capabilities, not a guarantee that every method or configuration is available to every merchant. Confirm current method limits, account configuration, and eligibility for the actual account before committing to a live billing design.
What does this stack choice mean for an Indian SaaS team?
The stack is a set of compatible capabilities, not a complete product architecture or a universal recommendation. Make the choice against the application’s server requirements, data model, billing pattern, account eligibility, and deployment constraints. In particular, decide whether a project needs to stay on Next.js 15 or can move to the Active LTS major; select and operate a supported PostgreSQL release; choose a deployment form that supports the required server features; and design payment handling for verified, duplicate, and out-of-order events.
The vendor documentation establishes these individual capabilities and lifecycle details; it does not establish that this exact combination has been tested together for a specific product, or that any publisher uses it. A team considering it should validate compatibility and operations in its own application and confirm its Razorpay account’s live configuration.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
