SAS Viya Platform

Commercial analytics and AI platform deployed into a customer-operated managed Kubernetes cluster.

9 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

SAS Viya November 2026 certificate and Brotli bulletins

SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches.

Scope: Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices.

Bundled trust stores, certificates, and Brotli-using components determine exposure.

Action: Apply the exact fixed maintenance level for each affected component and review certificate trust.

Primary source · Brotli CVE-2026-111497 bulletin · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    Provision EKS, AKS or GKE with SAS Terraform projects, then deploy Kubernetes manifests generated through Kustomize and SAS automation

  2. Operated by

    Your team

    Customer manages Kubernetes, networking, ingress, storage, PostgreSQL, identity, sizing, backups, platform updates and licensed deployment assets.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    SAS Viya infrastructure on AWS ↗ · Source checked 2026-11-17

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    SAS Viya infrastructure on Azure ↗ · Source checked 2026-11-17

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    SAS Viya infrastructure on Google Cloud ↗ · Source checked 2026-11-17

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodProvision EKS, AKS or GKE with SAS Terraform projects, then deploy Kubernetes manifests generated through Kustomize and SAS automation
InfrastructureServers / containers
SAS Viya runs persistent container workloads on managed Kubernetes with CAS compute, shared storage and PostgreSQL. Terraform projects provision customer infrastructure but do not complete the application deployment.
Licensing modelCommercial Only
SAS Viya requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution.
LicenseCommercial SAS Viya licensing; deployment assets and a JWT license are delivered for the customer's software order.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 9 documented · 3 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

SAS documents buying Viya through cloud marketplaces and specifically links Microsoft Marketplace. Select the matching packaged offering and delivery/entitlement terms; this is not proof every Marketplace offer matches a Terraform-based licensed deployment.

Viya software procurement; offering selection required · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

The purchasing page links packaged Viya offerings, but does not establish qualifying charges for this licensed platform deployment under the buyer cloud agreement. Workbench is separate.

Reviewed public evidence for SAS Viya Platform; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

Viya documents SAML and OIDC web SSO. Configure a compatible identity provider and matching certificates; this is distinct from user provisioning.

Reviewed SAS Viya platform requirements; web authentication; reviewed 2025.10 requirements · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

SCIM provisioning
AvailableEvidence and scope for SCIM provisioning

Viya supports SCIM 2.0, tested with Okta and Entra ID. Disable LDAP when using SCIM; SAML/OIDC, HTTPS, a public-CA certificate and inbound IdP access are required. Google Identity provisioning is not supported in this reviewed configuration.

Viya SCIM requirements; selected identity configuration; reviewed 2025.10 requirements · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The reviewed SAS Viya Platform material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The requirements separate service/user accounts, elevated deployment permissions, TLS/identity and database dependencies. Apply the selected platform security configuration; a reference to a security standard is not an independent deployment attestation. Current advisory review: SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches. Apply the exact fixed maintenance level for each affected component and review certificate trust.

Viya installation security prerequisites; reviewed 2025.10 requirements Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices. · Source ↗ · Prior security-controls source ↗ · Brotli CVE-2026-111497 bulletin ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation

The reviewed 2025.10 guide documents air-gapped deployment using SAS Mirror Manager: download entitled content outside the isolated network, transfer it and populate an internal registry without contacting the SAS entitlement/container services. Match the order assets, cadence and component dependencies.

SAS Viya 2025.10 air-gapped deployment procedure; confirm compatibility with the purchased cadence assets · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

SAS publishes Terraform for AWS infrastructure and separate deployment automation for the licensed Viya manifests. Pin a compatible tooling revision and SAS order assets; the Apache-licensed automation does not license the application.

SAS-owned AWS IaC repository · Deployment artifact ↗ (default branch (moving; select a compatible release)) · Viya deployment automation ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

Sizing depends on licensed workloads, CAS/compute roles, Kubernetes node pools, storage bandwidth and PostgreSQL. The requirements include provider-specific sizing; 100 users and 1 TB alone do not determine a supported HA cluster.

SAS Viya platform and workload-specific sizing; reviewed 2025.10 requirements · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

SAS Viya requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution.

SAS Viya Platform: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Choose the licensed Viya modules/cadence, CAS/compute pools, data-in-memory requirements, HA services and storage throughput. The order-specific topology and commercial licence price are not public. A complete monthly operating estimate is not established.

Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

SAS publishes monthly Stable releases and Long-Term Support releases about every six months, aggregating prior Stable changes. Obtain deployment assets for the purchased order and cadence; automation repository tags are not Viya application releases.

Viya platform cadence policy; exact order/version assets remain separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Scope & considerations

The public SAS infrastructure repositories are Apache-licensed deployment tooling; SAS Viya itself is commercial software and requires licensed order assets and a JWT license. Kubernetes and PostgreSQL are mandatory. SAS states that its infrastructure-as-code projects satisfy most, not all, deployment requirements. The viya4-deployment project can patch the same manifest but does not move an installation to a different cadence, version or software offering. SAS November bulletins cover compromised eMudhra certificates and critical Brotli CVE-2026-111497 across specified Viya branches. Use the vendor matrices to identify the exact affected component and fixed maintenance level; do not treat a generic Viya version as sufficient.

Category fit

Data & analytics
Enterprise data preparation, analytics, reporting and decisioning delivered by the customer-operated Viya platform.
AI tools & infrastructure
Model development, machine learning, model management and AI operationalization; exact products depend on the licensed order.

Compare within Data & analytics

  • ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
    • Azure
    Customer-operated · Commercial Only
  • Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Source Available
  • Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
    • AWS
    • Azure
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
    • AWS
    Customer-operated · Open Source / Open Core
  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core

Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • SAS Viya infrastructure on AWS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Official SAS Terraform provisions customer AWS resources including EKS, storage and optional RDS, after which the customer deploys licensed Viya assets.

    • SAS Viya infrastructure on Azure ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Official SAS Terraform provisions customer Azure resources including AKS, storage and optional PostgreSQL, after which the customer deploys licensed Viya assets.

    • SAS Viya infrastructure on Google Cloud ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      Official SAS Terraform provisions customer Google Cloud resources including GKE, storage and optional Cloud SQL, after which the customer deploys licensed Viya assets.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory