Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Cloud computing can give electronic-design-automation (EDA) teams burst capacity, flexible licensing and less infrastructure administration, but it is not automatically cheaper or faster than an established data center. In an EE Times interview published January 26, 2024, Vikram Bhatia, Synopsys’s head of cloud product management and go-to-market strategy, described Synopsys Cloud, FlexEDA licensing and the ChipSpot service as examples of this approach. His statements are vendor claims from a sponsored interview, not independent performance or cost validation.

What the EE Times episode says has changed in EDA

The episode’s central idea is that EDA teams increasingly need elastic capacity. Verification and implementation jobs can create short-lived peaks that exceed an organization’s installed servers, storage or software entitlements. Cloud capacity can be added for those peaks instead of permanently building for the maximum demand.

Bhatia said that, “a couple of years ago,” about 17% of total EDA capacity utilized was in the cloud. That figure is his 2024 estimate; the interview does not provide a dataset, geographic scope or definition of “utilized,” so it should not be treated as an industry census.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How Synopsys Cloud is described

Bhatia described Synopsys Cloud as a browser-based platform running on Microsoft Azure infrastructure. In his description, the service combines cloud compute and storage with EDA workflows and automated license management. He contrasted that managed experience with the weeks or months that can be required to assemble a conventional EDA environment, while saying onboarding through the platform could occur within a day or two in suitable cases. Those are illustrative statements from the January 2024 interview, not a guaranteed deployment time or a current product specification.

FlexEDA licensing

FlexEDA was described as on-demand EDA software licensing, including use measured by the minute. The practical value is matching license spending to burst workloads rather than buying enough perpetual or fixed capacity for every peak. Actual availability, tool coverage, contract terms and minimum charges must be confirmed with Synopsys.

ChipSpot and interruptible capacity

Bhatia described ChipSpot as a service developed with Exostellar for using interruptible Spot compute on selected, memory-intensive EDA jobs. Its proposed mechanism predicts a likely interruption and live-migrates the workload to reduce disruption. He reported 20 to 30 minutes of advance prediction in some cases, while acknowledging that some interruptions provide two minutes or less notice. He also characterized potential customer prices as 50% to 75% lower when Spot instances are used through ChipSpot. These figures are Synopsys claims; the episode supplies no workload list, baseline price, interruption statistics or independent test.

Where cloud can improve an EDA workflow

Capacity for verification and design iterations

When local queues are full, additional cloud workers can let teams run more regressions, corners or implementation experiments in parallel. More iterations may shorten a schedule, but the result depends on license availability, data-transfer time, job parallelism and the ability of the flow to checkpoint and restart.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Less infrastructure and license administration

A managed service can shift some server provisioning, storage configuration, tool installation and license coordination away from an internal CAD or IT team. This can be valuable for small organizations and startups that lack a large operations staff. It does not remove responsibility for access control, PDK and tool qualification, data governance, network design or vendor support.

Elastic spending

On-demand licenses and pay-as-used infrastructure can align spending with an irregular project schedule. They can also cost more when workloads run continuously or when data egress, storage and support charges are significant. A valid comparison must include all of those components.

Cloud, customer-managed cloud and on-premises: a practical comparison

Option Likely strength Questions to validate
Existing on-premises data center Predictable control, local data access and potentially low marginal cost when servers are already well utilized. How often are queues full? What is the cost of idle capacity, refresh cycles, power, facilities and CAD/IT staffing?
Customer-managed cloud environment Flexible infrastructure choices and control over network, images, storage and security architecture. Who builds and maintains the EDA environment, licenses, images, monitoring, PDK integrations and support process?
Managed/browser-based EDA cloud service Faster access to a packaged workflow, elastic compute and potentially simpler license administration. Which tools, foundry kits, regions, APIs, security controls and data-transfer patterns are supported today?

What the cost claim should—and should not—mean

Bhatia explicitly noted that a large, already-built on-premises data center can have a lower infrastructure cost than cloud. Cloud economics therefore depend on workload utilization rather than on a universal “cloud is cheaper” rule.

