Enterprise deployment
Run Jinkō as a dedicated instance in your AWS, Azure, or Google Cloud environment. Your organization controls the cloud account, network, storage, keys, and identity provider. Nova manages the Jinkō application, releases, and application-level support.
Privacy and control
Data sovereignty
Modeling data, Virtual Populations, and simulation results remain within your cloud environment. Databases and object storage use your infrastructure and encryption controls.
Enterprise security
- Connect through private networking, such as PrivateLink or a VPN.
- Integrate with your SSO and SAML 2.0 identity provider.
- Apply your existing cloud security, monitoring, and compliance controls.
Managed application updates
Nova delivers security and feature releases to the dedicated environment. Your team can review feature releases before deployment while receiving required security updates through the agreed operating process.
Adjustable compute capacity
Size simulation and calibration workers for your workload and budget. Capacity can scale with demand within the limits and policies of your cloud account.
Clear roles and responsibilities
| Category | Your organization | Nova In Silico |
|---|---|---|
| Application | User access and organization settings | Bug fixes, feature releases, and application performance |
| Infrastructure | Cloud account, network, and cloud costs | Deployment automation and scaling configuration |
| Data and secrets | Storage, keys, and secret-management services | Application-level encryption and security controls |
| Monitoring | Infrastructure and network monitoring | Application health and support |
Deployment process
- Architecture alignment. Nova engineers work with your cloud and security teams to document requirements and integration points.
- Infrastructure provisioning. The teams prepare the Kubernetes, database, storage, networking, and identity services required by the reference architecture.
- Preproduction validation. Users validate access, workflows, performance, and operational procedures.
- Production rollout. Nova deploys Jinkō, validates SSO and application health, and completes the agreed security checks.
Typical technical architecture
- Orchestration: A managed Kubernetes cluster, such as GKE, EKS, or AKS.
- Data services: Managed PostgreSQL and Redis services.
- Storage: S3-compatible object storage for persistent assets.
- Connectivity: Outbound access to Jinkō's secure container registry.
- Identity: Integration with your identity provider.
Reference architecture using Kubernetes and infrastructure as code.