Next Steps

Congratulations. You now have a working Granit API with the module system, persistence, authentication, and observability configured. From here, the documentation is organized to let you dive into whichever area your project needs first.

Recommended reading paths

Pick the goal closest to what you are building and follow the link to get started.

Goal	Start here
Understand the module system deeply	Module System concept
Add multi-tenancy	Multi-Tenancy concept
Set up notifications	Notifications reference
Import data from CSV/Excel	DataExchange reference
Generate PDF documents	Templating reference
Add background jobs	BackgroundJobs reference
Deploy to production	Operations (coming soon)

Good to know

You do not need to read the documentation linearly. Each module page is self-contained with its own installation steps, configuration, and usage examples. Jump to whatever your project needs right now.

Explore the module reference

Granit has 135 packages organized into categories: Core, Security, Data, Messaging, Documents, Workflow, Observability, and more. The Reference overview shows every module with a short description of its role, so you can quickly find the right package for your use case.

Each reference page covers:

• What the module does and when to use it
• Installation and module dependency declaration
• Configuration options
• Code examples for common scenarios
• Related modules and integration points

Architecture decisions

Curious why Granit uses CQRS, isolated DbContexts, or Channel fallbacks? The Architecture section documents the design decisions behind the framework, including the constraints that shaped them (GDPR, ISO 27001, multi-tenancy).

Understanding these decisions will help you work with the framework rather than against it, especially when you encounter patterns like separate Reader/Writer interfaces or the isolated DbContext checklist.

Community and contributing

Granit is open-source under the Apache-2.0 license. Contributions are welcome, whether that is fixing a bug, improving documentation, or proposing a new module.

Check the Contributing section to learn about the development workflow, coding conventions, and Definition of Done that all contributions must satisfy.

Pro tip

If you are building a reusable module for your organization, use the granit-module template from the Project Templates page. It scaffolds the correct project structure, test setup, and README so your module follows the same standards as the framework itself.