Billing reference
The six peer-equal cost dimensions, the `meta.cost` response shape, tier caps and overage behaviour, the Gate (IAK) MAU model, and the cost-export API.
Custom Domains
Replace the platform subdomain with your own brand. End-users hit your domain, not Kilimanjaro's; cookies, OAuth callbacks, JWT issuer, and DKIM-signed email all on your domain. Kilimanjaro is invisible.
Routing Modes
How customer URLs compose — subdomain mode by default, path-prefix mode for LAN multi-tenant, single-org mode for Private Perimeter appliances. One grammar, three operational behaviors.
Slug Addressing
How orgs and projects are addressed by customer-friendly slug across every customer-facing surface — URL, SDK init, CLI, webhook payloads, audit ledger. Slug is presentation; ID is internal canonical; the two compose without conflict.
Session Model
Two-tier session model — root sessions on the platform's identity anchor, tenant sessions on the org subdomain. Exchange flow, sign-out cascade, MFA step-up, and the API-key bypass for programmatic access.
Regions & residency
How data residency works on Kilimanjaro — 14 sovereignty-pinned regions, the legal bloc and pricing zone of each, region-pin at project creation, the immutability rule, cross-border policy, and the control-plane / data-plane split.
Stack-SDK extension-call pattern
How application code reaches an installed extension's runtime API: the route it is served on today, and the typed per-extension call pattern that is the design target but is not yet available in the SDKs.
Extension typing model
How typed access to an installed extension is designed to work: the per-extension OpenAPI document as the single source of truth, build-time and install-time codegen, and per-language parity. This is a design target; no SDK ships it yet.
Handling Errors
KError shape, the closed taxonomy, universal error families, status code mapping, retry behaviour, and rate-limit handling.
Error catalogue
The closed-taxonomy master catalogue — every error code and warning code with HTTP status, family classification, and originating chapter reference.
Project Selection & Access Requests
The auth-flow lifecycle from email discovery through org authentication to project selection — plus the access-request resource that lets non-members request project access.