What the base repository contains
The foundation, the modules that ship with it and the agent stack: what each part adds and what it needs.
This page lists what is in the base repository you clone. Nothing here is installed separately: the foundation and every module below are already in the checkout. A provider-backed feature stays unavailable until its credentials are configured.
Foundation
| Area | Available interface | Configuration or guide |
|---|---|---|
| Accounts and access | Sign-in, sign-up, verification, recovery, profile, sessions, roles, permissions and API keys | Authentication, roles, API keys |
| Billing | Products, pricing plans (/admin/plans), checkout, orders, subscriptions, customer billing pages and fulfilment plugins | Payments, products |
| Credits | Balance, reservations and ledger; settlement is performed by server-side workflows | Credits |
| AI and chat | Provider channels, scenes, text and media tasks, chat, pricing and usage | AI channels, scenes, chat |
| Files and messaging | Private assets, uploads, email templates and deliveries, notifications | Storage, email, notifications |
| Operations | Admin dashboard, users, support, analytics, audit, rate limits, countries and readiness checks | Admin console, setup |
| Extension | The plugin kernel, the list of installed plugins and /admin/plugins to switch them on and off | Plugins |
| Tooling | The kernlift deploy-target and kernlift context commands and the coding-agent skills | CLI, skills |
| Deployment | Configuration for Cloudflare, Fly.io, Railway and Docker, written by kernlift deploy-target | Runtimes and database adapters |
The example landing page, /pricing, about and contact pages are part of the foundation. The blog, editable legal content, changelog and RSS come from the CMS module below. Provider keys and business settings belong in /admin/config/* or the corresponding admin page. Environment variables are for startup and infrastructure. See configuration.
Modules in the repository
Each module is a self-contained feature with its own pages, server code, tables, copy in both languages and a validator. Its boundary is recorded in modules/<key>/module.json. The Requires column lists what else it depends on.
| Key | Kind | Requires | What it adds | Start here |
|---|---|---|---|---|
cms | Module | — | Content editor, taxonomy, revisions, legal and changelog pages, blog and RSS | CMS |
newsletter | Module | — | Newsletter, waitlist, invite and settings pages | Newsletter and waitlist |
affiliate | Module | — | Referral, commission, withdrawal and review operations | Affiliate |
image-agent | Module | agent-starter | /app/image, the Image Studio Skill (platform.image), a frame picker, the image viewer and the per-run picture limit, with settings at /admin/config/image-agent | Image agent |
agent-starter | Template | — | /app/agent, Agent API and service, skills, connectors, run workspace, sandbox and search configuration | Run the agent starter |
The Agent template runs a second service beside the web app and needs Postgres. kernlift deploy-target --agent accepts no other database. D1 can run the foundation, but cannot store Agent runs. Without the agent service the web app is complete, and the agent entries show that the service is not deployed.
image-agent is a module, but it is a plugin of the agent workbench, so it does nothing without agent-starter.
The business templates (image-studio, video-studio, image-agent, video-agent) are separate repositories, each a complete project built on this base. See Get Kernlift.
How to verify a project
- Read the
modules/*/module.jsonmanifests. Each one defines a boundary throughkind,requires,files,fragments,migrations,tables,configKeysandskillPackages. - Open
/setupfor live readiness information. A missing provider is reported as not configured. A page can exist while its external integration is not configured. - Run
pnpm validate:gate. Each capability contributes its validator.
Next steps
- Templates and derived products for how a product is built on the base.
- Build a module for the manifest fields and adding a module of your own.