StarterNext.js 16/Hono API/Neon Postgres

Next Hono Neon Starter

Production-ready fullstack template for teams that want a typed Next.js app, Hono API, Neon database, auth, organization scoping, and CLI integration from day one.

3

feature modules

2

app surfaces

1

typed API boundary

starter/system

Next.js App

Server Components + dashboard

Hono API

/api/tasks /api/ocr /api/api-keys

Request path
web session - organization scope - application command
CLI token - API key middleware - same domain service

DB

Drizzle

Auth

Neon

Tests

Vitest

Starter contents

Ship the application shell, not just a demo page.

The starter includes the web app, API routes, database access, auth boundaries, API key flow, and CLI client as connected pieces.

Next.js app router

Server Components, route groups, onboarding, dashboard, settings, and authenticated layouts are already wired.

Hono API boundary

Feature routes expose task, API key, and OCR endpoints through one Next.js route handler.

Neon + Drizzle

Schema, migrations, serverless Postgres client, and transaction-friendly repository patterns are in place.

Auth and organizations

Neon Auth sessions, organization activation, and scoped dashboard access are part of the default flow.

API key access

CLI and external clients can authenticate with managed API keys without sharing browser session state.

CLI integration

The Ink + Pastel CLI talks to the same Hono API for task and OCR workflows.

Optional AI workflow

OCR is included as a real feature slice.

Templates, extraction jobs, batch processing, result previews, Vercel Blob storage, and AI SDK providers are structured as a feature module.

Templates

Define schemas once and reuse them for consistent document extraction.

Extract

Submit documents and receive structured data through AI-backed providers.

Batch Processing

Track multi-document work through batch, job, result, and export screens.

Built for extension

Use it as the first commit for a product, not a throwaway scaffold.

The default app already has the boundaries most teams add later: feature modules, CQRS use cases, tests, auth, database migrations, and an HTTP client surface.