Skip to main content
This section is for teams integrating clients against Kralis. This is not a self-hosting or backend-contributor guide. The expected public developer workflow is:
  • authenticate against Kralis
  • call GraphQL for main application behavior
  • use REST where Kralis exposes auth or read-oriented resources
  • respect school scoping and product validation rules
It is intentionally different from the operator-facing guides:
  • operator guides explain how schools use Kralis
  • developer docs explain how an external client should call the platform safely

​
What developers should know first

  • Kralis is a multi-school platform
  • school context is part of the security model
  • GraphQL is the primary product API
  • REST remains important for auth, documentation, and selected resources
  • live documentation surfaces are part of the integration workflow
  • developers are expected to use Kralis, not self-host it, in the public docs context

​
Main interfaces

​
What belongs here

Use the pages in this section for:
  • auth expectations
  • school scoping rules
  • GraphQL and REST usage
  • client integration patterns
  • live reference entry points

​
Capabilities

The developer section supports:
  • authentication guidance
  • API surface discovery
  • GraphQL and REST usage guidance
  • school-scoping expectations
  • integration patterns
Internal backend implementation and contributor operations remain in the backend repository, not in this public docs site.