Loading…
Loading…
Archiet extends Avolution Abacus with AI-powered compliance automation, production code generation, and drift detection. Import your existing ArchiMate models and unlock capabilities Abacus was never designed to provide.
Avolution Abacus is an Australian enterprise architecture platform known for its flexible metamodel and visual roadmapping. Unlike most EA tools that force you into a fixed notation, Abacus lets you define custom element types, relationships, and views.
Archiet has a native integration with Abacus: import your Abacus ArchiMate models into Archiet, then use Archiet's capabilities that Abacus does not provide — compliance assessment, code generation, and drift detection. Your Abacus model becomes the input for automated compliance evidence and production-ready code.
This is not a replacement scenario. Use Abacus for detailed enterprise modelling with custom metamodels. Use Archiet to extend those models with compliance automation and code generation. The ArchiMate Model Exchange format is the bridge between them.
1. Model your architecture in Abacus (using ArchiMate or your custom metamodel) 2. Export the model as ArchiMate Model Exchange File (.xml) from Abacus 3. Import the .xml into an Archiet blueprint 4. Run compliance assessment — SOC 2, ISO 27001, DORA, etc. map automatically 5. Generate code from the imported architecture (optional) 6. Set up drift detection to monitor code vs architecture alignment 7. When the architecture evolves in Abacus, re-import to keep Archiet in sync
The workflow is additive — Archiet extends Abacus, it does not replace it.
No. Abacus excels at flexible metamodel-based modelling that Archiet does not replicate. Archiet adds capabilities that Abacus does not have: AI-assisted modelling, compliance automation, code generation, and drift detection. Use both together for the full architecture-to-code-to-compliance pipeline.
In Abacus, export your repository as an ArchiMate Model Exchange File (.xml). In Archiet, go to any blueprint → Import → Upload the .xml file. All ArchiMate elements, relationships, and properties are preserved. Custom metamodel extensions may not transfer — only standard ArchiMate types are imported.
Currently, the sync is manual (export from Abacus, import into Archiet). For Enterprise customers, we can set up periodic automated import via the Abacus API. Bidirectional sync (changes in Archiet reflected back in Abacus) is on the roadmap.