Skip to content
OPENCENTRIC / LEGAL

Community Guidelines

Public sharing, contact preferences, and reporting boundaries.

Framework draft · Not approved or effective

These pages are for review, not acceptance or signature. Business details, operational practices, and legal terms must be confirmed before launch.

Version 0.1 - review draft · Effective date: not set

Approval still required

This is a policy framework, not a signed agreement. Review the entity details, actual service implementation, customer jurisdictions, and required protections with qualified counsel before publishing an effective version.

View launch decisions
YOUR OPENCENTRIC WORKSPACE

Everything underneath. Managed.

From your first website to connected products and embedded AI. You define the outcome; OpenCentric brings together and manages the foundation your solution needs.

CUSTOMER APPLICATION LAYER

Customer owned and operated

Your applications, added dependencies, data, business logic, configuration, tenants, users, and decisions.

MANAGED PLATFORM COMPONENTS

OpenCentric supplied and managed

Infrastructure, runtime, supported base images, delivery controls, and agreed operations. The boundary follows component ownership, not simply what is inside a container.

Managed throughout the lifecycle

Performance and reliability
Track health and response times. Adjust capacity to demand, within agreed cost and recovery limits.
Releases and configuration
Keep code and settings recorded. Test and approve updates, with a way back if a release fails.
Security and evidence
Find and prioritize weaknesses, verify fixes, and keep records for reviews.
Cost and resource efficiency
See where money goes. Review unused resources, resource sizes, and spending limits.

Capabilities as your needs grow

8 platform layers + continuous management

212 capability entries to plan from

This is a capability planning catalog, not a list of active or universally available services. Provider availability, integrations, service levels, and operating responsibilities are agreed for each solution before deployment.

Different missions. The same managed foundation.

Websites, SaaS, and commerce
Public sites, customer workspaces, payment links, and transparent product records.
Healthcare and life sciences
Sensitive data boundaries, interoperability, auditability, and clinical safety requirements.
Government and DoD
Approved environments, access restrictions, control evidence, and system-specific ATO planning.
Edge AI, robotics, and embedded systems
On-device inference, sensors, embedded vision and voice, device telemetry, firmware integration, and hardware validation, including limited-connectivity environments.
Space, aviation, and remote operations
Ground systems, mission data, simulation, and intermittent-connectivity requirements.

Regulated and safety-critical systems require workload-specific assessment, contracts, validation, and applicable approvals. Cloud availability does not establish compliance, an ATO, or hardware or flight certification.

Engineering and operating practices

Reference points for solution design and delivery. Applicable versions, controls, review cadence, and evidence requirements are agreed in each implementation plan.

NIST SSDF: secure software deliveryFinOps: usage and resource optimization

These references describe practices, not certifications held by OpenCentric.