> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cronozen.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cronozen Docs

> Build SaaS platforms without building infrastructure. Multi-tenant, AI-native, audit-ready.

<div className="not-prose mb-8">
  <h1 className="text-4xl font-bold tracking-tight mb-4">Build on Cronozen</h1>

  <p className="text-xl text-muted-foreground max-w-2xl">
    Multi-tenant SaaS infrastructure with built-in authentication, billing, AI automation, and cryptographic decision proof. Ship your vertical platform in weeks, not years.
  </p>
</div>

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    First API call in 5 minutes
  </Card>

  <Card title="Proof Quickstart" icon="shield-check" href="/getting-started/proof-quickstart">
    Add AI decision evidence in 3 steps
  </Card>

  <Card title="Build with Cronozen" icon="hammer" href="/build-with-cronozen">
    See what you can build
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/overview">
    Explore 30+ endpoints
  </Card>
</CardGroup>

***

## Why Cronozen?

You shouldn't have to build multi-tenancy, auth, billing, and audit trails from scratch every time.

<CardGroup cols={2}>
  <Card title="Multi-Tenant Isolation" icon="shield">
    Row-level data isolation across 200+ tables. Scoped database queries. Center-based access control. Works from day one.
  </Card>

  <Card title="Decision Proof (DPU)" icon="link">
    SHA-256 hash chains seal every decision. Tamper-evident, audit-ready, exportable as JSON-LD. No other SaaS platform has this.
  </Card>

  <Card title="White-Label Ready" icon="palette">
    Custom domains, branding, landing pages via CloudFlare Workers. Your customer sees their brand — powered by your infrastructure.
  </Card>

  <Card title="AI-Native" icon="robot">
    Workflow engine, pgvector embeddings, 5-level governance guards. AI decisions are recorded, reviewed, and provable.
  </Card>
</CardGroup>

<Card title="Read: Why Cronozen" icon="lightbulb" href="/why-cronozen">
  How Cronozen differs from traditional SaaS stacks and why it matters for regulated industries.
</Card>

***

## Platform Architecture

```
           ┌──────────────────────────┐
           │    OPS Hub               │
           │    (cronozen.com)        │
           │                          │
           │  Auth · Billing · DPU    │
           │  Tenants · AI Workflows  │
           └────┬────────┬────────┬───┘
                │        │        │
         ┌──────▼──┐ ┌───▼───┐ ┌──▼───┐
         │  LMS    │ │  CMS  │ │  ERP │
         │ learn.  │ │ blog. │ │ erp. │
         └─────────┘ └───────┘ └──────┘
```

| Service  | Domain             | Purpose                                              |
| -------- | ------------------ | ---------------------------------------------------- |
| **OPS**  | cronozen.com       | Hub — SSO, payments, tenant master, DPU, 7 verticals |
| **LMS**  | learn.cronozen.com | HRD-Net compliant LMS, EMON, workshop attendance     |
| **CMS**  | blog.cronozen.com  | Blog, user manuals, SEO content                      |
| **ERP**  | erp.cronozen.com   | Odoo-based business management                       |
| **Docs** | docs.cronozen.com  | Developer documentation (you are here)               |

***

## For AI Agents

Cronozen is designed to be AI-readable:

| Resource      | URL                              | Purpose                         |
| ------------- | -------------------------------- | ------------------------------- |
| llms.txt      | [/llms.txt](/llms.txt)           | Quick platform summary for LLMs |
| llms-full.txt | [/llms-full.txt](/llms-full.txt) | Full technical context          |
| OpenAPI       | [/openapi.yaml](/openapi.yaml)   | API spec for code generation    |
| AI Context    | [/ai-context](/ai-context)       | Structured reference for agents |

```bash theme={null}
# Generate a TypeScript client with Cursor or Claude:
"Read docs.cronozen.com/openapi.yaml and generate a typed API client"
```

***

## Explore

<CardGroup cols={2}>
  <Card title="System Diagram" icon="sitemap" href="/architecture/system-diagram">
    Visual architecture with Mermaid diagrams
  </Card>

  <Card title="Core Concepts" icon="lightbulb" href="/getting-started/concepts">
    Actors, tenants, membership, DPU
  </Card>

  <Card title="Proof SDK" icon="shield-check" href="/examples/proof-sdk">
    Decision evidence in one line of code
  </Card>

  <Card title="TypeScript SDK" icon="code" href="/examples/typescript-sdk">
    Full client library with types
  </Card>

  <Card title="White-Label Guide" icon="palette" href="/guides/white-label-setup">
    Deploy a branded instance in 2 hours
  </Card>

  <Card title="LMS Platform" icon="graduation-cap" href="/guides/lms-integration">
    HRD-Net compliance, EMON, QR attendance
  </Card>

  <Card title="Data Model" icon="database" href="/guides/data-model">
    Core entities and relationships
  </Card>
</CardGroup>
