CAST Highlight review

CAST Highlight is a software-intelligence product for governing application portfolios. CAST positions it around software mapping and intelligence: helping leaders see applications, architecture, code, data access, and dependencies, then use that context to prioritize technical debt, cloud work, modernization, and software risk management.

Architecturally, treat it as a portfolio-governance product, not as a documented API, library, CLI, or runtime security component. CAST’s homepage does not establish whether Highlight is delivered as hosted SaaS, installed software, or another deployment model; confirm that with the vendor before planning its place in your stack. Its stated use cases sit at the portfolio and planning layer, where teams assess applications and decide what to remediate or modernize. The product also presents AI opportunity mapping and agentic readiness as leadership use cases. Those claims describe intended outcomes, not a published integration contract or a guarantee of compatibility with a particular development platform.

CAST presents Highlight as software intelligence for portfolio governance, rather than as a developer-facing API or library. Its stated capabilities include mapping applications and architecture and surfacing code, data access, and dependencies. The homepage does not describe a build-time or runtime integration workflow, so teams should not assume they can call Highlight from an application or CI pipeline.

Before adopting it, ask CAST for the technical documentation and confirm whether REST API access, webhooks, a CLI, plugins, or SDKs are available. Confirm supported SDK languages, authentication, data ingestion, and export formats in the vendor’s docs; the homepage does not name languages or protocols. It also does not identify integrations with specific source-control, CI/CD, or cloud providers. That leaves the implementation effort difficult to estimate from public product positioning alone. For an architecture review, request a demo of the actual data flow, permissions model, and any supported automation points.

CAST Highlight has no listed free plan, and a free trial is not published. Pricing is based on edition and named-application cap, not on documented API requests or compute. The pricing page lists annual prices as monthly equivalents; it does not publish monthly-billing prices. For 25 applications, the listed equivalents are $2,566.67 per month for Cloud Insights, $2,750 for SCA Insights, and $3,666.67 for Complete Edition. At 1,000 applications, those rise to $27,708.33, $29,691.67, and $39,583.33, respectively.

Complete Insights — Single Application is listed at $566.67 per named application per month, with no access to concierge services. Seat limits are not published, and larger portfolios require contacting CAST. Overage costs are also not published. Before budgeting, ask whether the listed equivalent assumes annual payment, how CAST counts named applications, and what happens when the portfolio exceeds its cap. These are portfolio-license costs, not a published usage-based developer API tariff.

CAST’s product positioning does not establish a source-code license, open-source availability, or a self-hosting option for Highlight. Ask the vendor whether the product is proprietary, what deployment models are available, and whether customer code or analysis data leaves your environment. Do not assume that the product can run on your own infrastructure based on its portfolio-governance use cases.

Portability depends on what you can export and in which formats. CAST should confirm whether application maps, findings, and portfolio metadata can be exported in machine-readable form, and whether an API is available for retrieving them. Without those details, the effort to migrate data or replace the product is hard to estimate. Ask for export examples and termination terms during procurement; the pricing material does not publish them.

The application cap is the clearest published scaling boundary: editions list portfolios from 25 to 1,000 named applications, with larger portfolios directed to CAST. Seat limits, overage costs, API rate limits, and monthly-billing prices are not published. Confirm how applications are counted and what the product does when a portfolio grows beyond its licensed tier.

Before relying on Highlight in production, ask for its deployment architecture, availability commitments, backup and recovery terms, and security and compliance documentation. Confirm data residency, access controls, authentication options, and how code or analysis results are handled. If automation is part of the plan, request the API or integration limits and the supported export path in writing. CAST’s homepage describes portfolio mapping and risk-management use cases, but those do not establish an SLA or operational controls. Resolve those questions with the vendor before connecting sensitive repositories or making Highlight a dependency in governance workflows.