IT leaders manage unique landscapes. You balance innovation with security. You balance speed with data sovereignty. Krista respects this reality. We designed our platform architecture to adapt to your infrastructure requirements.
You choose the topology. Krista provides the automation.
Understanding the platform requires defining its four primary components.
services to host multiple workspaces and orchestrates interactions with appropriate data appliances and access points. Krista DevSecOps automates and manages all deployments, updates, and migrations. We deploy the Instance into a Kubernetes-based Infrastructure.
This is your secure tenant. It is a single logically segregated tenant within a Krista Instance. It is typically dedicated to a specific customer and delivers the Krista Studio and Krista Client. Workspaces are isolated by separate databases within the same engine, isolated file systems, authentication of every API call into and within Krista, and many other means.
This component secures your information. It stores all data for the connected workspace(s). Data is not stored outside the data services at any time except for transient caching of latency-sensitive use. We deliver this as a set of Kubernetes Services that can be hosted in a variety of ways. This approach is considered the most challenging to operationalize, but it offers significant control.
This acts as the secure bridge. It is a component in Krista that is responsible for hosting extensions, enabling Krista connectivity to customer applications and data. We deliver this as Kubernetes or Docker components that can be hosted in a variety of ways. Many Access Points may be used in a single deployment. Every Krista Instance has at least one Access Point deployed.
Krista operates as SaaS in every model. This ensures reliability and continuous security updates regardless of where the infrastructure lives.
We partner with you to secure the platform. Our obligation to monitor, maintain, and secure your data and our IP remains constant. Zero-day patching is non-negotiable for us. Krista DevSecOps maintains continuous connectivity to monitor and patch the environment. This keeps your deployment secure against emerging threats.
You retain control over your AI models. You have flexibility with Krista regarding which LLMs you use and when. You can connect to the Krista Cloud from your Instance or use third-party providers. You can also deploy GPU-based servers to run Krista LLMs locally. Most customers access both Krista LLMs and third-party models to optimize performance and cost.
We support three topologies to match your specific compliance and operational goals.
This model delivers maximum speed and global accessibility. The entire Krista Instance and Data Appliance run in the Krista Public Cloud. We manage all compute and storage. You simply connect your internal systems via a secure on-premise Access Point. This ensures full adherence to Krista’s audit standards and certifications.
This model prioritizes data sovereignty. The Instance runs in the Krista Public Cloud. You host the Data Appliance in your own data center. Data stays on your premises to meet regulatory needs. You retain full physical control over your information while leveraging cloud compute for logic.
This model ensures maximum isolation. We deploy a dedicated Krista Instance solely for your organization. You do not share infrastructure with any other customer. You can deploy this in the Krista Cloud, your private cloud, or on-premises. Krista DevSecOps maintains 24/7 access to ensure security integrity across the environment.
Choosing a self-hosted model increases your control. It also shifts operational responsibility to your team.
Choose the model that fits your mission. Krista delivers the flexibility to scale securely. For the complete technical blueprint behind these deployment options, download the Krista Platform Architecture white paper.
© Krista Software | Privacy Policy | Terms of Service
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |