Krantho is in active development and not yet published to npm. Read what that means today.
esc

Search the documentation and product pages. Type “theme” to switch themes.

Features

Features

What krantho does for a site built in your own codebase: content, the admin, structured SEO, page caching, media, databases, configuration and agent skills.

  1. Content and collections

    Your content model is code you review, type-check and version with the site.

    Define collections as Zod schemas in your codebase. They type your pages, validate every save, and become the forms editors fill in the admin.

  2. The admin

    Editors get an admin without you building one, whichever framework the site uses.

    One admin for Next.js, SvelteKit and Express at /admin: forms from your schemas, drafts, preview on the site, version history, media and SEO.

  3. Structured SEO

    Every page carries a connected JSON-LD graph without anyone writing JSON-LD by hand.

    Schema.org structured data from archetypes, meta and social tags from your content, and AI enrichment on the LLM provider you choose.

  4. Rendering and page caching

    Visitors get cached pages, and editors see their changes without waiting for a timeout.

    Pages render on the server and stay cached until an editor changes something they show — in Next.js, or at the CDN in front of SvelteKit and Express.

  5. Your framework

    You keep the framework and components you know, and krantho fits around them.

    Adapters for Next.js, SvelteKit and Express with Vite, and UI packages for React, Svelte, MUI and Tailwind. The same content, API and admin on each.

  6. Your database

    Your content stays in a database you own, and moving from SQLite to Postgres is a configuration change.

    Content, versions, users, settings and SEO configuration live in your own SQLite or Postgres database, behind one adapter interface you can read.

  7. Media on any store

    Media files live where your site runs, and the choice is one configuration value.

    A media library with folders, tags, crop and hotspots. Files go to local disk, Vercel Blob, an S3-compatible bucket or Google Cloud Storage.

  8. Typed configuration

    The same code runs on every host; what differs between them is configuration you can read in one place.

    One typed configuration tree from krantho.config.ts and the environment, resolved once at startup, with every problem reported together.

  9. Agent skills

    Your coding agent works from krantho's own guidance instead of guessing at an API it has not seen.

    A Claude Code plugin that teaches your coding agent how to build with krantho: setup, content models, page templates, content and SEO.

Each capability below has its own page: the problem it addresses, how krantho approaches it, the code that shows it, and what it does not do yet. Every page ends with the documentation that shows how to use it.