Join us in shaping the future of building automation
With the Advancis Open Platform (AOP), you can develop integrations, automations, and extensions for WinGuard—using open APIs, without modifying the core system.
Integrations and Extensions Using Open APIs
The Advancis Open Platform (AOP) transforms WinGuard into an open integration platform. Using standardized APIs, developers can create their own extensions (AOP extensions) and specifically enhance WinGuard with new features, integrations, and automations. This results in solutions that precisely meet a project’s requirements – without requiring changes to the core system.
Your benefits
- Flexibly develop custom integrations for third-party systems
- Efficiently meet project-specific requirements
- Deploy extensions in a way that is scalable across projects
- Seamlessly integrate existing IT and security infrastructures
- Implement new features without modifying the WinGuard core system
- Create future-proof solutions with full upgradeability

Develop on an open platform – while still maintaining full control.
When projects demand more than the standard
Complex security and control center solutions require flexible customization – without compromising stability, maintainability, and upgradeability.
When off-the-shelf software reaches its limits
When off-the-shelf software is used in complex security and control center projects, it often reaches its limits. Many projects give rise to requirements that go beyond the original scope of a standard product. These include, for example, the integration of customer-specific systems, the mapping of project-specific workflows, or the expansion of the solution to include industry-specific functions. Likewise, adaptation to existing IT and security architectures plays a crucial role, as new systems are rarely operated in isolation in practice but must integrate into established infrastructures.
Customization as a traditional solution
Until now, addressing such requirements has often led to custom developments or direct modifications to the core system of the software in use. While this approach works in the short term, it comes with several drawbacks. Projects often become significantly more expensive as a result, due to the additional development effort required. At the same time, the software’s upgradeability can be limited, because customizations must be taken into account or adjusted again during future updates.
The tension between flexibility and stability
This creates a constant tension for operators and integrators: on the one hand, there is a desire for high flexibility to accommodate project-specific requirements; on the other hand, a stable, maintainable, and updatable system foundation is crucial for secure and cost-effective long-term operation.
Extensions and Integrations
AOP is a development and integration platform for WinGuard that provides developers with comprehensive tools, interfaces, and documentation to create their own extensions. With AOP, functions within WinGuard can be triggered selectively, external systems can be seamlessly integrated, and data can be efficiently exchanged between different systems. In addition, the platform serves as the foundation for developing new applications within the WinGuard ecosystem.
The extensions created in this way are used in projects as so-called AOP extensions. They can be developed by various stakeholders, including system integrators, software and technology partners, and customers with their own development teams, thereby enabling flexible and customized extensions of WinGuard.
Expand openly without modifying the core system
With AOP, WinGuard becomes an extensible platform. Using an open API, developers can create their own extensions – so-called AOP extensions. These extensions make it possible to extend WinGuard in a targeted manner:
- new integrations
- additional automations
- project-specific functions
- industry-specific modules
The key advantage: The expansion takes place outside the core system. This ensures that WinGuard remains stable and upgradeable – while projects can still be implemented flexibly.
What is the idea behind AOP ?
Over the years, the requirements for our WinGuard security and building management software have become increasingly diverse. In order to meet these different needs, we have continuously developed and optimized our solution. The result of this development is the Advancis Open Platform (AOP) – a powerful, modular software platform that enables you to easily create and extend flexible, scalable applications.
Flexible expandability and central control
Thanks to the modular structure, there are almost no limits to the development of user-defined components, so that even “applications within the application” can be implemented. This means that even very individual adaptations are possible in customer projects. The central AOP API is the heart of WinGuard and allows you to easily and flexibly expand your overall solution. Thanks to the AOP API, you can seamlessly integrate and control a wide range of functions. AOP offers you the flexibility, scalability, and expandability required by modern security and building management solutions. Discover the possibilities AOP offers with WinGuard and take your projects to the next level.
![260319_AOP_List_EN IPAI_Badge_Stacked[17][71][11]](https://advancis.net/wp-content/uploads/2022/10/260319_AOP_List_EN.png)
AOP Developer Portal
Develop Extensions for WinGuard – with the AOP Developer Portal
The AOP Developer Portal is designed for developers, software partners, and integrators who wish to develop extensions for WinGuard. Using the AOP tools available in the Developer Portal, you can develop interoperable extensions for security- and mission-critical environments.
With AOP, you can develop extensions for WinGuard while retaining full control over your intellectual property. Your development remains yours, while you simultaneously become part of an open integration ecosystem. You also have flexibility when it comes to marketing: extensions can be offered through system integrators, resellers, OEM partnerships, or direct sales. This allows solutions to be deployed on a project-by-project basis as well as scaled across multiple projects. AOP was developed for security- and mission-critical environments and supports stable integrations, controlled extensibility, and reliable operation in complex projects.
AOP enables the creation of a wide variety of extensions for the WinGuard ecosystem—such as integrations with third-party systems, workflow extensions, integration services for customer projects, or industry-specific modules. The key is that the development creates additional value for customers and meaningfully expands the ecosystem.
Interested? Apply for developer access now.
Please fill out the form. We will contact you as soon as possible.
FAQ
Any questions?
Here you will find answers to the most frequently asked general questions.
Question: How long does it take to develop and deploy an extension?
Answer: That depends on individual requirements. From AOP’s perspective, we’ve kept the entry barriers as low as possible so that users can achieve initial development successes very quickly and the learning curve is steep.
Question: As a Development Partner, what benefits does the AOP offer me?
Answer: You can offer your customer the customized solution (e.g., integrating a system for which WinGuard has no interface) that they’ve always wanted.
Question: Does Advancis develop extensions on its own?
Answer: Yes, there are currently over 40 extensions available. All new extensions are implemented using AOP.
Question: How do you prevent Advancis from offering an identical extension itself?
Answer: In principle, there are no technical barriers to this. The AOP is intentionally designed as an open platform. It is managed through clear product and portfolio governance, as well as close strategic collaboration with our partners. Before Advancis enters a functional area itself, an assessment is conducted regarding:
- Strategic relevance
- market demand
- Existing Partner Solutions
- Economic viability
- Impact on the ecosystem
If there are overlaps with partner extensions, we seek direct communication at an early stage to ensure transparency and explore joint solutions. The goal is not to displace partner solutions, but to build a stable and sustainable platform ecosystem.
Question: Can identical extensions be offered based on the AOP?
Answer: Yes, because we focus on our customers’ needs. We don’t want to stifle competition; rather, we aim to establish an open ecosystem where the best solution prevails.
Question: How many extensions can I access today?
Answer: Over 40 extensions.
Question: Do I need to register to access the technical documents?
Answer: Yes, this is necessary. We need to ensure that our Terms and Conditions are accepted.
Question: What role will WinGuard play in the future?
Answer: In the future, WinGuard is intended to enable the management of all technical systems in any building, rather than focusing solely on security-related systems.
Question: How are extensions priced?
Answer: The pricing is divided into two parts
- The development partner sets the pricing for the extension.
- License fees apply for the use of WinGuard in accordance with the price list.
Question: Who is responsible for ensuring that an extension works properly?
Answer: The development partner is liable.
Any technical questions left?
Here you will find answers to the most frequently asked technical questions.
Question: What is the difference between "interface," "extension," and "adapter"?
Answer: There are only AOP Extensions, and we no longer distinguish between the different technical variants for licensing purposes.
Question: Are all extensions operated and managed within the WinGuard environment?
Answer: No – there are extensions that run entirely externally (not alongside WinGuard). These require an access token to communicate via AOP. Responsibility for their operation and administration then lies with a different instance, not with WinGuard.
Question: An extension can have skills. What does that mean?
Answer: An extension can provide various predefined functionalities—known as “skills”—defined by the AOP. These are declared by the extension via the AOP manifest. Based on its skills, the extension may or may not be displayed in certain sections of the AOP (similar to iOS apps that, for example, indicate they can handle “PDF” files).
Question: Can an extension also provide a front end?
Answer: Yes, that’s possible.
Question: Can I use different versions of the same extension?
Answer: Yes, that is possible. For example, different versions or systems can be used in parallel, provided that the third-party system also supports this. This also enables, for example, phased migrations to new versions.
Question: Where can I find technical information and examples for developing an extension?
Answer: You can find this information on the Partner Portal. There, we offer SDKs, examples, design principles, and much more.
Question: Can I access AOP data using Zapier, Make, n8n, or Flowise?
Answer: This is easily possible. All you need to do is write an adapter in AOP. Then the data can be used in other platforms.
Question: Can one extension access the data of another extension?
Answer: Yes, that is possible.
Question: Can an extension save data in WinGuard?
Answer: AOP extensions are fewer (*.exe).