What is Straktur?

Straktur is a production-ready Next.js codebase for building internal tools - CRMs, admin panels, portals, ops dashboards, and back-office workflows.

You buy the codebase, run it locally, and deploy it yourself. Straktur is not a hosted SaaS.

What is Straktur?

Straktur is a production-ready Next.js codebase for internal tools.

Use it when you need custom internal software for your company or clients - things like CRMs, admin panels, client portals, ops dashboards, and workflow tools.

It is built for teams who want to move fast with AI, but still need a real architecture underneath.

Not for: public SaaS products, marketing websites, e-commerce storefronts, or no-code users looking for a hosted tool.

What you actually buy

When you buy Straktur, you get a production-ready codebase - not a hosted app.

That means:

• You get the source code
• You run it locally
• You deploy it on your own infrastructure
• You customize it for your own workflows
• You keep full control over the product you build on top of it

Quick Start

Want to evaluate Straktur properly? Run it locally first.

git clone <repo-url> my-app
cd my-app
npm install
cp .env.example .env.local
# Edit .env.local with your database URL
npm run db:push && npm run db:seed
npm run dev

Open http://localhost:3000 and sign in with the demo account: [email protected] / testingpassword

Tech Stack

Documentation Structure

Getting Started

• Getting Started - Setup in 5 minutes
• Project Structure - Where things live
• Environment Variables - All config options

Core Concepts

• Architecture - How it all fits together
• Feature Modules - The feature-first pattern
• Multi-tenancy - Organization isolation

Features

• Authentication - Auth methods, RBAC, sessions
• Database - Drizzle ORM, migrations, queries
• API (oRPC) - Type-safe API layer
• UI Components - DataTable, forms, layouts
• Storage - File uploads, images
• Email - Transactional emails

Guides

• Recipes - Step-by-step tutorials
• Troubleshooting - Common errors and fixes

Philosophy

1. One way to do things - No "you can also..." alternatives
2. Feature-first - All code for a feature lives together
3. Type-safe end-to-end - TypeScript from database to UI
4. Server-first - Server Components by default
5. AI-optimized - Structure and docs designed so AI can build features without getting lost

Reference Implementation

The Clients feature (/clients) demonstrates all patterns:

Study this feature to understand the patterns, then apply them to your own features.