Describe the process.
Receive the model.
ViewSet turns written descriptions into working ArchiMate models: native .archimate source, a review SVG and Word step descriptions. From a chat. No toolbars, no drawing.
EU hosted · nothing retained · bring your own key
- 7 elements · 7 relationships · view: customer onboarding
- ✓Relationship legality, ArchiMate 3.2 matrix
- ✓Layer placement
- ✓Naming, rule pack: default
- ✓0 orphan elements
Recorded session, shortened.
View 01 · Deliverable
One package, three files.
Every session ends in a single download. The package holds the model, the review copy and the text. Nothing to assemble afterwards.
onboarding.archimate
Source of record
A native Archi model with a full repository behind. Every element typed, every relationship legal. Opens in Archi, exports to Open Exchange XML for Sparx and BiZZdesign.
onboarding.drawio.svg
Review copy
Embeds in Confluence and Word as an image and stays editable in draw.io. Reviewers without Archi read the view and move a box before the steering committee.
onboarding-steps.docx
Step descriptions
Numbered steps in plain language, matched to the view, ready to paste into the deliverable. This is the part clients read, and the part nobody enjoys writing.
View 02 · Method
Three turns, no toolbars.
The interface is the conversation. Every element appears by name in the reply, so every change is one sentence.
Describe
Write the process in plain language, or paste what you have. ViewSet asks up to three scoping questions before drawing anything. Vague prose in, vague model out, so the questions come first.
Generate and validate
The model is built against the ArchiMate 3.2 metamodel and your rule pack, laid out top to bottom, then checked. The checklist prints with the view.
Refine and download
Say the change: rename the third actor, move the payment service down a layer. Or open the file in Archi, adjust by hand, and bring the file back. ViewSet continues from your version.
View 03 · Validation
Checks you can read.
Architects distrust generated models. Correct. So every session ends with the checklist in plain sight, and trust rests on the checks, not on the vendor. A view leaves ViewSet only after passing all five.
View 04 · Rule packs
Your conventions, stated once.
Naming, colours, allowed elements, layering. Written in plain language, stored as a rule pack, applied to every future view. The second view set costs less than the first, and the tenth looks like the first.
View 05 · Security
Built for the security review.
Your buyers sit in banks, insurers and public administrations. The questions are known, so the answers ship with the product.
Hosted in the EU
EU infrastructure under EU jurisdiction. viewset.eu means what the address says.
Nothing retained
Processed in memory, deleted at session end. Model content never enters the logs.
Bring your own key
Point ViewSet at your own Azure OpenAI or Anthropic tenant. Your text stays under agreements you already signed.
Paperwork ready
One-page DPA and subprocessor list, on request, before procurement asks twice.
View 06 · Pricing
Priced against a saved day.
A consultant bills 600 to 1200 euros a day. One saved day a month pays for the year.
Pilot
1,500 EUR fixed
Your next real view set, produced with ViewSet and delivered as the full package. You keep the rule pack. If the output disappoints, you know within a week.
Book a pilotSeat
79 EUR per month · 790 annual
Chat, validation, three exports, rule packs. Opens to pilot customers first.
Join the listEnterprise
from 15k per year
Bring-your-own-key or dedicated deployment, rule pack setup with your team, support with a name attached.
Talk to usSend a process. Get a model back.
The pilot is paid, fixed price, and produces your real deliverable, so the answer arrives in a week, not after a year of licences.
Book a paid pilot