Question 1

Does it work with Cursor / Copilot?

Accepted Answer

Yes as a complementary system of record. Agents still write code; the model holds durable domain and architecture so prompts stay grounded.

Question 2

Is this GitHub Spec Kit?

Accepted Answer

Spec Kit is a markdown workflow agents read once. Katip is a product model: versioned YAML layers, fail-closed validation, and a NestJS skeleton. Complementary category, not the same artifact.

Question 3

Is this low-code?

Accepted Answer

No. You author formal models and generate structural Nest code — not a visual app builder or proprietary runtime lock-in.

Question 4

Which stacks today?

Accepted Answer

NestJS / TypeScript generation is the first technology profile. Multi-stack is roadmap, not a current claim.

Question 5

Is event-driven the same as event sourcing?

Accepted Answer

No. In Clerk they are separate capabilities: event_driven is communication-level; event_sourcing is persistence with domain-event constraints.

Question 6

Do you generate UI?

Accepted Answer

Presentation is an architecture axis; full UI generation is not a shipped product claim in this preview.

Question 7

What is the model format?

Accepted Answer

YAML with clerk_version, strict Zod schemas, and a four-layer pipeline (manifest, domain, architecture, technology).

Question 8

Pricing?

Accepted Answer

Developer Preview — pricing lands with Playground and SaaS packaging. Core remains open-core oriented.

Question 9

Can I self-host?

Accepted Answer

Core packages are for local/CI use. Katip SaaS is self-hosted on TOGSAR infrastructure when you use the product site.

Pricing

Starter

Pro

Enterprise

FAQ

Pricing

Starter

Pro

Enterprise

FAQ