Bundled features

Bundled features are complete features from the framework repo that you add to an app in one line. Each includes schema, handlers, hooks, often UI components, and tests. You use them like your own features and can override conventions such as table names, hash algorithms, and channel implementations.

They live under packages/bundled-features/src/<feature>/ and get activated through two paths:

1. Auto mode: when you set auth: { ... } in runDevApp / runProdApp, composeFeatures auto-prepends the identity quartet (config, user, tenant, auth-email-password). That’s all most apps need.

2. Manual: other features (audit, secrets, jobs, channels …) you import explicitly and add to your features array.

import { runDevApp } from "@cosmicdrift/kumiko-dev-server";
import { createAuditFeature } from "@cosmicdrift/kumiko-bundled-features/audit";
import { createSecretsFeature } from "@cosmicdrift/kumiko-bundled-features/secrets";

await runDevApp({
  features: [
    createAuditFeature(),
    createSecretsFeature(),
    myAppFeature,
  ],
  auth: { /* enables config + user + tenant + auth-email-password */ },
});

Overview

Bucket	Features	When
Identity layer	auth-email-password, sessions, user, tenant, config	Every multi-tenant app. Auto-loaded in auto mode.
Audit & security	audit, secrets, rate-limiting	Compliance, external API keys, throttling write paths.
Compliance & DSGVO	compliance-profiles, data-retention, user-data-rights, user-data-rights-defaults	DSGVO Art. 15/17/18/20, region profiles, retention cron, forget-grace, magic-link export.
Operations	jobs, feature-toggles	Background work, gradual rollout.
Notifications	delivery, channel-email, channel-in-app, channel-push	Notify users, channel-agnostic.
Files & renderer	files-provider-s3, renderer-simple	File uploads, email templates.
Content & SEO	template-resolver, legal-pages, managed-pages, seo	Editable copy, DACH legal pages, tenant-branded public pages, sitemap/llms.txt + OG/JSON-LD site discovery.
Custom fields	custom-fields	Per-tenant extra fields on any entity, defined at runtime, no migration.

Status legend

• ✅ Stable, used in production apps (publicstatus), API is stable
• 🚧 Beta, works, but the API may still change. Use at your own risk in production
• ⬜ Planned, on the roadmap, not in the repo yet

Detail pages

🚧 A dedicated detail page per bundled feature is planned (setup + full options list + edge cases + migration paths). Until then the source under packages/bundled-features/src/<feature>/ is the authoritative reference, every feature has a header comment with an architectural overview.

See also

Where do I find…	Here
How these features fit into the pipeline	Framework
Runnable examples (auth, audit, notifications, …)	Recipes
Deployment + hosting	Platform
Pattern reference (r.config, r.secret, r.job, …)	Patterns