Roadmap

ZeroStarter already ships a substantial feature set; the rest is on the way. This page lists what is Already Implemented today, then the Planned integrations (AI, background tasks, email, payments, i18n, and more) and their concepts.

Already Implemented

The following are shipped and available out of the box.

PostHog Analytics

Status: ✅ Implemented

PostHog for product analytics, feature flags, and session recordings. Configured via the NEXT_PUBLIC_POSTHOG_HOST and NEXT_PUBLIC_POSTHOG_KEY environment variables.

Available now: See the Analytics documentation for setup and usage.

Admin Console + Roles

Status: ✅ Implemented

The /console route group is a privileged admin area gated server-side by role === "admin" (via the Better Auth admin plugin and assertConsoleAccess()). Manage access from the CLI with bun run console:roles <grant|revoke|list> [email].

Available now: See the Scripts documentation for the console:roles command.

Rate Limiting

Status: ✅ Implemented

API rate limiting with hono-rate-limiter and @arcjet/ip for IP detection. Limits are per-user when authenticated (and otherwise per-IP), and authenticated users get twice the anonymous limit. Tuned via HONO_RATE_LIMIT and HONO_RATE_LIMIT_WINDOW_MS.

Dynamic OG Images

Status: ✅ Implemented

On-the-fly Open Graph image generation with takumi-js, served from the /og routes (home, docs, and blog).

Available now: See the OG Images documentation for details.

Scalar API Docs

Status: ✅ Implemented

Scalar UI at /api/docs, served from the auto-generated OpenAPI spec at /api/openapi.json, with an interactive API explorer and code samples (defaults to hono/client).

Available now: See the Type-Safe API documentation for usage details.

Better Auth Organizations

Status: ✅ Implemented

Better Auth Organizations plugin for multi-tenant SaaS: organization creation and switching, team management, member roles and invitations, last-used-organization persistence, and the organization, member, team, teamMember, and invitation tables.

Available now: See the Authentication documentation for details.

llms.txt + llms-full.txt

Status: ✅ Implemented

Auto-generated AI documentation endpoints: llms.txt (the index) and llms-full.txt (the full corpus).

Available now: See the llms.txt documentation for details.

SEO Routes

Status: ✅ Implemented

robots.ts generates robots.txt and sitemap.ts generates the sitemap for search engines.

Available now: See the robots.txt and Sitemap documentation for details.

zerostarter CLI

Status: ✅ Implemented

The published zerostarter CLI scaffolds a rebranded fork in one command: npx zerostarter@latest init fetches the latest starter, strips the sample content, rebrands it, and installs dependencies.

Available now: See the Setup guide to scaffold a project.

Public Waitlist

Status: ✅ Implemented

A public waitlist signup page at /waitlist, backed by POST /api/waitlist (with an approximate GET /api/waitlist count) and the waitlist table. A freshly scaffolded fork's home redirects here until you build your product.

Available now: See the Database documentation for the table.

---

Planned Integrations

ZeroStarter is actively evolving, and we're planning to add integrations for AI, background tasks, email, payments, and more. The sections below outline the planned features and their concepts.

AI Integration

Vercel AI SDK

Status: Planned
Priority: High

Concept: Integration with Vercel AI SDK to enable AI-powered features like chatbots, content generation, and intelligent assistants within your SaaS application.

Use Cases:

• AI-powered customer support chatbots
• Content generation and summarization
• Intelligent search and recommendations
• Natural language processing for user inputs

Implementation Notes:

• Will integrate with OpenAI, Anthropic, and other AI providers
• Type-safe AI function calling
• Streaming responses support
• Server-side and client-side AI hooks

---

Background Tasks

Inngest

Status: Planned
Priority: Medium

Concept: Integration with Inngest for reliable background job processing, scheduled tasks, and event-driven workflows.

Use Cases:

• Email sending and notifications
• Data processing and ETL jobs
• Scheduled reports and analytics
• Webhook processing
• Retry logic for failed operations

Implementation Notes:

• Type-safe function definitions
• Built-in retry and error handling
• Visual workflow builder
• Integration with Hono API routes

Trigger.dev

Status: Planned
Priority: Medium

Concept: Alternative integration with Trigger.dev for background jobs, scheduled tasks, and workflow orchestration.

Use Cases:

• Long-running background processes
• Scheduled cron jobs
• Multi-step workflows
• Integration with external APIs
• Task queuing and processing

Implementation Notes:

• TypeScript-first approach
• Visual workflow editor
• Built-in observability
• Integration with existing API structure

---

Email Services

Resend

Status: Planned
Priority: High

Concept: Integration with Resend for transactional emails, marketing campaigns, and email notifications.

Use Cases:

• User authentication emails (verification, password reset)
• Transactional notifications
• Marketing campaigns
• Email templates with React components
• Email analytics and tracking

Implementation Notes:

• React Email template support
• Type-safe email sending
• Webhook handling for email events
• Integration with background tasks for async sending

SendGrid

