The thinking behind the tool, for anyone mapping a process for the first time.
Step-by-step instructions for using Qlerify, one task at a time.
Trial, invoices, seats and cancellations.
Qlerify Modeler is a modeling tool for software teams. You map a business process together with the people who know it, using Event Storming, Domain-Driven Design, Event Modeling or User Story Mapping. The board becomes a process model, a backlog and a domain model that your coding agent can build from.
Each workflow gives you four connected things:
You can export the backlog to Jira, Azure DevOps or CSV, the model to JSON and the diagram to PDF.
Product owners, product managers, architects, business analysts, CTOs, founders and the teams around them. Qlerify is built for the discovery and design conversation that happens before a single ticket gets written.
Any AI tool that can connect to an MCP server, which includes most coding agents and AI assistants.
The integrations page has setup steps for Claude Code, Cursor, Antigravity, VS Code, Gemini CLI, Lovable, Claude and ChatGPT.
Yes. You can export cards to Jira and Azure DevOps, export data as CSV, which opens in Google Sheets or Excel, or as JSON, and connect AI coding tools over MCP. Custom integrations are available on Enterprise. Setup steps are on the integrations page.
No. Describe your process in a sentence and the AI drafts a first workflow, which you then adjust with your team.
If you want the background first, read our guides to Event Storming and Domain-Driven Design, or browse the blog. The more of the method you use, the cleaner your domain model gets.
No. Qlerify runs in the browser, in Chrome or Edge, on any operating system.
Miro is a general-purpose whiteboard. Qlerify is a modeling tool where the board is structured data: every card has a type, belongs to a step in the process, and flows into a backlog you can filter by release and export to Jira or Azure DevOps. In Miro the sticky notes are still sticky notes after the call ends, so somebody has to retype them into a tracker.
Lucidchart is a diagramming tool for documenting a process you already understand. Qlerify is for working the process out in the first place, with the domain experts in the room. Its output is an editable model rather than a drawing, so you can turn it into a domain model with aggregates and commands and generate code from it.
IcePanel documents architecture that already exists, as a C4 model of the systems you have built. Qlerify runs earlier, while you are still working out the business process and the requirements, and the workshop produces a domain model with aggregates, bounded contexts and commands that a coding agent can build from. Plenty of teams use both.
Lovable turns a prompt into a working full-stack app, which is a fast way to get an MVP in front of people. It works from what one person can describe. Qlerify runs earlier and with more people involved: you map the real process with the domain experts who know the rules, and agree what is required before anything gets generated. The two work together, because Lovable is one of Qlerify’s MCP clients, so an agreed Qlerify spec can be handed straight to it.
Spec Kit gives a coding agent a structured spec to work from in the repo, written by a developer at the terminal. Qlerify is where that spec gets produced, visually, in a workshop with the business people who know the rules, which is the part Spec Kit leaves to you. Use Qlerify to reach an agreed spec and domain model, then hand it to Spec Kit or any of the agents it supports. Qlerify connects to several of those agents over MCP too, so the spec arrives as live context instead of a pasted file.
No. Qlerify is where requirements get discovered and shaped, and Jira or Azure DevOps is where they get executed. You export from Qlerify into whichever tracker you already run sprints in.
A workflow is read-only for one of four reasons.
You opened it through a public link or an embed, which gives view-only access. Ask to be invited to the project, or use Clone this workflow to copy it into a project of your own.
Its status is set to Completed, which locks it. The project owner can change the status under Workflow Settings.
The subscription is not active. An expired trial, a failed payment or no plan puts every workflow into read-only, and your data stays untouched. On Basic, only three projects are accessible.
You are a Qlerify admin who is not a member of the project. Ask to be added as a member.
Yes. Basic and Pro includes 14 days for free, every feature unlocked, no credit card. You only add a payment method when you want to keep going after the trial.
No. Basic and Pro both include unlimited AI prompts.
The account switches to read-only: your projects and workflows are all still there and you can export to Jira, Azure DevOps, JSON, CSV or PDF. We keep them for six months in case you re-subscribe, then delete them.
Yes. Email support@qlerify.com and we will add another 14 days.
Yes, on all plans. When you remove a seat you can either drop the cost or reassign it to someone new.
Yes. You can do both, in either direction.
Yes, annual plans come with a 17% discount. You can switch from monthly to annual billing under Plan & Billing then My Plan, under the profile icon in the app.
No. Anyone with a link opens a model with one click without an account. You only pay for the people who edit.
The owner of the plan can invite new users. You can see the cost and confirm it before anything is charged. An invitation gives access to the whole project rather than a single workflow.
Basic and Pro are paid by credit card: Visa, Mastercard and other major cards. Wire transfer and invoicing are available on Enterprise plans.
No, prices exclude VAT. Qlerify is a Swedish company, so we have to charge VAT to some customers depending on where you are and whether you have a VAT number. Reach out to support@qlerify.com and we can tell you what applies.
Under Plan & Billing from the profile icon in the top right of the app.
Go to Plan & Billing then My Plan, under the profile icon in the app, and select Cancel Plan. You do not need to contact us. The subscription runs to the last day of the period you have already paid for, and nothing renews after that.
We keep it for six months so you can pick up where you left off if you come back, then it is deleted. See above for exporting your content.
Data is encrypted at rest and every connection to Qlerify uses TLS encryption. Only a small number of Qlerify staff have access to the production environment, backups run continuously with 35 days of point-in-time recovery, and we are GDPR compliant. The full statement is on our security page.
By default, in AWS data centers inside the European Union. On Enterprise plans you can choose another location or host Qlerify Modeler in your own environment.
Yes, on Enterprise plans. By default, Qlerify Modeler runs as a cloud service hosted in the European Union. Enterprise customers can choose where their data is stored, or host Qlerify Modeler in their own environment.
No. Your workflows, requirements and domain models are never used to train AI models, either by Qlerify or by the AI providers we use.
We are happy to offer discounts. Tell us about your work and we will review it case by case.
Yes. Pro includes onboarding and training sessions, and Enterprise adds custom training and workshops. Contact us to schedule one.
Fill out our support form on the contact page, or email support@qlerify.com.
Fill out our support form.
Fill out our support form.
Cannot find what you are looking for?
Contact us
