Araf

Araf is the O3K cloud console: the human interface to the O3K Cloud Operating System.

This repository is intentionally not a Horizon-style UI fork and is not an infrastructure-specific administration panel. Araf presents stable O3K resources, operations, relationships, capabilities, scopes, usage and policy while keeping provider implementation details out of the normal tenant experience.

Strategic position

Araf must support the same product architecture across:

• enterprise private cloud,
• sovereign/regional cloud,
• service-provider/MSP deployments,
• community and development environments.

The product may expose different capabilities per deployment, but it must not fork into separate product-specific dashboards.

Frozen direction

• Shared UI platform with separate Tenant Console and Operator Console security/deployment surfaces.
• React + TypeScript + Vite frontend.
• O3K-owned design-system API, initially implemented using Cloudscape-compatible primitives.
• Rust Backend-for-Frontend (BFF) services; browser code does not own O3K bearer/refresh tokens.
• Native O3K resource model; OpenStack is a compatibility/migration concern, not the native UX vocabulary.
• Manifest-first, capability-driven generic resource runtime.
• Durable O3K Operations are first-class UX objects.
• Portal/API/CLI/Terraform parity; no privileged console-only cloud semantics.
• Provider details are visible to operators when required and hidden from ordinary tenants.
• WCAG 2.2 AA target for production-critical workflows.

Development

Toolchains (pinned)

• Node.js 22 LTS (.nvmrc: 22.23.2, engines range >=22.12.0 <23)
• pnpm 10.14.0 (packageManager field, enabled via corepack enable)
• Rust 1.95.0 (rust-toolchain.toml, with rustfmt and clippy)

Layout

• apps/tenant-console, apps/operator-console — separate React/Vite surfaces (ADR 0001)
• packages/* — shared UI/runtime platform; @araf/ui is the only package allowed to import an underlying component library (ADR 0004)
• backend/* — Rust BFF workspace (console-bff-core, tenant-bff, operator-bff)

Commands

corepack enable
pnpm install

pnpm format:check   # prettier --check
pnpm lint           # eslint (type-aware, strict)
pnpm typecheck      # tsc project builds
pnpm test           # vitest unit/component tests
pnpm build          # production builds of both consoles

cd backend
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo check --workspace --all-targets --all-features
cargo test --workspace --all-features

Run locally:

pnpm --filter @araf/tenant-console dev     # http://localhost:5173
pnpm --filter @araf/operator-console dev   # http://localhost:5174
cargo run -p tenant-bff                    # http://localhost:8080/healthz
cargo run -p operator-bff                  # http://localhost:8081/healthz

Planning status

The repository planning pack defines two delivery gates:

1. Prototype gate — prove the shared design system, separate shells, generic resource runtime, schema-driven actions and Operation UX using contract fixtures.
2. MVP gate — connect the architecture to real supported O3K native APIs, add production authentication/session boundaries, tenant/operator workflows, service discovery, usage visibility, security hardening and release gates.

Live tracking starts at epic #2; the committed roadmap index is in issues/README.md.

See:

• docs/product/mvp-prototype.md
• docs/product/strategic-alignment.md
• docs/product/screen-inventory.md
• docs/architecture/overview.md
• docs/architecture/o3k-integration-contract.md
• docs/security/threat-model.md
• docs/engineering/quality-gates.md
• docs/roadmap.md
• issues/README.md
• prompts/README.md

Non-goals for the first MVP

The first MVP does not include full billing/invoicing, marketplace execution, arbitrary third-party JavaScript plugins, OpenStack migration-center implementation, Kubernetes/database product UX, graphical VM console, AI-driven control-plane actions, native mobile applications, or a complete white-label reseller hierarchy.

These are future-compatible requirements, not MVP deliverables.

License

Apache License 2.0. See LICENSE in the repository root.