Skip to main content
This is the main entry point for KilatKoding documentation. It is written for two audiences: non-technical readers who want to understand what is already included, and developers who will run or modify the code.

​
What KilatKoding is

KilatKoding is a Next.js SaaS boilerplate built for the Indonesian market. You do not start from a blank app. You start from a codebase that already includes a landing page, auth, dashboard, billing, admin, email, blog, AI, and testing. This documentation reflects the kilatkoding-src repository as of March 19, 2026.

​
Choose the right reading path

If you are opening this docs site with a specific goal, start with the path that best matches your role.

​
For founders or non-technical operators

  1. Product overview
  2. KilatKoding use cases
  3. KilatKoding comparison
  4. KilatKoding FAQ
  5. Ready-to-use AI prompts
  6. What you can do without code vs what needs a developer
  7. Launch checklists

​
For developers who want a fast setup path

  1. Getting started
  2. Preset recipes by use case
  3. Ready-to-use AI prompts
  4. Local setup
  5. Services setup
  6. Environment variables
  7. Vercel deployment

​
For agencies or freelancers who want to rebrand it

  1. KilatKoding use cases
  2. KilatKoding comparison
  3. Preset recipes by use case
  4. Customization
  5. Rebranding recipes
  6. Feature toggle matrix
  7. End-to-end flows

​
For technical audits or handovers

  1. Features and routes
  2. Architecture
  3. API reference
  4. Database map
  5. Operational runbook

​
Start with the core pages

Understand the product

See what is already included, who it fits, and which areas are still roadmap items.

Choose a use case

Match KilatKoding to scenarios such as subscription SaaS, client portals, pre-launch waitlists, or AI products.

Compare starting points

Judge whether KilatKoding fits better than starting from scratch, using a UI-only template, or building fully custom.

Read the FAQ first

Get fast answers to common questions about setup, billing, AI, rebranding, and current limitations.

Use copy-ready AI prompts

Open ready-to-send prompts for non-technical users, developers, and agencies when you want more directed AI help.

Define ownership

See which areas are safe to manage without code and which areas still need a developer.

Plan your setup

Decide which services and feature modules you want to enable before editing configuration.

Run it locally

Follow the local setup steps for Windows, macOS, or Linux.

Adapt it to your brand

Change product naming, navigation, pricing, pages, design presets, email, and content.

​
Additional docs that matter before launch

These pages usually become important once the project moves into implementation, QA, or launch prep.

Preset recipes by use case

Copy a more prescriptive starting point for waitlists, subscription SaaS, member portals, AI SaaS, or white-label client work.

Launch checklists

Use different checklists for waitlists, subscription SaaS, AI SaaS, or client portals before going live.

Services setup

Connect Supabase, Resend, Midtrans, Doku, and AI services based on the combination you need.

Environment variables

Review required env vars, optional env vars, and safe toggle combinations.

Vercel deployment

Follow the production deployment flow, fill env vars in Vercel, and run post-deploy checks.

Testing recipes

Run manual test scenarios for auth, payments, webhooks, waitlists, and AI features.

Operational runbook

See what to check when emails fail, webhooks do not arrive, or subscriptions do not activate.

​
Docs for changing the product with less guesswork

Rebranding recipes

Follow goal-based tutorials such as renaming the product, disabling AI, or turning the landing page into an agency site.

Feature toggle matrix

See the effect of each toggle on the UI, routes, env vars, and service setup before disabling features.

End-to-end flows

Understand auth, checkout, payment webhook, avatar upload, and AI usage flows from a product perspective.

Components and UI

Review the component structure, layout patterns, and UI areas that are most often changed during rebranding.

AI and tooling

Check the AI surface area, provider integration, and tooling touchpoints you should review before custom work.

​
Technical and operational reference

If you are auditing the codebase, handing it over to another developer, or need more technical answers, start here.

Features and routes

Get a map of the existing pages, key routes, and modules already included in the boilerplate.

Architecture

Review the folder structure, boundaries between layers, and main implementation patterns in the app.

API reference

Check important endpoints, auth requirements, request shapes, response shapes, and common error cases.

Database and storage

Understand how Supabase is used for auth, primary data, avatars, and storage.

Database map

Learn the main tables, relationships, and database areas most often touched during customization.

Glossary

Read friendly definitions for terms such as webhook, service role, RLS, migration, and rate limit.

Current limitations

Review areas that are not automatically ready for every use case so expectations stay realistic.

Testing and deployment

Get the higher-level view of testing workflow, CI, and release setup already present in the repo.

Troubleshooting

Find quick fixes for setup errors, incorrect env configuration, or service integrations that do not work yet.

​
Who this documentation is for

  • founders or non-technical operators who want to understand what is ready to use,
  • developers who need to run the project and decide which features stay enabled,
  • freelancers or agencies who want to rebrand the boilerplate for clients.

​
What is already in the repository

  • a complete marketing site with supporting pages such as about, compare, roadmap, status, waitlist, contact, privacy, and terms
  • Supabase auth with email/password, Google OAuth, Magic Link, email verification, and password reset
  • a user dashboard with profile, billing, payment history, and avatar support
  • an admin dashboard with revenue metrics, role management, webhook logs, and audit trail
  • Midtrans and Doku integrations with webhook verification
  • transactional email through Resend and React Email
  • an MDX blog with frontmatter, tags, and reading time
  • AI routes for chat and generate, including usage tracking
  • testing with Vitest, Testing Library, Playwright, and GitHub Actions CI
If this is your first time opening the docs and you are not sure where to begin, read Product overview, KilatKoding use cases, KilatKoding comparison, then continue to Ready-to-use AI prompts, Preset recipes by use case, and Getting started.