Build a comparison using at least these cost buckets:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Compute for normal and burst periods, including any Spot or interruptible discounts.
  • Storage, backups, snapshots, networking and data egress.
  • EDA licenses, FlexEDA usage and any fixed commitments.
  • Server, facility, power, hardware-refresh and operations costs for on-premises capacity.
  • CAD/IT labor for installation, patching, monitoring, security and support.
  • Schedule impact when jobs wait in a local queue or data must be moved to and from the cloud.

Workloads that need special scrutiny

Memory-intensive jobs

Large-memory simulation and verification jobs may be candidates for specialized or interruptible instances, but only if the tool and flow tolerate migration or restart. Confirm memory size, local scratch requirements, checkpoint behavior and maximum interruption loss.

Long-running and fragile jobs

A job that cannot checkpoint efficiently may lose more value than it gains from a discounted instance. Measure restart time and the amount of recomputation after an interruption before adopting Spot capacity.

Data-heavy flows

Moving RTL, netlists, waveforms, layouts, PDKs and libraries can dominate both runtime and cost. Test representative datasets, not a small synthetic job, and establish where persistent data resides.

Security, IP and ecosystem requirements

EDA data commonly includes proprietary designs, third-party IP and foundry process-design kits. Before placing it in a cloud service, obtain current documentation for identity management, encryption, tenant isolation, audit logging, region selection, retention and incident response. Also check whether every foundry, IP vendor and EDA tool in the flow permits the proposed environment. The interview discusses security-sensitive IP and ecosystem coordination as industry context but does not establish a particular certification or customer control set.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A validation plan for an EDA cloud pilot

  1. Choose a representative workload. Include a normal run, a peak regression and at least one memory-heavy or long-running job.
  2. Record the baseline. Capture queue time, wall-clock runtime, license wait time, storage transferred, engineer involvement and total on-premises cost.
  3. Recreate the flow in the target environment. Qualify tool versions, PDKs, scripts, license behavior, file permissions and result reproducibility.
  4. Test scaling. Increase parallel workers and measure queue delay, throughput, network performance and license availability.
  5. Test interruption recovery. For any Spot-based design, inject or observe interruptions and record lost work, migration success, restart time and final output integrity.
  6. Calculate full cost. Include compute, storage, transfer, licenses, support and internal labor for both environments.
  7. Set acceptance gates. Define the maximum allowed cost, runtime variance, data-transfer time and recovery loss before expanding beyond the pilot.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What is—and is not—established by the customer examples

The interview names Cisco, Econix, ASI and unnamed startups as examples. It does not provide independently sourced case studies, sample sizes, workload descriptions or measurement methods for their outcomes.

Bhatia also referred to an independent-user survey that found up to 40% time saved. The transcript does not provide the survey sample, questions, workload mix or baseline, so the figure should be treated as a reported survey result rather than a predictable saving for every team.

The Openlink program

Bhatia described the Synopsys Cloud Openlink Program as an announced open-API initiative intended to connect ecosystem participants and allow customer access across providers. The interview does not establish its current status, integrations or production availability. Confirm those details in current Synopsys documentation before designing an architecture around it.

Questions to ask before committing

  • Which exact EDA tools, versions, PDKs and third-party IP licenses are supported?
  • Can data remain in the required country or region?
  • What are the compute, storage, network, license and support charges?
  • How are interruptions, failed jobs and corrupted or incomplete results handled?
  • What APIs, export paths and termination procedures prevent lock-in?
  • Which security attestations and customer-controlled safeguards are available now?
  • What service-level commitments apply to capacity, support and data durability?

The Bottom Line

Cloud can make EDA capacity and licensing more elastic, especially for bursty verification and design workloads. The 2024 EE Times interview presents Synopsys Cloud, FlexEDA and ChipSpot as examples, but its adoption, savings and performance figures are vendor-reported. Decide with a workload-based pilot that measures queue time, recovery behavior, complete cost and security requirements against your existing environment.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.