CHRONOOPS
TRUST CENTER · VERIFIABLE DELIVERY

ChronoOps Trust Center

A clear view of security boundaries, deployment, compatibility, and acceptance. Final capabilities are defined by version-specific evidence and the agreed project scope.

01 · Representative scenarios

These are representative product scenarios, not customer case studies or performance guarantees. Product interfaces on the home page use demonstration data; book a demo to review the current product workflow.

  • Hybrid-cloud production change with unified approval, revalidation, execution, read-back, and audit across hosts, Kubernetes, and releases.
  • Regulated operations with four-eyes approval, least privilege, controlled sessions, and immutable evidence.
  • Offline and localized environments with isolated deployment, licensing, upgrade, rollback, and compatibility validation.
  • AI-assisted remediation with fact/inference/advice separation, human review, formal approval, and outcome feedback—without an AI bypass.

02 · Security whitepaper (web v1.0)

  • Identity and authorization: MFA/OIDC, scoped roles, four-eyes controls, and single-use approval.
  • Controlled execution: immutable action intent, pre-run revalidation, bounded retries and timeouts, compensation, and read-back verification.
  • Credential boundary: the core stores references only; isolated adapters use least privilege; browsers never hold production credentials.
  • Audit evidence: decisions, approvals, execution, verification, and denials enter an append-only evidence trail.
  • Data security: sensitive content is separated from general audit, with encryption in transit, minimization, backup, and recovery drills.
  • Supply chain: artifact checksums and signatures, version manifests, pre-upgrade backup, rollback, and offline bundle verification.

03 · Deployment and acceptance guide

  • Lightweight PoC: one Linux test node and Docker to verify agent registration, jobs, approval, execution, and audit.
  • Production: Helm-based services with storage, backup, ingress, monitoring, and capacity aligned to availability goals.
  • Offline: image and artifact manifest, checksums, dependencies, license, upgrade bundle, and rollback bundle.
  • Acceptance: each capability links a claim, prerequisites, steps, evidence, owner review, and customer sign-off.

04 · Compatibility assessment matrix

CategoryAssessment scopeAcceptance
Operating systemsopenEuler, Kylin, UOS, and other mainstream LinuxValidate exact release and kernel
Architecturex86_64 and ARM64Install, agent, upgrade, and rollback
Container platformsConformant Kubernetes distributionsAPI, RBAC, controlled actions, compensation
ObservabilityPrometheus, Alertmanager, Loki, OpenTelemetry, cloud monitoringIngestion, routing, and incident timeline
IdentityOIDC, enterprise SSO, MFALogin, role mapping, and authorization boundary
DeliveryConnected, intranet, and fully offlineInstall, license, upgrade, backup and restore

05 · Contact and service

  • Sales and demos: the website form or contact@chrono.red.
  • Response window: business days, 09:00–18:00 China Standard Time; normally within one business day.
  • Implementation and support: scope, service windows, emergency contacts, and escalation are defined in the project contract and delivery handbook.
  • Operator: Beijing Shixu Zhedie Technology Co., Ltd.; website: www.aiops.red.