Work with Cratis maintainers
You can work directly with Cratis maintainers to review an architecture, model a business workflow, or build a first slice alongside your team. Dedicated work is scoped and paid, with deliverables and availability agreed before it starts. Use community help for questions you can discuss publicly without a response deadline.
An engagement should resolve a specific decision or leave your team with something it can use: a reviewed model, an adoption plan, or a bounded implementation. Describe the decision you face and the result you need; you do not need a finished design to start a conversation.
If you need help
Section titled “If you need help”You might be deciding whether event sourcing fits your system or choosing the first Cratis feature to adopt. A review can also help when your read models, the views built from recorded events, no longer answer the business’s questions.
If the team needs to learn together, a workshop can use your domain to work through commands, events, and the views people need. For implementation help, identify one slice: a bounded business feature that the team can build and use as a pattern for later work.
What we can help with
Section titled “What we can help with”| Need | Work to discuss | Possible agreed deliverable |
|---|---|---|
| Event modeling | A working session over your domain: commands, events, read models, and boundaries | A reviewed event model and candidate slices to build first |
| Cratis adoption | Slice selection, component choice, and a path from the system you run today | A sequenced adoption plan with the first slice specified |
| Architecture review | A review of selected system boundaries and failure modes | A written review with risks ranked and recommended changes |
| Implementation help | Pairing or focused development on a bounded slice alongside your team | A first slice in your codebase with the pattern explained |
| AI-ready foundations | Repository conventions, analyzers, and Cratis AI guidance | Repository instructions and checks for developers and assistants |
| Teaching event sourcing | Domain events, consistency, projections, replay, versioning, and operational trade-offs | A workshop applying those concepts to your domain |
| Teaching the stack | Relevant Cratis components taught through a feature | A guided implementation your team can study and extend |
| Production readiness | A scoped review of deployment, security, observability, replay, and recovery plans | Findings and follow-up actions, not a certification or guarantee |
Building for the AI age
Section titled “Building for the AI age”If your team uses coding assistants, make the repository’s expectations explicit. Cratis AI rules and skills provide instructions for assistants; analyzers check specific code patterns. Cratis Arc generates TypeScript clients from recognized backend contracts, so the frontend does not need a separately handwritten copy of those contracts.
An AI-ready foundations engagement can focus on the instructions and checks your repository needs. These tools do not establish that generated code is correct: your team still owns review, tests, and the decision to ship.
For what this looks like in the products themselves, see AI-native development, Cratis AI skills and plugins, and code analysis.
How we work
Section titled “How we work”Start with a conversation about fit. Before work begins, agree the scope, deliverable, price, and timeframe in writing. For dedicated support, the signed agreement defines availability, response targets, points of contact, and escalation; an inquiry alone does not establish those commitments.
Agree confidentiality and access arrangements before sharing private code or domain material. Questions that can be answered publicly can stay in Discord or become documentation improvements without a paid engagement.
What to include when you contact us
Section titled “What to include when you contact us”Enough context for us to tell you honestly 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 a system already in production.
- The kind of help you want: modeling, review, development, training, or troubleshooting.
- The rough timeframe, and whether the work has to be private.
When we are not the right fit
Section titled “When we are not the right fit”For questions you can discuss publicly, start with Community and help. For a suspected vulnerability, use the private reporting route in Security, not an engagement inquiry or a public thread.
Dedicated work focuses on the model, Cratis components, and the architecture around them. It is not a general .NET or React consultancy or a replacement for your development team. Implementation help is bounded work alongside your team, not a commitment to build and maintain the whole product.
Contact us
Section titled “Contact us”Email oss@cratis.io with a subject that starts with Working with Cratis, and include the context above. Keep the first message to a summary without credentials, personal data, or confidential attachments. The conversation can then establish fit, scope, and possible start dates.
If you are still deciding where to begin, Adopting Cratis lays out the paths from an existing system, and Learning paths routes you through the documentation by role.