Easy-to-setup, fully-featured, and customizable NextJS 15 Boilerplate.
- NextJS 15 - Full-Stack React framework
- Supabase - Database Provider
- Drizzle - ORM (TypeScript-first)
- Clerk - Authenticate your users (ban, impersonate etc.)
- Stripe - Collect Payments
- Plunk - Send Emails Programmatically
- Upstash - Redis for rate limiting
- DataFast - User Analytics for Actionable Growth (Know exactly which marketing channels are working)
- UserJot - User Feedback/Bug-Reports and Product Roadmap
- GetFernand - Fast, Calm Customer Support
- Vercel - Deployments without worrying about infrastructure (DDoS protection, etc.)
Titan includes bi-directional intelligent upgrade systems for continuous improvement.
Extract battle-tested improvements from mature projects back to Titan boilerplate.
Apply latest Titan improvements to existing projects safely and selectively.
Quick Start via Script:
# Automated setup via script
bun scripts/upgrade-titan.ts --project-path ./evolved-projects/my-saas-app
# Or via interactive prompt
bun run upgrade-titanManual Setup:
-
Clone your evolved project into the Titan workspace:
mkdir evolved-projects git clone <your-evolved-saas-project> ./evolved-projects/my-saas-app
-
Create a project-specific PRD for the analysis:
cp docs/titan-upgrade-prd-template.txt .taskmaster/docs/prd.txt # Edit the PRD to replace [PROJECT_NAME], [TIME_SPAN], etc. with your project details -
Start the analysis with Cursor:
"Analyze my-saas-app for Titan upgrades using the PRD"
Quick Start via Script (Recommended):
# From your Titan-based project directory
bun scripts/upgrade-project.ts
# Conservative upgrade focusing on security
bun scripts/upgrade-project.ts --risk-tolerance conservative --domains security,performance
# Dry run to preview changes
bun scripts/upgrade-project.ts --dry-runManual Setup:
-
Ensure clean repository (all changes committed):
git status # Should be clean -
Create project upgrade PRD:
cp docs/project-upgrade-prd-template.txt .taskmaster/docs/prd.txt # Edit PRD with your project details and risk tolerance -
Start the upgrade with Cursor:
"Upgrade my project to latest Titan using the PRD"
Safety Features:
- 🛡️ Creates
upgrade/titan-latestbranch for all changes - 🔄 Easy rollback:
git checkout main && git branch -D upgrade/titan-latest - 📊 Intelligent compatibility assessment
⚠️ Never overwrites custom business logic
Both workflows systematically analyze 20 domains including:
- Core Infrastructure: Authentication, payments, database, email systems
- Development Experience: Scripts, components, configuration, testing
- Quality & Performance: Error handling, security, optimization, monitoring
- User Experience: UX patterns, analytics, mobile responsiveness
- Integrations: APIs, background jobs, SEO, third-party services
- Titan-Specific: CLI improvements, utility patterns, app structure
All upgrades follow strict compatibility and safety rules:
- ✅ Add new features as opt-in enhancements
- ✅ Maintain existing API interfaces
- ✅ Progressive enhancement approach
- ❌ Never break existing functionality
- ✅ Selective application based on project needs
- ✅ Branch-based upgrades with easy rollback
- ✅ Incremental testing after each domain
- ❌ Never overwrite custom business logic
Upstream (Titan Improvement):
- Domain Analysis: Compare evolved project vs current Titan across all domains
- Improvement Extraction: Identify specific code improvements and optimizations
- Migration Planning: Create safe migration tasks with compatibility assessment
- Implementation: Apply improvements while maintaining backward compatibility
Downstream (Project Upgrade):
- Compatibility Assessment: Compare current project vs latest Titan
- Selective Application: Only apply relevant and safe improvements
- Safe Implementation: Branch-based upgrades with incremental testing
- Validation: Comprehensive testing before merge or rollback
- Upstream:
.cursor/rules/titan-upgrade-workflow.mdc - Downstream:
.cursor/rules/project-upgrade-workflow.mdc - Compatibility:
.cursor/rules/upgrade-compatibility.mdc - Safety Patterns:
.cursor/rules/upgrade-safety-patterns.mdc
Detailed Docs here