Skip to content
Planning workspace · Session-only drafts. Export before reloading. AI, cloud access, team routing, and deployment execution are not connected.

MANAGED SOFTWARE FOUNDATION

Container catalog

Starting software for your application, with clear responsibility for updates.

PLANNED CATALOG · Profiles are not published images. Versions, digests, support windows, and evidence require qualification.

Web & API

Node.js / Python

Customer portals, APIs, and business services.

Release
Pending qualification
Version / digest / support
Not published
SBOM / signature / scan evidence
Not available

Enterprise services

Java / .NET

Transactional services and enterprise integrations.

Release
Pending qualification
Version / digest / support
Not published
SBOM / signature / scan evidence
Not available

Minimal application

Compiled binaries / static content

Small runtime footprints for compatible applications.

Release
Pending qualification
Version / digest / support
Not published
SBOM / signature / scan evidence
Not available

AI inference

Python / approved accelerator runtime

Model serving with workload-specific GPU and driver qualification.

Release
Pending qualification
Version / digest / support
Not published
SBOM / signature / scan evidence
Not available

Edge & embedded gateway

Linux ARM64 / AMD64 candidates

Container-capable gateways with device-specific validation. Not a microcontroller firmware image.

Release
Pending qualification
Version / digest / support
Not published
SBOM / signature / scan evidence
Not available

Checked before release. Maintained over time.

Catalog qualification is intended to cover minimal components, restricted privileges, supported runtimes, scan evidence, SBOMs, provenance, and documented update policies. No image is represented as vulnerability-free or automatically compliant.

Customer-managed components

Application code, installed dependencies, models, business logic, data, and application configuration. Compatibility changes and application acceptance remain yours unless separately delegated.

OpenCentric-managed components

Agreed base OS packages, supported language runtimes, base-image releases, and the underlying container platform. Routine supported-component maintenance is included in Platform Operations.

An update is a controlled release.

  1. 1Publish updated base
  2. 2Rebuild application image
  3. 3Scan and test
  4. 4Validate in Dev
  5. 5Accept in UAT
  6. 6Approve Prod rollout

Publishing a new base image does not update running containers. Rebuild and redeploy the application artifact, verify health, and retain a rollback path. Source access, build instructions, tests, and customer acceptance must be agreed.

Make this workspace yours.

Sign in to start creating.

Sign-up and sign-in are not available on this deployment yet. You can explore examples, tools, and blueprints while account access is being prepared.

Your typed idea stays here until you refresh or leave the page.
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.