Upload a machine's AASX: 43 rules show what breaks, and the fixable findings are repaired in one step after a preview. The same server serves the AAS over the IDTA Part 2 REST API, collects machine values over OPC UA, Modbus TCP and MQTT, and sends events and equipment data to MES, ERP and CMMS.
Demo account demo / 0629 — opens in a new tab. The trial server is for demonstration.
Workspace — tree on the left · summary in the middle (7 submodels · 175 elements · 0 rule errors) · collection panel on the right. Sample file · v2.1.0 screen
| Task | Usual tool | Here |
|---|---|---|
| Open · edit · export AASX | AASX Package Explorer (desktop) | In the browser, with findings and auto-fix |
| Serve AAS to other systems (Part 2 REST · registry) | Eclipse BaSyx server | The same server does it |
| Collect machine values · publish by subscription | Separate OPC UA client / server | Collects per the AID in the AAS and publishes via an OPC UA server |
Not affiliated with, and not derived from, the tools above — it combines the same jobs in one place.
01Author & tree
Findings — 0 errors · 9 warnings (fixable automatically). Sample file SPREquipment · v2.1.0 screen
Auto-fix preview — a checkbox per item with the value before and after
02Findings & auto-fix
Collection panel — the sample file connected to a virtual PLC (simulation). Demo values, not a real machine.
03Live collection
04Standard API
node scripts/part2-coverage.mjs compares the implementation with the specification's OpenAPI files# find the shell (globalAssetId) GET /api/v3.0/lookup/shells?assetIds=<base64url> # Part 2 base path per file GET /packages/{packageId}/api/v3.0/shells GET /packages/{packageId}/api/v3.0/submodels/{id}
Reference bundle — equipment count, pre-check, operation evidence and structure. Demo file on a virtual PLC (simulation)
05Bundle & report
Integrations window — Export tab: equipment master, BOM, hierarchy, maintenance plan, documents
06MES · ERP · CMMS integration · new in 2.0
@aas/bundle library)Integrations are off by default — turn them on with INTEGRATIONS=on. Creating subscriptions on PostgreSQL also needs AAS_SECRET_KEY. They are always off on the trial server.
Addressed by the AID in the AAS
| Item | Detail |
|---|---|
| Self-hosted | Docker Compose, or from source on Node.js 22 or later. No external cloud is involved. |
| Storage | PostgreSQL for shared use, or a single data folder for one person. |
| Accounts & roles | Admin, editor, viewer — with an audit trail of who changed what. |
| Who can reach it | Run from source with neither accounts nor an API key and it listens on 127.0.0.1 only. The Docker example opens it to your network (AAS_ALLOW_OPEN=1 in .env.example), so create the first administrator right after start and put HTTPS in front. |
| OPC UA server | Off by default. When on, clients sign in with a web account over Sign or SignAndEncrypt; no anonymous sessions, and an administrator trusts each client certificate once. |
| Private workspaces | AAS_WORKSPACE=private shows each person only what they uploaded. |
| Sign-in protection | Only scrypt hashes are stored; five failures lock the account for five minutes. Cookies are HttpOnly and SameSite=Strict. |
| Outbound connections | Webhooks and MQTT refuse loopback and metadata addresses; private networks only when listed. Signing secrets are sealed with AES-256-GCM. |
git clone https://github.com/waceinc/vexplor-aas.git && cd vexplor-aas cp .env.example .env sed -i.bak "s/^POSTGRES_PASSWORD=.*/POSTGRES_PASSWORD=$(openssl rand -hex 16)/" .env docker compose up -d --build
Line three fills the empty database password (POSTGRES_PASSWORD) with a random value — Docker refuses to start while it is empty.
Open http://localhost:8080 and go to Settings → Create the first administrator. The server is open to your network (AAS_ALLOW_OPEN=1), so it asks for a setup code, printed in the startup log: docker compose logs app | grep "설치 코드" (or grep "setup code" with AAS_LANG=en in .env). Until the first administrator exists, anyone on the network can open it.
Use the demo account without signing up. Downloading your files requires an account.
| Demo account | Member | |
|---|---|---|
| Open · edit · lint · auto-fix | Yes | Yes |
| View the validation report | Yes | Yes |
| Download AASX · bundle | Members | Yes |
Demo account demo / 0629. Each demo sign-in gets its own empty workspace, and idle files are deleted. The operator can see them — keep confidential data on your own server.
| Open source | Detail |
|---|---|
| Current release | VEXPLOR AAS Studio 2.2.0 |
| License | Apache License 2.0 — modify it and ship it in commercial products |
| Names · logos | The names and logos VEXPLOR and WACE are not licensed under Apache-2.0 (see NOTICE) |
| Source · docs | github.com/waceinc/vexplor-aas · Official project page |
Under Connect sits the open-source tool VEXPLOR AAS Studio (Apache-2.0).
Connect is the equipment and system integration module. Using the international standard AAS (IEC 63278) and industrial protocols, it converts floor data into a standard format.
See VEXPLOR Connect →Download it from the public repository and install it yourself. To review equipment integration with us, request an adoption diagnosis.