Skip to main content

CloudForge standardized docs

Platform docs for the current CloudForge deployment model.

This site is the operational and architectural source of truth for CloudForge: Cloudflare Pages frontend, Fly.io API, frontend-owned Okta SPA PKCE, backend JWT validation, and the current 300K-finding public demo footprint.

Open DocsAPI Schema

Standardization notes

  • CloudForge branding is the active public name across docs-site and current docs.
  • Legacy `AEGIS_*`, `aegis-*`, and `/icons/aegis-logo.svg` references remain only where compatibility matters.
  • Interactive OpenAPI explorer is still deferred; the YAML spec and markdown reference are the supported path today.
89OpenAPI operations
17Remediation handlers
300KPublic demo corpus
4Ticket providers incl. mock

Start here

Entry points by job to be done.

Architecture

Start with HLD, DDD, DR/BC, and the ADR trail behind the current platform shape.

Open section

API And Schema

Use the OpenAPI YAML plus the markdown endpoint reference while the interactive explorer stays deferred.

Open section

Operations

Deployment, identity, remediation, and teardown runbooks for the live Fly.io plus Cloudflare Pages topology.

Open section

Auth Decision

See why CloudForge keeps SPA PKCE today and what would be required before moving to a BFF.

Open section

Quickstart

Work on the docs locally.

cd docs-site
npm install
npm run start

# production build
npm run build

The docs source lives in `../docs`.

Diagram rendering and visual QA are handled separately from this docs-content pass.

Use the sidebar for current platform docs; treat archive and research content as historical context.