OSuite Readiness — Compliance and procurement

Opening OSuite

Preparing your governed workspace

We are restoring identity, workspace context, and the next control surface.

Cookie settings

Essential cookies keep sign-in and workspace routing stable. You can separately choose Analytics cookies and Preference cookies.

Security posture

validated

API security posture with protected-route enforcement and controlled failure probes

Security headers, publication-stack hardening, and explicit public/private surface ownership

Runtime-neutral governance backed by replay, proof, and trust-material capture

Live details

{ "protocol_lane_enforcement": "implicit", "privacy_gate_ready": false, "retention_policy_ready": false }

Data residency and retention

incomplete

Workspace governance profile carries region, retention, privacy ownership, and processor posture

Compliance exports surface governance readiness, identity coverage, protocol posture, and plugin footprint

Private deployment and regional buyer paths stay explicit rather than implied

Live details

{ "data_residency_region": null, "data_retention_days": null, "compliance_owner": null, "privacy_contact_email": null }

Audit trail and evidence

verified

Action envelope, risk result, policy snapshot, proof bundle, and replay surfaces form the evidence chain

Compliance report snapshots include manifest hash, verified snapshot posture, and evidence graph summary

Readiness portal publishes real validation artifacts rather than unbacked claims

Live details

{ "compliance_snapshot_verified": true, "plugin_exchange_summary_present": true, "trust_material_summary_present": true }

RBAC and IAM

available

Workspace-scoped role catalog, enterprise IAM posture, and separation-of-duties narrative

Break-glass operator isolation remains distinct from buyer-facing account and workspace roles

Future SCIM/SSO posture is tracked as deployment and lifecycle capability, not hidden roadmap debt

Live details

{ "identity_providers": 3, "role_catalog_size": 6, "scim_status": "planned" }

Support model and publication surfaces

published

Status, docs, readiness, and system-card surfaces are treated as release artifacts rather than marketing pages

Procurement buyers can inspect roadmap, deployment profiles, validation evidence, and assurance posture from public entry points

Enterprise support expectations are grounded in published deployment mode and release-readiness posture

Live details

{ "docs": "https://docs.osuite.ai/docs/enterprise-assurance", "status": "https://status.osuite.ai/", "readiness": "https://readiness.osuite.ai" }

Deployment assurance

published

SaaS, self-hosted, Azure Marketplace, and Teams plugin profiles are all described as operationally distinct deployment paths

Monitoring, backup, network, identity, and ownership boundaries are explicit for each deployment mode

Release-readiness gates require system-card, validation artifact, runtime coverage, and buyer-facing docs alignment

Live details

{ "current_mode": "saas", "distribution_mode": "production" }

Preparing your governed workspace

Compliance and procurement views for serious buyers

Security posture

Data residency and retention

Audit trail and evidence

RBAC and IAM

Support model and publication surfaces

Deployment assurance