Crescentek

Custom Framework Development

When CMS can't, custom code can.

Next.js, React, Node.js, Postgres, and the rest of the modern stack — for Irish businesses building real applications, not brochures. Performance, scale, ownership. The upgrade from 'on a platform' to 'built properly'.

Based in Ireland
GDPR compliant
Reply within 1 working day
crescentek-app — route.ts
Explorer
app
api
products
route.ts
layout.tsx
page.tsx
components
lib
package.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
import { NextResponse } from 'next/server'
import { db } from '@/lib/db'
// GET /api/products — fetch Irish store catalogue
export async function GET(request: Request) {
const { searchParams } = new URL(request.url)
const region = searchParams.get('region') ?? 'IE'
const products = await db.products.findMany({
where: { region, active: true },
orderBy: { createdAt: 'desc' },
})
return NextResponse.json({ products })
}
main·TypeScript · Next.js 15
Build passing
When custom earns its keep

Four situations where custom frameworks win.

Most projects don't need custom — a CMS or SaaS platform does fine. But when these conditions apply, bespoke pays back many times over.

Performance matters genuinely

Sub-second page loads across millions of visits. CMS-driven platforms can't match what a bespoke framework delivers. Ecommerce and content brands with real scale need this.

Off-the-shelf can't solve it

Your product isn't a template. The flows, logic, or data model don't map cleanly to Shopify or WordPress. When the square peg won't fit, bespoke is the answer.

Control is non-negotiable

No SaaS vendor holding your business hostage at renewal. Your code, your infrastructure, your data. Strategic businesses own their stack — they don't rent it.

Scale is a real concern

100k users per month is fine on most platforms. 10 million? You'll hit walls. Custom frameworks give you the architecture to grow without rebuilding every two years.

The stack we actually build on

Three layers — modern, proven, not trendy.

We don't chase the new framework every six months. These are the technologies we actually deliver with — mature enough to trust, modern enough to last.

Frontend frameworks

The app layer users see

Next.js 15 (React) — our default
Remix — when it's a better fit
Astro — for content-heavy sites
Vue + Nuxt — for Vue-oriented teams
Tailwind + shadcn/ui for UI
Backend & data

The systems underneath

Node.js / TypeScript
Postgres — our preferred DB
Supabase for auth + realtime
Redis for caching
Pinecone / pgvector for AI features
Infrastructure & ops

Where and how it runs

Vercel / Cloudflare Workers
AWS / GCP for heavier workloads
GitHub Actions CI/CD
Sentry for monitoring
Proper staging environments
How we decide the framework

Next.js by default, alternatives when they fit.

Framework religion is a hiring drama waiting to happen. We pick the tool that matches the project — not the one our team's currently excited about.

When we choose Next.js

Most web apps and marketing sites

Server components + RSC for performance
File-based routing maps to sitemap
Edge deployment for global users
Mature ecosystem & hiring pool
Incremental static regeneration where it fits
When we choose alternatives

Context-specific picks

Astro — for content-first sites with less interactivity
Remix — for form-heavy apps with complex state
Vue + Nuxt — for teams already in Vue
Custom Go/Rust — for high-perf backends
SvelteKit — for component-heavy small apps
When we stop at Next.js for frontend

And reach further for backend

Postgres + Drizzle/Prisma ORM
Separate API service for complex domains
Microservices when the org is big enough
Queue workers for async heavy lifting
Dedicated auth service for enterprise
Is it a fit?

Custom frameworks are more ambitious than CMS builds.

They take longer, cost more up front, and require ongoing dev capability. For the right projects, they're transformational. For the wrong ones, they're a regret.

Right fit
We should talk if…
You've exhausted what CMS/SaaS platforms can do
Performance, scale, or custom logic genuinely matters
You have — or will have — real engineering leadership
You want to own the stack, not rent it
You're building a product, not a brochure
Not a fit
We'll point you elsewhere if…
A simple brochure site — WordPress or Squarespace is cheaper, faster
Standard ecommerce — Shopify will serve you better
You have no engineering capability to maintain it
Budget is very limited — custom frameworks cost more upfront
Speed to launch is the #1 priority over everything else
When custom makes sense

Common custom framework scenarios.

Where building on Next.js, Remix, or similar earns its place over off-the-shelf.

Custom SaaS product builds
High-performance marketing sites
Headless commerce frontends
B2B internal tools
Mobile-first web apps
Realtime apps (chat, dashboards)
AI-powered applications
Multi-tenant platforms
Common questions

Custom framework questions, honestly answered.

The questions Irish SMBs ask us most often.

React alone gives you a frontend library; Next.js adds routing, server-side rendering, APIs, and a deployment story. 'Going custom' with Next.js means you're building a real application — not just a static site. It's the right choice when what you're building is actually an app, not a page.
Plenty of times. If your site is essentially a brochure with some content, WordPress or Squarespace is faster and cheaper. If you're selling products online with standard flows, Shopify will serve you better. Custom is right when platforms can't solve it — or when owning the stack genuinely matters strategically.
More than SaaS on month one, often less over 3-5 years depending on scale. A Next.js app on Vercel costs maybe €20-500/mo in hosting vs Shopify at €29-2000+/mo. Plus you own it. But dev maintenance (updates, security, features) is ongoing — budget accordingly.
Legitimate middle ground. You get Shopify's commerce engine or WordPress's CMS with a custom Next.js/Astro frontend — performance and design freedom without building commerce/content management from scratch. We do these where they genuinely fit.
Depends on the setup. Vercel/Netlify for frontend is typically simple and reliable — we handle via retainer or you own it. Heavier apps on AWS/GCP need more serious DevOps. We document everything at handover so you can hire your own team or stay on retainer with us.
Genuine concern — some agencies lock clients in. Our approach: open-source frameworks (no proprietary platform), clean code with documentation, repos in your GitHub org, hosting in your accounts, no custom CMS only we can work on. If we disappear, your next agency picks up cleanly.
Works well with

Services that pair with this one.

Thinking of going custom?

Free 30-minute call. Tell us what you're building — we'll tell you honestly if custom is the right call, or if a CMS/SaaS platform would serve you better.

Reply within 1 working day GDPR compliant Based in Ireland