A SaaS product may also need to run in customer AWS accounts, data centers, private clouds, air-gapped environments, or dedicated installations. DJ2 Services builds a reusable baseline for those deployments, covering virtualization, Linux, network boundaries, Kubernetes, backups, and evidence for security reviews.
The work focuses on the infrastructure your product installs onto. Operating your customers' general IT environments is outside our scope.
Keep your primary SaaS environment. Use its account structure, networking, and identity requirements to establish a baseline that can also support customer deployments.
Define how the product deploys into a customer-owned AWS account, including access boundaries and evidence their security team can review.
Use OpenNebula with OneKS as a reference design for customer hardware, with virtual machines and Kubernetes managed from one control plane.
Apply the deployment baseline to vendor- or customer-owned hardware in colocation, including rack deployment, the network handoff, and hardened hosts.
Kubernetes can provide a common application platform across Amazon EKS, OneKS, and customer-managed clusters. A shared deployment model gives your engineering team a baseline to reuse as customer requirements change.
During a Customer-Hosted Deployment Architecture Diagnostic, DJ2S reviews where the product needs to run and designs the platform baseline. The accompanying build plan defines a fixed implementation scope.