Operations
Aidin separates public customer documentation (this portal) from restricted internal operations documentation (runbooks, privileged procedures, cluster internals). This page states what customers can rely on operationally; anything security-sensitive remains internal by design.
Monitoring and observability
Section titled “Monitoring and observability”- Each workspace has access to workload monitoring dashboards (GPU/CPU/memory utilization and pod metrics) from the platform dashboard — see Integrations.
- Platform-side monitoring (control plane, capacity, alerting) is operated by Aidin.
Updates and releases
Section titled “Updates and releases”- Platform components are released on a managed cadence with pinned versions (see Integrations and deployed versions) and controlled rollback.
- This documentation is versioned to match the deployed platform: the document version shown on the About page maps to the platform release it describes. Release notes for the platform will be published as the release process for public tenants is finalized.
Backup and recovery
Section titled “Backup and recovery”Documentation governance (docs-as-code)
Section titled “Documentation governance (docs-as-code)”- Technical docs are authored in the component repositories that own each feature, alongside the code they describe, and validated by CI (lint, link check, required-doc-change gates).
- This portal synchronizes that material at pinned commits with checksums — never from an arbitrary branch — then builds, previews, and publishes under release authorization.
- Publication is part of the release gate: if documentation publishing fails, the release fails its documentation gate.
What stays internal
Section titled “What stays internal”Incident response procedures, cluster administration, credential and secret handling, security controls detail, and customer-identifying operational data live in restricted internal documentation and are never published here.