Introduction

What this is #

next-starter is the foundation we use for every web build at raxel — a Next.js application with the unglamorous parts already wired up: authentication, database, a backoffice route group, an email pipeline, and a deploy story. You clone it, fill in your env, and you're shipping by lunch instead of yak-shaving for a week.

It exists because every "modern starter" we tried either bundled the wrong choices or stopped at the demo. This one is the version we actually want to start from — and raxel.studio itself runs on it, so the codebase you'd inherit is the same codebase backing the site you're reading.

Who it's for #

Teams who:

• want a real Next.js app, not a marketing demo
• prefer a small, opinionated set of libraries over a config menu
• intend to ship to production, not localhost

If you want a no-decisions, batteries-omitted scaffold, this is heavier than you need. If you want a 200-package framework, this is lighter. The middle path: just enough to start, nothing you'll have to rip out.

What's not here #

We've kept the set deliberately tight. No analytics SDK. No feature-flag service. No CMS adapter. No queue worker. Add them when you need them; the starter doesn't pre-decide.