Loading…
Loading…
Import your entire Avolution application portfolio into Archiet with one click. Every component, owner, and lifecycle status becomes a live ArchiMate element — ready for compliance checks, Jira stories, and code generation. No re-entry.
free plan · no credit card required · your data stays yours
Abacus is a portfolio repository. It was built to store and model. Archiet was built to run compliance, push to Jira, generate code, and detect drift. They solve different problems — and now they connect.
Tracks the portfolio. Cannot act on it.
Every imported element runs compliance checks, pushes to Jira, generates code.
Compliance is a manual export and spreadsheet exercise.
SOC 2, ISO 27001, GDPR, HIPAA, PCI-DSS, DORA, NIS2 — one click per framework.
No connection to delivery tooling (Jira, GitHub, CI/CD).
Blueprint → Jira Epics → GitHub drift detection in CI — all wired.
Architecture decisions stay in Abacus. Developers never see them.
ADRs linked to elements. GitHub Actions alerts when code violates them.
Code generation is not available.
Production-ready codebase from any blueprint, downloadable as a ZIP.
The import takes two minutes. What comes after takes hours off every compliance cycle, every sprint planning session, and every ARB review.
Connect your Avolution Minerva instance. Every ApplicationComponent — name, lifecycle status, business owner, criticality, domain — imports directly as an ArchiMate element. 400 applications become 400 elements in under two minutes.
The moment the import completes, run compliance checks across SOC 2, ISO 27001, GDPR, HIPAA, PCI-DSS, DORA, and NIS2. Archiet maps each imported element against control requirements and shows you exactly where the gaps are. No spreadsheets.
Pick any imported system, click Push to Jira, and Archiet generates structured Epics and user stories with acceptance criteria. Your Abacus data becomes delivery-ready work items without a workshop.
Connect GitHub and Archiet checks every pull request against the imported blueprint. The moment code diverges from what Abacus describes, you know — before it reaches production.
The full flow from Abacus credentials to a compliance-checked, Jira-connected architecture portfolio.
Connect your Minerva instance
Go to Settings → Integrations → Avolution Abacus. Enter your instance URL and OAuth2 credentials (client_id and client_secret from your Abacus admin portal). Test the connection — Archiet shows you how many applications it found.
Import your application portfolio
Click Import Application Portfolio. Archiet fetches every ApplicationComponent via the Minerva OData API — including Properties (lifecycle, criticality, data classification) and OutConnections (business owners, domain assignments). A new Blueprint is created automatically.
Run compliance checks immediately
Open the imported Blueprint, go to Compliance, and select a framework. Archiet runs a full control-level gap analysis against your actual portfolio data. Export the result as a PDF report for auditors.
Push to Jira, generate code, detect drift
Every imported element is a live ArchiMate element in Archiet. Push to Jira, generate code for new services, add compliance frameworks, enable GitHub drift detection — all without leaving the browser.
Archiet reads the Avolution Minerva OData API. Every field mapping is explicit and deterministic — no guessing, no silent data loss.
EEIDElement identifier (external_id)
NameElement name
DescriptionElement description
Properties.LifecycleStatusLifecycle status (normalised)
Properties.BusinessCriticalityCriticality (Critical / High / Medium / Low)
Properties.DataSensitivityTypeData classification
OutConnections: App Business OwnerBusiness owner
OutConnections: IT Security OfficerTechnical owner
OutConnections: Business Unit OwnerBusiness domain
OutConnections (all types)ArchiMate Association relationships
Properties are read from the Minerva [{Name, Value}] array format. OutConnections are resolved to owner and domain fields.
For Enterprise Architecture teams already invested in Avolution
You have done the hard work. The portfolio is documented. Lifecycle statuses are maintained. Ownership is recorded. Archiet is not asking you to redo that. It is asking to read it — and then run the compliance checks, Jira pushes, and drift detection that Abacus was never designed for.
The typical onboarding for an Archiet customer starting from zero takes a day. For an Abacus customer with an existing portfolio, it takes two minutes to import and fifteen minutes to see a compliance gap report for the first time.