Status: Planned
Priority: Medium

Concept: Alternative integration with SendGrid for email delivery and marketing automation.

Use Cases:

• High-volume email sending
• Marketing automation workflows
• Email template management
• Email analytics and reporting
• Contact list management

Implementation Notes:

• REST API integration
• Template engine support
• Webhook configuration
• Deliverability optimization

---

Internationalization

i18next

Status: Planned
Priority: Low

Concept: Integration with i18next for comprehensive internationalization and localization support.

Use Cases:

• Multi-language support
• Locale-based content rendering
• Date, time, and number formatting
• Right-to-left (RTL) language support
• Language detection and switching

Implementation Notes:

• Server-side and client-side rendering
• Namespace organization
• Pluralization support
• Translation management workflow

next-intl

Status: Planned
Priority: Medium

Concept: Integration with next-intl for Next.js-optimized internationalization with type-safe translations.

Use Cases:

• Next.js App Router integration
• Type-safe translations
• Server and client components support
• Locale-based routing
• SEO-friendly URLs

Implementation Notes:

• Built for Next.js 13+ App Router
• TypeScript-first approach
• Automatic locale detection
• Integration with Next.js middleware

---

Payment Processing

Stripe

Status: Planned
Priority: High

Concept: Integration with Stripe for payment processing, subscriptions, and billing management.

Use Cases:

• One-time payments
• Recurring subscriptions
• Usage-based billing
• Invoice generation
• Payment method management
• Webhook handling for payment events

Implementation Notes:

• Stripe Checkout integration
• Stripe Elements for custom UI
• Webhook signature verification
• Type-safe Stripe API client
• Subscription management UI components

Lemon Squeezy

Status: Planned
Priority: Medium

Concept: Integration with Lemon Squeezy for simplified payment processing and subscription management.

Use Cases:

• Global payment processing
• Tax handling automation
• Subscription management
• Affiliate program support
• Digital product delivery

Implementation Notes:

• Simplified API compared to Stripe
• Built-in tax compliance
• Webhook integration
• Checkout page customization

Paddle

Status: Planned
Priority: Medium

Concept: Integration with Paddle for payment processing with built-in tax and compliance handling.

Use Cases:

• Merchant of record services
• Global tax compliance
• Subscription billing
• Revenue recovery
• Customer portal

Implementation Notes:

• Merchant of record model
• Simplified tax handling
• Webhook system
• Customer management

Razorpay

Status: Planned
Priority: Low

Concept: Integration with Razorpay for payment processing, primarily for the Indian market.

Use Cases:

• Indian payment methods (UPI, Net Banking, etc.)
• Subscription billing
• Payment links
• Refund management
• Settlement reports

Implementation Notes:

• India-focused payment gateway
• Multiple payment method support
• Webhook integration
• Dashboard integration

Polar

Status: Planned
Priority: Low

Concept: Integration with Polar for open-source monetization and subscription management.

Use Cases:

• Open-source project monetization
• Sponsorship management
• Subscription tiers
• Issue funding
• Revenue sharing

Implementation Notes:

• Open-source focused
• GitHub integration
• Subscription management
• Revenue tracking

Autumn

Status: Planned
Priority: Low

Concept: Integration with Autumn for modern payment processing and subscription management.

Use Cases:

• Payment processing
• Subscription management
• Customer portal
• Invoice generation

Implementation Notes:

• Modern API design
• Webhook support
• Dashboard integration

Creem

Status: Planned
Priority: Low

Concept: Integration with Creem for payment processing and subscription management.

Use Cases:

• Payment processing
• Subscription billing
• Customer management
• Revenue analytics

Implementation Notes:

• API integration
• Webhook support
• Dashboard access

Dodo

Status: Planned
Priority: Low

Concept: Integration with Dodo for payment processing services.

Use Cases:

• Payment processing
• Subscription management
• Customer portal

Implementation Notes:

• API integration
• Webhook handling
• Payment method support

---

Implementation Priorities

These priorities cover the Planned integrations only. For what already ships, see Already Implemented above.

Phase 1 (High Priority)

1. Resend Email - Critical for user communication
2. Stripe Payments - Essential for monetization

Phase 2 (Medium Priority)

1. Vercel AI SDK - Modern AI capabilities
2. Background Tasks (Inngest/Trigger.dev) - Async processing
3. next-intl - Internationalization

Phase 3 (Lower Priority)

1. Alternative Payment Providers - Market expansion
2. i18next - Advanced i18n features
3. SendGrid - Alternative email provider

---

Contributing

If you're interested in contributing to any of these features, please:

1. Check existing GitHub Issues
2. Open a new issue to discuss the implementation approach
3. Follow our Contributing Guidelines

---

Notes

• This roadmap is subject to change based on community feedback and priorities
• Features are implemented based on demand and community contributions
• Priority levels may shift as the project evolves
• Some features may be implemented as optional packages/plugins

For questions or suggestions about the roadmap, please open an issue or start a discussion.