Our customers rely on Altium 365 to run mission-critical
projects. We are committed to delivering products that are
stable and secure at scale.

High Availability by Design

The Altium 365 cloud platform is hosted on the Amazon Web Services (AWS) infrastructure, one of the world’s largest cloud infrastructures. It leverages redundant compute resources with multi-availability zone storage services spread across four independent regions.

Our platform is architected to avoid any single point of failure. We utilize AWS techniques, including multi-zone availability, load balancing, and clustering, to have a multilayer approach for fault tolerance. This way, we can achieve a higher level of availability than a single installation of the service hosted on-premises.

Disaster Recovery and Contingency Planning

We build and maintain comprehensive business continuity and disaster recovery plans. These plans ensure our ability to minimize disruptions and restore services as fast as possible in the unlikely event of a disaster.

We routinely back up data for fast recovery times. Our backup and restoration capabilities and disaster recovery plans are tested regularly.

Platform Performance and Scalability

We continuously monitor and optimize key platform performance metrics, such as search responsiveness, load, and rendering times. We conduct performance and load tests to ensure that our services are resilient against usage spikes.

Our cloud infrastructure is hosted in four distinct geographic regions; you can choose the region closest to you to minimize latency.

Working Offline

There might be occasions when you need to work on a project without stable access to the internet. With Altium 365, you can work on projects locally. When you open any project from the cloud, a local copy is saved on your computer, and you can work with it offline. For more information, see Working Offline.

Thanks to local caching, an internet connection is not required to place components from your cloud library. If you are using other library options, such as database (DbLibs) or integrated (IntLibs) libraries, there will be no change to the way you work if you migrate your library to Altium 365. Note that creating and editing components in your Altium 365 library does require an internet connection because the changes need to be synced to the server.

24/7 Monitoring and Operations

We monitor the platform’s performance using multiple approaches, from synthetic agents to real-time detection of abnormalities in behavior. We can identify unusual slowdowns or other performance issues and initiate an incident response before the problem becomes noticeable.

We have a dedicated team of engineers on call 24/7 to ensure that we maintain the platform in working order at all times.

Incident Response and Status Transparency

We are prepared to react to any incidents immediately. Keeping customers informed about the severity, scope, root cause, and resolution of any incidents and associated problems is essential to our incident response plan.

We provide real-time information on the status of our systems via the Altium 365 Status Page, where you can also report an issue or subscribe for updates on the system performance. The history of past incidents is available on the Incident History page.

Quality Controls

We implement quality control and quality assurance on every update and improvement. These controls are routinely audited, both internally and by trusted third parties, to ensure that any defect is caught early in the process. We use best-practice methodologies, such as code reviews, non-production environments, and automated and manual testing, to find issues early in the development phase. The majority of errors are detected automatically and corrected before they have any impact on the user experience.

Altium 365 has a biweekly development cycle, which means updates to the platform are delivered every two weeks. Due to the cloud-based nature of the platform, no user action is required to install the updates; Altium 365 is always on and always up-to-date. The resolution time for any user-reported issues is usually faster than for on-premise products; most issues are addressed within a biweekly cycle.