WeaveKit Docs

service

The service preset: a headless backend with RBAC and script hooks.

create-weavekit-app my-app --type=service

Narrative: Business service — headless backend with RBAC and a REST API.

What it scaffolds

  • Script subsystem on (subsystems.script: { enabled: true }) — *.server.js hooks run in the sandbox.
  • features.fieldTypes includes the opt-in types.
  • REST + MCP enabled (as always).

What it's for

A headless backend that other teams or services consume: RBAC-scoped objects over REST, with server-side hooks for the logic you don't want clients to own. Think "internal API for a business domain", not a product UI.

What you'll usually add

  • Script hooks for validation and side effects (objects/<name>/server.js).
  • Quotas if different callers share the API.
  • Events / ingress to talk to other systems.

On this page