Secure Computing Architecture
for Enterprise Information Systems
Defines enterprise boundaries for computing, data and AI capabilities, and specifies how environments collaborate.
TECHNOLOGY & INNOVATION
From Architectural Principles to Engineering Practice.
Addressing the new demands of enterprise computing in the AI era through technical mechanisms, engineering discipline and publicly available technical evidence.
Bring AI into the business—without giving up enterprise control.
Adopting AI is not only about gaining intelligence. Enterprises must keep computing under control, retain governance over data, and define clear task boundaries. The Secure Computing Architecture for Enterprise Information Systems establishes the requirements for control and collaboration; NGCC provides the computing foundation; and PANSTONE turns the architecture into products through CPC and DPC.
Explore Core TechnologiesSecure Computing Architecture
NGCC
Provides a unified foundation for business and AI workloads so computing environments can be managed, audited and verified.
03 · Product Implementation
PANSTONE
PANSTONE CPC · Cloud Physical ComputerPANSTONE DPC · Dual Host PC
CPC and DPC are supported by a shared management and control plane
From Architecture to Delivery
The architecture defines the rules, NGCC provides the computing foundation, and PANSTONE delivers the products.
Core Technologies
Turn boundaries into mechanisms people can understand.
Independent physical computing units · Structural illustration
Computing Unit A
CPU · MemorySystem · Applications
Independent resource ownership
Computing Unit B
CPU · MemorySystem · Applications
Independent resource ownership
Business data remains in the target computing and storage environment
Every environment has clear computing ownership.
Systems and applications run on independent physical computing units, making resource ownership and execution location explicit. Virtual resource allocations are not treated as equivalent to independent physical computers.
Environment boundaries · Structural illustration
Environment AComputing resourcesBusiness networkData path
Structural boundary
Environment BComputing resourcesBusiness networkData path
Interaction interfaces and paths must be defined separately
Isolation is more than a permission toggle.
Boundaries are defined structurally across computing resources, data paths, business networks and interaction interfaces. Any isolation claim must still correspond to the specific topology, interfaces and scope of verification.
Controlled interaction · Mechanism illustration
Access point
Display · InputControlled interaction path
Authorized environment
Access does not imply unrestricted data exchange.
Display, input and supported peripherals interact through controlled paths. Environment access and data exchange are authorized separately; file transfer, clipboard sharing and network data exchange are not enabled by default.
Unified management · Management relationship illustration
DMSResource identity · Authorization relationships
CPCCloud-hosted computing resource
DPC Host AIndependent resource identity
DPC Host BIndependent resource identity
The management and control plane is not a business data exchange channel
Unified management preserves each environment's data ownership.
DMS organizes managed resources and authorization relationships, while each DPC host has its own resource identity. Unified management does not move local data or bridge business networks.
Mechanism illustration. Actual capabilities depend on product release, configuration, licensing, deployment and verification conditions.
View CPC/DPC Architecture & Authorization
Computing in a controlled environment; interaction at the endpoint
Endpoint access domainDisplay and input
Isolated transport domain
←Display output
→Keyboard and mouse input
Business computing domainEnterprise-owned or dedicated controlled environment
Independent Physical Computer ACPU · MemorySystem · Applications
Independent Physical Computer BCPU · MemorySystem · Applications
Business data: target computing and storage environment
DMS shared management and control plane · Resource identity · Authorization relationships · Unified management
Architecture illustration. Actual connections depend on the product and deployment.
On-demand multi-network access,
controlled cross-domain collaboration.
Physical computers are centrally deployed in an enterprise-owned or dedicated controlled environment, preserving native computing capabilities and application environments. Users access the required independent environment through authorized endpoints.
- Computing & Data
- Physical computers host systems and applications; business data remains in the target computing and storage environment
- Endpoint Role
- Display and input for authorized use of an independent computing environment
- Isolation Method
- Physical topology, interfaces and controlled interaction
“Zero data at the endpoint” applies only to designated dedicated endpoints and policies. General-purpose software clients require separate assessment of host permissions and local data-retention risks.
One chassis, two independent physical computing systems
Independent Host ACPU · Memory · StorageSystem · Applications · Business network
Independent Host BCPU · Memory · StorageSystem · Applications · Business network
Independent computingIndependent storage
One workstation: shared display and input
DMS manages each host separately, subject to the applicable release and license
Architecture illustration. Actual connections depend on the product and deployment.
Two independent hosts,
physical domain separation.
A single chassis contains two independent physical computing systems, bringing work across two domains to one workstation. Each host has its own CPU, memory, storage, system, applications and business network.
- Data Location
- Each local host has its own computing and storage
- Shared Interaction
- Shared display and input, with no network or data connectivity by default
- Management
- DMS manages the two hosts separately, subject to the applicable release and license
The DPC platform should not be described as a wholly “zero-data” device. Unified management does not mean moving data to the cloud. Actual capabilities depend on release, configuration and deployment conditions.
Two product platforms with controlled, authorized access.
Users access PANSTONE CPC (Cloud Physical Computer) and PANSTONE DPC (Dual Host PC) through supported endpoints, subject to authorization.
CPC Endpoint Access to Local Hosts
CPC user endpointApplicable access point
Authorized access→
DPC Host A or BTwo local hosts managed separately
DPC Access to CPC
Applicable DPC access pointAccess point for the Dual Host PC
Authorized access→
PANSTONE CPCAuthorized cloud-hosted computing environment
DMS Shared Management and Control PlaneUnified management and authorization are provided according to the applicable release and license; each DPC host has its own resource identity.
Access requires management enrollment, compatibility, connectivity and authorization. Access to an environment does not imply unrestricted data exchange; business data remains in the target computing environment.
R&D & Engineering
Connect the R&D process to real-world use.
Requirements & Planning
Start R&D with clearly defined requirements.
Product requirements and project plans organize R&D work and provide the basis for solution design.
- Product requirements
- Project plan
Solution Design
Move from the overall solution to subsystem requirements.
Overall solution design, a standardization plan and subsystem requirements analysis turn requirements into an implementable design.
- Overall solution design
- Standardization plan
- Subsystem requirements analysis
Development
Bring hardware and software together as one system.
Software, hardware and mechanical development advance together through integrated hardware-software testing.
- Software and hardware development
- Mechanical development
- Hardware-software integration
Verification
Carry design requirements through verification.
The R&D process includes system testing and applicable qualification trials. Test conclusions apply only to the actual product, configuration and scope of verification.
- System testing
- Applicable qualification trials
Release
Connect product introduction with real-world use.
New-product introduction, customer trials and service readiness connect R&D with product adoption. Post-delivery technical support and maintenance are provided according to contract.
- New-product introduction
- Customer trials
- Service readiness
Technical Resources
From technical claims to verifiable sources.
Version Note
The architecture content on this page is aligned with NGCC V4.2 (September 2026) and Secure Computing Architecture for Enterprise Information Systems V4.0 (September 2026). The public downloads below remain V1.0 (January/March 2026) and are not the current source for this page. Download links will be updated when the new public editions are released.
Architecture White Paper · Public Edition
Next Generation Commercial Computer (NGCC)
Next Generation Commercial Computer (NGCC)
Architecture
Explore the computing architecture, environment roles and product implementation.
Public Edition V1.0 · 2026-01-28 · PDF approx. 24.3 MBView Public Edition
Secure Computing Architecture White Paper · Public Edition
Secure Computing Architecture for Enterprise Information Systems
Secure Computing Architecture for Enterprise Information Systems
in the AI Era
Understand trust boundaries across business operations, data and AI tasks.
Public Edition V1.0 · 2026-03-28 · PDF approx. 30.8 MBView Public Edition