Kernlift

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

AreaAvailable interfaceConfiguration or guide
Accounts and accessSign-in, sign-up, verification, recovery, profile, sessions, roles, permissions and API keysAuthentication, roles, API keys
BillingProducts, pricing plans (/admin/plans), checkout, orders, subscriptions, customer billing pages and fulfilment pluginsPayments, products
CreditsBalance, reservations and ledger; settlement is performed by server-side workflowsCredits
AI and chatProvider channels, scenes, text and media tasks, chat, pricing and usageAI channels, scenes, chat
Files and messagingPrivate assets, uploads, email templates and deliveries, notificationsStorage, email, notifications
OperationsAdmin dashboard, users, support, analytics, audit, rate limits, countries and readiness checksAdmin console, setup
ExtensionThe plugin kernel, the list of installed plugins and /admin/plugins to switch them on and offPlugins
ToolingThe kernlift deploy-target and kernlift context commands and the coding-agent skillsCLI, skills
DeploymentConfiguration for Cloudflare, Fly.io, Railway and Docker, written by kernlift deploy-targetRuntimes 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.

KeyKindRequiresWhat it addsStart here
cmsModule—Content editor, taxonomy, revisions, legal and changelog pages, blog and RSSCMS
newsletterModule—Newsletter, waitlist, invite and settings pagesNewsletter and waitlist
affiliateModule—Referral, commission, withdrawal and review operationsAffiliate
image-agentModuleagent-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-agentImage agent
agent-starterTemplate—/app/agent, Agent API and service, skills, connectors, run workspace, sandbox and search configurationRun 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

  1. Read the modules/*/module.json manifests. Each one defines a boundary through kind, requires, files, fragments, migrations, tables, configKeys and skillPackages.
  2. Open /setup for live readiness information. A missing provider is reported as not configured. A page can exist while its external integration is not configured.
  3. Run pnpm validate:gate. Each capability contributes its validator.

Next steps