Professional help

The open community is the right place for public questions, design discussion, and help getting unstuck. Sometimes a team needs dedicated time: private domain context, a workshop, an architecture review, or hands-on help moving a slice into Cratis.

That is what professional help is for. It is separate from the open-source community and depends on availability, fit, and the right engagement model.

Start a professional conversation Email the Cratis maintainers with the context, the kind of help you need, and the timeframe.

Ask in the community first Use Discord when the question can be discussed in the open or when you are still exploring the problem.

Choose an adoption path Use the adoption guide before a paid engagement so the starting point is clear.

What we can help with

Need	Typical format
Event modeling	Workshop around commands, events, read models, policies, and bounded contexts
Cratis adoption	Slice selection, migration plan, product choice, and architecture review
Implementation	Pairing, pull-request guidance, or focused development on a bounded slice
Teaching Cratis	Team introduction to Chronicle, Arc, Components, CLI, and the full-stack loop
Teaching event sourcing	Domain events, consistency, projections, replay, versioning, and operational tradeoffs
Production readiness	Review of TLS, storage, secrets, deployment, observability, replay, and backup plans

What to include

When you contact us, include enough context to decide whether we can help:

What you are building or evaluating.
Which Cratis products you use or expect to use.
Whether this is greenfield, brownfield, or an existing production system.
The kind of help you want: workshop, architecture review, development help, training, or troubleshooting.
The rough timeframe and whether the work must be private.

If you are not sure

Start with Community and help for open questions, Feedback and suggestions for product ideas, or Learning paths if you are still choosing where to begin.